Set up AWS CLI locally and confirm which identity and account are currently active.
Build a habit of verifying AWS context before making cloud changes.
Set access key, secret key, default region, and output format.
Command
aws configureExpected Result
AWS CLI should save your credentials and default settings.
Check what profile, region, and credential sources are active.
Command
aws configure listExpected Result
You should see configured values and where they come from.
Confirm which AWS account and principal the CLI is using.
Command
aws sts get-caller-identityExpected Result
You should see account ID, user or role ARN, and principal details.
Inspect the current IAM user if user-based credentials are in use.
Command
aws iam get-userExpected Result
You should see details about the current IAM user if applicable.
Review why identity verification should happen before any cloud changes.
Expected Result
You should be able to explain why checking account and role context prevents mistakes.
You can configure AWS CLI and verify the active account safely.
You understand why checking AWS identity is one of the first commands to run.