A company is setting up a new multi-department environment on AWS. The security team is defining identity and access management policies for corporate employees, applications running on Amazon EC2 instances, and administrative workflows. Which of the following are recommended AWS IAM best practices for managing access for these entities? (Select TWO.)
- Assign IAM roles to Amazon EC2 instances instead of storing long-term AWS access keys within the application code.Answer
- Use AWS IAM Identity Center to federate employee identities from the company's existing identity provider for console access.Answer
- CCreate a single shared IAM user with administrator permissions for all developers to simplify credential rotation.
- DUse the AWS account root user for daily administrative and deployment tasks to ensure full visibility.
- ERely on AWS to automatically manage and rotate access keys stored within customer application code on Amazon EC2 instances.
Answer
Assigning IAM roles to Amazon EC2 instances to avoid storing hardcoded credentials, and using AWS IAM Identity Center to federate employee identities from an existing identity provider.
The correct practices are to assign IAM roles to EC2 instances so applications can access resources using temporary security credentials, and to use AWS IAM Identity Center to federate employee identities from an existing identity provider. This aligns with the principle of least privilege and avoids managing long-term static credentials.
Step-by-Step Solution
Key Concept
AWS IAM best practices for managing credentials and access for applications and human users
Estimated Time:1m 30s