AWS Command Line Interface (CLI) tools allows you to manage your
AWS services from the command line. For it to work you'll need to have an
IAM user configured for programmatic access and with appropriate permission, and to configure the
CLI tools configured on your machines.
These steps specifically outline how to configure
Linux or any other
UNIX-based operating systems such as
Access key IDand
Secret access keyfor the user when creating the
awscommand in the command line with
$ aws configure
AWS Access Key IDof the user.
AWS Access Key ID [None]: AKIAJ3TE4LUDC4I6SQDQ
AWS Secret Access Keyof the user.
AWS Secret Access Key [None]: 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
Default region nameto use the account.
Default region name [None]:
You could leave the field blank. The list of available regions are available in
AWS online documentation.
AWS Regions and Endpoints
Default output format.
Default output format [None]:
You could leave the field blank. Default value is
json but you can also set it to
$ ls .aws/ config credentials
AWS Access Key IDand
AWS Secret Access Keystored in ~/.aws/credentials
$ cat .aws/credentials [default] aws_access_key_id = AKIAJ3TE4LUDC4I6SQDQ aws_secret_access_key = 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
Default region nameand
Default output formatare stored in ~/.aws/config.
$ cat .aws/config [default]
You could manually add the configuration later in the following format:
awscommand to execute upon your
AWSaccount wherever you have the correct permission for.
$ aws s3 ls 2018-12-29 13:58:51 simplified-guide
Learn more about Amazon Web Services. Get AWS Solutions Architect - Associate certified!
Written by Mohd Shakir Zakaria.
Last updated on 2019-03-26.