Authentication and access using AWS SDKs and tools

When you develop an AWS SDK application or use AWS tools to use AWS services, you must establish how your code or tool authenticates with AWS. You can configure programmatic access to AWS resources in different ways, depending on the environment the code runs in and the AWS access available to you.

Authentication options for code running locally (not in AWS)

• Using IAM Identity Center to authenticate AWS SDK and tools – As a security best practice, we recommend using AWS Organizations with IAM Identity Center to manage access across all your AWS accounts. You can create users in AWS IAM Identity Center, use Microsoft Active Directory, use a SAML 2.0 identity provider (IdP), or individually federate your IdP to AWS accounts. To check if your Region supports IAM Identity Center, see AWS IAM Identity Center endpoints and quotas in the Amazon Web Services General Reference.

• Using IAM Roles Anywhere to authenticate AWS SDKs and tools – You can use IAM Roles Anywhere to obtain temporary security credentials in IAM for workloads such as servers, containers, and applications that run outside of AWS. To use IAM Roles Anywhere, your workloads must use X.509 certificates.

• Assuming a role with AWS credentials to authenticate AWS SDKs and tools – You can assume an IAM role to temporarily access AWS resources that you might not have access to otherwise.

• Using AWS access keys to authenticate AWS SDKs and tools – Other options that might be less convenient or might increase the security risk to your AWS resources.

Authentication options for code running within an AWS environment

If your code runs on AWS, credentials can be made automatically available to your application. For example, if your application is hosted on Amazon Elastic Compute Cloud, and there is an IAM role associated with that resource, the credentials are automatically made available to your application. Likewise, if you use Amazon ECS or Amazon EKS containers, the credentials set for the IAM role can be automatically obtained by the code running inside the container through the SDK's credential provider chain.

• Using IAM roles to authenticate applications deployed to Amazon EC2 – Use IAM roles to securely run your application on an Amazon EC2 instance.

• You can programmatically interact with AWS using IAM Identity Center in the following ways:

  • Use AWS CloudShell to run AWS CLI commands from the console.

  • To try cloud-based collaboration space for software development teams, consider using Amazon CodeCatalyst.

Authentication through a web-based identity provider - Mobile or client-based web applications

If you are creating mobile applications or client-based web applications that require access to AWS, build your app so that it requests temporary AWS security credentials dynamically by using web identity federation.

With web identity federation, you don't need to create custom sign-in code or manage your own user identities. Instead, app users can sign in using a well-known external identity provider (IdP), such as Login with Amazon, Facebook, Google, or any other OpenID Connect (OIDC)-compatible IdP. They can receive an authentication token, and then exchange that token for temporary security credentials in AWS that map to an IAM role with permissions to use the resources in your AWS account.

To learn how to configure this for your SDK or tool, see Assuming a role with web identity or OpenID Connect to authenticate AWS SDKs and tools.

For mobile applications, consider using Amazon Cognito. Amazon Cognito acts as an identity broker and does much of the federation work for you. For more information, see Using Amazon Cognito for mobile apps in the IAM User Guide.

More information about access management

The IAM User Guide has the following information about securely controlling access to AWS resources:

• IAM Identities (users, user groups, and roles) – Understand the basics of identities in AWS.

• Security best practices in IAM – Security recommendations to follow when developing AWS applications according to the shared-responsibility model.

The Amazon Web Services General Reference has foundational basics on the following:

• Understanding and getting your AWS credentials – Access key options and management practices for both console and programmatic access.

IAM Identity Center trusted identity propagation (TIP) plugin to access AWS services

• Using the TIP plugin to access AWS services – If you are creating an application for Amazon Q Business or other service that supports trusted identity propagation, and are using the AWS SDK for Java or the AWS SDK for JavaScript, you can use the TIP plugin for a streamlined authorization experience.

AWS Builder ID

Your AWS Builder ID complements any AWS accounts you might already own or want to create. While an AWS account acts as a container for AWS resources you create and provides a security boundary for those resources, your AWS Builder ID represents you as an individual. You can sign in with your AWS Builder ID to access developer tools and services such as Amazon Q and Amazon CodeCatalyst.

• Sign in with AWS Builder ID in the AWS Sign-In User Guide – Learn how to create and use an AWS Builder ID and learn what the Builder ID provides.

• CodeCatalyst concepts - AWS Builder ID in the Amazon CodeCatalyst User Guide – Learn how CodeCatalyst uses an AWS Builder ID.