You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws-v3/iam-role-architecture.md
+4-13Lines changed: 4 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,8 @@ The integration is designed to work with the full `ReadOnlyAccess` policy, which
15
15
-**Reliable operation** without permission-related issues.
16
16
:::
17
17
18
+
If you prefer to create the IAM role manually rather than using the CloudFormation template, the following sections describe the setup we implement. This will help you understand the reasoning behind our design choices and adapt them if you decide to configure the role differently.
19
+
18
20
## Role structure
19
21
20
22
For multi-account setups, the role structure is replicated across all target accounts.
@@ -74,7 +76,7 @@ The IAM role uses an **OIDC (OpenID Connect) trust policy** with **IRSA (IAM Rol
74
76
75
77
The role uses the **AWS managed `ReadOnlyAccess` policy**, which provides comprehensive read-only access to all AWS services:
76
78
77
-
```yaml
79
+
```yaml showLineNumbers
78
80
ManagedPolicyArns:
79
81
- arn:aws:iam::aws:policy/ReadOnlyAccess
80
82
```
@@ -86,17 +88,6 @@ ManagedPolicyArns:
86
88
- **AWS Maintained**: AWS manages and updates the policy as needed.
87
89
- **Read-Only Security**: Only read permissions, no write/delete/create access.
88
90
89
-
## Permission categories
90
-
91
-
Since the role uses the AWS managed `ReadOnlyAccess` policy, it has comprehensive read-only access to **all AWS services**.
92
-
Here are the key categories relevant to AWS Hosted by Port:
93
-
94
-
- **Comprehensive Discovery**: Access to all AWS resource types.
95
-
- **Future-Proof**: New services are automatically supported without redeployment.
96
-
- **Operational Efficiency**: No CloudFormation updates needed when adding new services.
97
-
- **Consistent Access**: Same permission model across all services.
98
-
- **No Maintenance**: AWS manages policy updates.
99
-
100
91
## Security considerations
101
92
102
-
From a security view point the integration uses a **read-only** role. It can list/describe and read metadata/tags, but cannot create, modify, delete, or change policies. No cross-account access is available unless it is explicitly configured.
93
+
From a security view point the integration uses a **read-only** role. It can list/describe and read metadata/tags, but cannot create, modify, delete, or change any resource.
0 commit comments