AWS Certified Data Analytics Specialty 2021 - Hands-On! - Amazon Web Services Security Token Service (AWS STS) and Cross

The video tutorial explains the Security Token Service (STS) in AWS, which provides temporary and limited access to resources. It covers the use of STS for cross-account access and federation, including integration with Active Directory and third-party providers like Cognito. The tutorial also details the Assume Role API, which allows users to impersonate IAM roles with temporary credentials. The session concludes with a summary and a preview of the next lecture on federation.

What is the primary purpose of the Security Token Service (STS)?

• To provide permanent access to AWS resources

• To grant limited and temporary access to AWS resources

• To manage AWS billing and costs

• To create AWS user accounts

Which of the following is a use case for STS in AWS?

• Cross-account access

• Managing AWS billing

• Monitoring AWS services

• Creating permanent user credentials

How does STS facilitate federation with third-party providers?

• By managing AWS billing

• By creating new AWS accounts

• By providing permanent credentials

• By using SAML and linking Active Directory credentials

What is the AssumeRole API used for in the context of STS?

• To create new AWS accounts

• To manage AWS billing

• To define IAM roles

• To retrieve temporary security credentials

What is the validity period for credentials obtained through the AssumeRole API?

• 1 to 2 hours

• 2 to 3 hours

• 5 to 10 minutes

• 15 minutes to 1 hour