An enterprise is planning to grant its network engineering team access to manage resources in the AWS Cloud. The network engineers are currently managed in the company's on-premises Active Directory. The company's security policy requires that engineers authenticate using their existing corporate credentials and that no long-term AWS credentials, such as access keys, are created or stored. Which solution meets these requirements while following AWS security best practices?
- AShare the AWS account root user credentials with the network engineering team and enable Multi-Factor Authentication using a shared corporate hardware token.
- Configure identity federation using AWS IAM Identity Center integrated with the company's Active Directory, and assign permission sets to the engineering group.Answer
- CCreate individual IAM users in the AWS account for each network engineer, generate long-term access keys, and configure active directory synchronization to update their IAM passwords weekly.
- DStore the corporate Active Directory administrator credentials as a plaintext parameter in Systems Manager Parameter Store, and write a script on a bastion host to dynamically provision IAM roles for engineers when they log in.
Answer
Configure identity federation using AWS IAM Identity Center integrated with the company's Active Directory, and assign permission sets to the engineering group.
The correct solution uses AWS IAM Identity Center to federate the on-premises Active Directory. This allows network engineers to sign in with their corporate credentials and access AWS resources using short-term, temporary credentials. This directly fulfills both requirements of using existing corporate credentials and avoiding long-term access keys.
Step-by-Step Solution
Key Concept
Identity Federation and Single Sign-On (SSO) with IAM Identity Center