A company is establishing its AWS environment and needs to define its identity and access management strategy. The security team must ensure that application servers running on Amazon EC2 can securely access files in Amazon S3, and that emergency administrative actions can be performed securely if primary identity systems fail. Which two AWS Identity and Access Management (IAM) best practices should the company implement? (Select TWO.)
- Associate an IAM role with the EC2 instances using an instance profile, allowing the application to use temporary security credentials.Answer
- Configure the AWS account root user with multi-factor authentication (MFA), secure its login credentials, and use it only for tasks that explicitly require root permissions.Answer
- CCreate an IAM user for the application, generate long-term access keys, and store them directly in the application code on the EC2 instances.
- DUtilize the AWS account root user for daily administrative activities and share its credentials with the development team to simplify resource provisioning.
- EApply a Service Control Policy (SCP) at the AWS Organizations level to grant direct read and write access to the S3 bucket.
Answer
The correct practices are to associate an IAM role with the EC2 instances using an instance profile and to configure the AWS account root user with multi-factor authentication (MFA) while securing its credentials for emergency-only use.
Associating an IAM role with an EC2 instance provides temporary security credentials dynamically, eliminating the need to store long-term access keys. Additionally, securing the AWS account root user with MFA and restricting its usage to emergency-only tasks is a fundamental AWS security best practice.
Step-by-Step Solution
Key Concept
AWS IAM Best Practices for EC2 access and Root User Security