An enterprise is designing a multi-account strategy using AWS Organizations. An application running on Amazon ECS tasks in the Production Account (Account A) must retrieve database credentials from AWS Secrets Manager in the Security Account (Account B). The secret in Account B is encrypted using a customer managed KMS key. The development team must also be federated into both accounts using their corporate Identity Provider (IdP) to manage these workloads. The architecture must satisfy security audits, enforce automatic rotation of credentials, and adhere to the principle of least privilege. Which combination of actions should the solutions architect take to meet these requirements securely? (Select TWO.)
- Configure AWS IAM Identity Center integrated with the corporate SAML 2.0 Identity Provider (IdP) to manage console access, and assign developers to appropriate permission sets in both Account A and Account B.Cevap
- Attach an IAM role to the ECS task definition in Account A that grants permissions to retrieve the secret and decrypt with the KMS key. In Account B, update the resource-based policy of the secret and the key policy of the KMS key to permit access from the ECS task IAM role.Cevap
- CCreate individual IAM users in Account B for each developer, and configure the corporate IdP to assume these user identities using AWS Security Token Service (STS) long-term access keys.
- DEnable automatic key rotation for the customer managed KMS key in Account B, ensuring that all existing Secrets Manager secrets are immediately re-encrypted using the new key version and the older key version is deleted.
- EStore the database credentials as a plaintext String parameter in Systems Manager Parameter Store in Account A to avoid cross-account KMS decryption and IAM configuration, and allow the ECS task to read this parameter directly.
Cevap
To meet the requirements, the solutions architect should configure AWS IAM Identity Center integrated with the corporate SAML 2.0 Identity Provider (IdP) to manage console access, and attach an IAM role to the ECS task definition in Account A that has permission to retrieve the secret and decrypt using the KMS key, while configuring the resource-based policy of the secret and the KMS key policy in Account B to trust the ECS task role.
The correct solution involves setting up AWS IAM Identity Center for federated single sign-on access to eliminate the need for local IAM users, and establishing cross-account access by combining identity-based policies (ECS task role) in the source account with resource-based policies (the secret and KMS key policies) in the target account.
Adım Adım Çözüm
Anahtar Kavram
Cross-account access delegation using IAM roles, resource policies, KMS key policies, and IAM Identity Center federation.