//
Search across all documentation pages
7 pages in this section.
Why installing and configuring the AWS CLI is step one for both boto3 and the AWS SDK for JavaScript v3 - they read the same shared credential files.
Install AWS CLI v2, run aws configure, verify your identity, and confirm boto3 and the AWS SDK for JavaScript v3 read the same profile.
Lay out ~/.aws/config and ~/.aws/credentials for multiple accounts and roles, then select any profile from the CLI, boto3, or the AWS SDK v3.
Configure aws configure sso, run aws sso login for short-lived credentials, and let boto3 and the AWS SDK v3 pick them up automatically.
Use --output json/table/text and --query JMESPath to shape CLI results, and see the same filtering done in boto3 and the AWS SDK v3.
Best practices for AWS CLI setup: profile naming, credential rotation, preferring SSO over long-lived keys, and keeping secrets out of code and git.