AWS Resource Interaction Methods Exam frequency ⭐⭐⭐⭐⭐

AWS Resource Interaction: Console, CLI, SDK, and IaC

AWS Management Console / AWS CLI / AWS SDK / Infrastructure as Code

devopsAWS CLIAWS SDKIaC
Last organized

All four call AWS APIs, but differ in interface, credential source, and automation level.

In one sentence

Console, CLI, SDK, and IaC all call AWS APIs; the difference is whether the action comes from clicks, commands, application code, or a declarative template.

MethodBest forTypical credentials
ConsoleExploration and manual operationsPassword + MFA or SSO session
CLIBatch and routine automationIdentity Center, roles, profiles
SDKApplication integrationCredential provider chain
CloudFormation / IaCRepeatable infrastructureCaller permissions or service role

The Region Selector changes the regional resource view. For a missing resource, check account, identity, Region, List / Describe permission, then filters and state. Multi-session keeps login contexts in parallel but creates no account and merges no permissions.

Local CLI uses locally discovered credentials. CloudShell receives temporary rotating credentials for the current console identity. aws configure only stores profile credentials, default Region, and output format; it grants no IAM permissions.

Access key ID identifies a credential, secret access key signs requests, and temporary credentials also require a session token. CLI and SDK do not require long-term keys: people should prefer Identity Center and workloads should use roles.

Roles and the credential provider chain

CLI and SDK processes running on EC2 should use an IAM role through an instance profile and obtain rotating temporary credentials from IMDS. Do not run aws configure on an instance to store a long-term secret. Passing a role to a service normally requires a narrowly scoped iam:PassRole permission; this differs from the current user assuming the role.

CloudShell boundaries

CloudShell obtains temporary credentials for the current console identity, includes the AWS CLI, and provides persistent HOME storage separated by Region. A command can override the default Region with —region, but no Region selection bypasses IAM policy. It is useful for temporary administration and troubleshooting, not as a separate identity or a higher-privilege entry point.