Question

Difficulty: MediumIdentity and Access Management (IAM)

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.)

  1. Configure AWS IAM Identity Center to federate access from the existing corporate identity provider.Answer
  2. Configure developers to use short-lived temporary credentials for local command-line access.Answer
  3. C
    Share the AWS account root user credentials with the development team to simplify console access.
  4. D
    Create a single IAM user with administrative permissions and share its permanent access keys among all developers.
  5. E
    Rely 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

1
Address console access integration by implementing identity federation.
AWS IAM Identity Center is configured to allow developers to log in to the console using their corporate identity provider credentials.
This satisfies the requirement to integrate access with the existing corporate identity provider without creating duplicate IAM users.
2
Address programmatic workstation security by enforcing short-lived temporary credentials.
Developers use short-lived credentials (such as those generated via AWS STS or IAM Identity Center CLI integration) on their local machines.
This satisfies the requirement to avoid storing long-term credentials like permanent IAM access keys on local workstations.

Key Concept

Identity federation and short-lived credentials management in AWS IAM.
Rate this question