Cross Account IAM Role enables a client from an AWS account to access the resources of another AWS account temporarily using the Binary Snaps that support reading from/writing into S3 buckets. This helps organizations or different teams in an organization to access each other's AWS account without compromising security by sharing AWS credentials.
You can briefly allow access to your AWS account and specify the access duration. You must create a role and policy in your AWS account. The policy created by the host is attached to the access seeker's account. This cross account IAM role enables SnapLogic to trigger the necessary APIs.
The Summary page displays the Amazon Resource Name number. Make a note of this ARN, as you will need it when completing the AWS IAM Role account settings.
Steps
Click the JSON tab and enter the following policy in the editor then Click Review Policy.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "sts:AssumeRole", "Resource": "<Role ARN>" } ] } |
4. Review the policy summary. Add a name and optionally, a description for this policy, and click Create policy.
The policy is created and can be assigned to the cross-account IAM role.
You can configure the cross account IAM Role inside the S3 Account or S3 Dynamics Account. Enter the credentials provided of the IAM role. Enter Role ARN and External ID (if setup by the host) provided from the host S3 account.
OR
For an account used in EC2 groundplex with IAM role configured, select the IAM role check box.
2. Enter the Role ARN and External ID provided by the S3 host account.