A company is setting up AWS access for a team of developers who need to manage cloud resources through the AWS Management Console and execute command-line scripts locally. The company wants to integrate access with their existing corporate identity provider and ensure that developers do not store long-term credentials on their local workstations. Which of the following actions should the company take to meet these requirements? (Select TWO.)
- Configure AWS IAM Identity Center to federate access from the existing corporate identity provider.Answer
- Configure developers to use short-lived temporary credentials for local command-line access.Answer
- CShare the AWS account root user credentials with the development team to simplify console access.
- DCreate a single IAM user with administrative permissions and share its permanent access keys among all developers.
- ERely on AWS to automatically secure and rotate any permanent credentials stored locally on user workstations.
Answer
Configure AWS IAM Identity Center to federate access from the corporate identity provider and configure developers to use short-lived temporary credentials for local command-line access.
Configuring identity federation via AWS IAM Identity Center integrates access with the corporate identity provider. Enforcing short-lived temporary credentials for local CLI access prevents the risk of storing long-term credentials on developer workstations.
Step-by-Step Solution
Key Concept
Identity federation and short-lived credentials management in AWS IAM.