orbweb/aws repository overview

⁠What is docker-aws

Docker⁠ image for running the Amazon Web Services Command Line Interface⁠ and s3cmd⁠. It creates a Docker⁠ image containing all dependencies needed to run aws and s3cmd. That way, you can run these tools in a Docker⁠ container without setting the dependencies on the host system.

⁠Version

• Check versino : aws --version
• Update version, just go to docker hub and build this Dockerfile, it will help you to build the latest version.

⁠AWS Credentials

There are three primary methods for setting up your AWS credentials:

1. Run the setup using the container, i.e. when you run the CLI tools for the first time, you need to configure the aws cli⁠ with your AWS credentials. For example:

   / # aws configure
   AWS Access Key ID [None]: [YOUR_AWS_ACCESS_KEY_ID_HERE]
   AWS Secret Access Key [None]: [YOUR_AWS_SECRET_ACCESS_KEY_ID_HERE]
   Default region name [None]: [YOUR_AWS_REGION_HERE]
   Default output format [None]: [YOUR_AWS_OUTPUT_FORMAT_HERE]
   

   Copy

2. The volume /root/.aws has been exposed within the image for external access. Therefore you can mount the AWS credential file to the container:

   docker run --volume ~/.aws:/root/.aws orbweb/aws:latest aws [some_command]
   

   Copy

3. By configuring your EC2 instances to make use of IAM Roles, the AWS CLI tools can then transparently make use of this role. Note however, that not all CLI tools can currently leverage this functionality, namely some of the RDS tools.

⁠Getting started with the AWS CLI and s3tools

For documentation on the AWS CLI, see the AWS command line interface documentation⁠ and the aws-cli GitHub page⁠. For S3 tools, see the S3 tools documentation⁠.