Skip to content

Commit 3218a1b

Browse files
author
iru
authored
doc: clarify org role
1 parent e1c002c commit 3218a1b

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

examples/organizational/README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,8 @@ Minimum requirements:
2626
2727
3. Organizational Multi-Account Setup
2828
* An specific role is required, to enable Sysdig to impersonate and be able to provide
29-
* For the scanning feature, the ability to pull ECR hosted images when they're allocated in a different account
29+
* For scanning feature, the ability to pull ECR hosted images when they're allocated in a different account
30+
* For scanning too, the ability to query the ECS tasks that are allocated in different account, in order to fetch the image to be scanned
3031
* A solution to resolve current limitation when accessing an S3 bucket in a different region than where it's being called from
3132
* By default, it uses [AWS created default role `OrganizationAccountAccessRole`](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_access.html)
3233
* When an account is created within an organization, AWS will create an `OrganizationAccountAccessRole` [for account management](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_access.html), which Sysdig Secure for Cloud will use for member-account provisioning and role assuming.

0 commit comments

Comments
 (0)