New answers tagged

1

Have you considered AWS Cloud Shell? It's free, has AWS CLI pre-installed, and after the initial launch I think it opens quite quickly. Your question doesn't say what you're trying to achieve, just how you're trying to achieve it, so it's difficult to know for sure if this is going to help.


1

Assuming you can run a container you could use the AWS CLI version 2 Docker image. After the image is pulled the first time the container launches and runs aws quickly.


3

I don't think so, most of the dependencies are used by most of the AWS CLI commands I'd suspect so installing a trimmed down version won't really help much. But you can either: Use an AMI that comes with AWS CLI already installed - e.g. Amazon Linux 2 Create your own AMI with AWS CLI installed and use that as your base image - simply spin up an instance ...


0

Bit old question but, I made a bash script to automate it: https://gist.github.com/maurostorch/0a03da8770f9c798d964cb67befae935


0

In the <output.json> field, you should write uploaded file name. if the uploaded file name you want retrive, is a: backup.zip, you should run your command like this: aws glacier get-job-output --account-id - --vault-name <example-vault-name> --job-id <job-id> backup.zip at the end, the backup.zip in your system. you can verify the ...


0

CreateImage now supports resource level policies. The following policy allows creating an image but only for the specified instance id: { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowCreateImage", "Effect": "Allow", "Action&...


Top 50 recent answers are included