Passing access and aws cli secret key

Question

I am trying to inject access and private key with aws cli. eg.

aws ec2 describe-instances --aws-access-key <access_key> --aws-secret-key <secret_key> 

The -o and -w options are also used to access the private key, respectively. It says: Unknown parameter aws-access-key and aws-secret-key

Answer 1

You can provide keys on the command line through envars:

 AWS_ACCESS_KEY_ID=ABCD AWS_SECRET_ACCESS_KEY=EF1234 aws ec2 describe-instances 

See http://docs.aws.amazon.com/cli/latest/topic/config-vars.html#credentials

EDIT: @wisbucky noted that this can leave secrets in the history of your team. One way to get around this in bash at least, I think, is to add the command to an empty space, and the command should not extend to your bash history.

Answer 2

You can use it like that;

 aws configure set aws_access_key_id <yourAccessKey> aws configure set aws_secret_access_key <yourSecretKey> 

For more information, use this;

 aws configure set help 

General pattern:

 aws <command> help aws <command> <subcommand> help 

Hope this helps!

Answer 3

To summarize aws doc , there are several ways to pass credentials to the command line. Please note that there are no command line options for passing the key and private key directly. Instead, a "provider chain" is used.

In my bash scripts, I often use environment variables. To add a little security, I create a file containing the variables, and not put them in a script. With named profiles, this is even easier.

Supply Chain:

1. command line options: specify region, output format or profile
2. Environment variables: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN
3. AWS Credentials File - Located at ~ / .aws / credentials on Linux, macOS, or Unix, or at C: \ Users \ USERNAME.aws \ credentials on Windows. This file can contain several named profiles in addition to the default profile.
4. CLI configuration file - usually located in ~ / .aws / config on Linux, macOS or Unix, or in C: \ Users \ USERNAME.aws \ config on Windows. This file can contain a default profile, named profiles, and specific CLI configuration settings for each.
5. Container credentials - Provided by Amazon Elastic Container Service in container cases when you assign a role to your task.
6. Instance profile credentials — These credentials can be used in EC2 instances with the assigned instance role and delivered through the Amazon EC2 metadata service.

Answer 4

You can also use aws configure:

 $ aws configure AWS Access Key ID [None]: xxxxxxxxxxxxxxxxxxxxxxxxx AWS Secret Access Key [None]: xxxxxxxxxxxxxxxxxxxxxxxxx 

Answer 5

It’s best and safest to use IAM roles. There you can set certain rights to this instance and access to it in your account.

Depending on which version of awscli you are using, you can use instance descriptions in several ways.

Like this:

 ec2din -O your-key -W your-secret-key --region your-region 

There is also a big difference when you install awscli with pip installation or from pkg, such as the debug debug package.

ec2din - short command for ec2-describe-instance

Other examples here: ec2-describe instances

Sincerely.

Answer 6

I had to access multiple accounts on Amazon .... so my solution is:

in: ~ / .aws / config

[default] aws_access_key_id = xxxx aws_secret_access_key = xxxxxx region = sa-east-1 output = text

[profile prof1] region = us-east-1 output = text aws_access_key_id = yyy aws_secret_access_key = yyyyy

[profile prof2] region = us-east-1 output = text aws_access_key_id = wwwwww aws_secret_access_key = wwwww

..and then, when aws CLI was called, I passed the "--profile" parameter as:

/ usr / local / bin / aws ec2 describe-security-groups --group-ids sg-xxxx --profile prof2

...this is!

Answer 7

You must save your credentials in the file ~ / .aws / config (or .aws / credentials)

Learn more about how to set it up. Http://docs.aws.amazon.com/cli/latest/reference/configure/index.html

Also, as an alternative way, you can create an IAM role and a specific policy and set it for your ec2 instance, where you will use aws cli, then you will not need any credential settings there.

Answer 8

To access aws through cli,

 aws configure 

Answer 9

Another method is to use echo with aws configuration as a single line:

 echo -ne '%s\n%s\n%s\n%s\n' <access_key> <security_key> <region> <output> | aws configure