├── .github ├── ISSUE_TEMPLATE │ ├── bug_report.md │ └── feature_request.md └── workflows │ └── main.yml ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── Dockerfile ├── LICENSE ├── README.md ├── SECURITY.md ├── get_tags.sh ├── latest └── releases /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: bug 6 | assignees: richarvey 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Desktop (please complete the following information):** 27 | - OS: [e.g. iOS] 28 | - Docker Version [e.g. CE 19.0.3] 29 | - Version Tag [e.g. 2.2.10] 30 | 31 | **Additional context** 32 | Add any other context about the problem here. 33 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: '' 5 | labels: enhancement 6 | assignees: richarvey 7 | 8 | --- 9 | 10 | **Is your feature request related to a problem? Please describe.** 11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 12 | 13 | **Describe the solution you'd like** 14 | A clear and concise description of what you want to happen. 15 | 16 | **Describe alternatives you've considered** 17 | A clear and concise description of any alternative solutions or features you've considered. 18 | 19 | **Additional context** 20 | Add any other context or screenshots about the feature request here. 21 | -------------------------------------------------------------------------------- /.github/workflows/main.yml: -------------------------------------------------------------------------------- 1 | # This is a basic workflow to help you get started with Actions 2 | 3 | name: build 4 | 5 | # Controls when the action will run. 6 | on: 7 | schedule: 8 | - cron: '33 13 * * 1-5' 9 | push: 10 | branches: [ main ] 11 | # Publish semver tags as releases. 12 | tags: [ 'v*.*.*' ] 13 | pull_request: 14 | branches: [ main ] 15 | 16 | # Allows you to run this workflow manually from the Actions tab 17 | workflow_dispatch: 18 | 19 | jobs: 20 | checkTags: 21 | name: Check Tags 22 | runs-on: "ubuntu-latest" 23 | outputs: 24 | latest_version: ${{ steps.getTags.outputs.latest_version }} 25 | local_version: ${{ steps.getTags.outputs.local_version }} 26 | build: ${{ steps.getTags.outputs.build }} 27 | steps: 28 | - name: Get Tags 29 | id: getTags 30 | run: | 31 | echo "Getting all releases" 32 | curl https://api.github.com/repos/aws/aws-cli/tags | jq -r '.[0].name' | grep -v dev > releases && cat releases | head -n1 > latest 33 | curl https://api.github.com/repos/WAOptics/aws-docker-toolkit/tags | jq -r '.[0].name' | grep -v dev > releases && cat releases | head -n1 > local_version 34 | if [ $local_version != $latest_version ]; then echo "true" > build ; fi 35 | echo "latest_version=`cat latest`" >> $GITHUB_OUTPUT 36 | echo "local_version=`cat local_version`" >> $GITHUB_OUTPUT 37 | echo "build=`cat build`" >> $GITHUB_OUTPUT 38 | 39 | build: 40 | name: Build 41 | needs: checkTags 42 | runs-on: ubuntu-latest 43 | outputs: 44 | latest_version: ${{ steps.latestTag.outputs.latest_version }} 45 | steps: 46 | - 47 | name: Set up QEMU 48 | uses: docker/setup-qemu-action@v1 49 | - 50 | name: Set up Docker Buildx 51 | uses: docker/setup-buildx-action@v1 52 | - 53 | name: Login to DockerHub 54 | uses: docker/login-action@v1 55 | with: 56 | username: ${{ secrets.DOCKERHUB_USERNAME }} 57 | password: ${{ secrets.DOCKERHUB_TOKEN }} 58 | - 59 | name: Validate Build 60 | id: latestTag 61 | if: ${{ needs.checkTags.outputs.build }} == "true" 62 | run: | 63 | echo Building Version = ${{ needs.checkTags.outputs.latest_version }} 64 | echo ${{ needs.checkTags.outputs.latest_version }} > latest 65 | echo "latest_version=`cat latest`" >> $GITHUB_OUTPUT 66 | - 67 | name: Build and push 68 | id: docker_build 69 | uses: docker/build-push-action@v2 70 | if: ${{ needs.checkTags.outputs.build }} == "true" 71 | with: 72 | push: true 73 | platforms: linux/amd64,linux/arm64 74 | tags: richarvey/awscli:latest, richarvey/awscli:${{ needs.checkTags.outputs.latest_version }} 75 | - 76 | name: Image digest 77 | if: ${{ env.build == 'true' }} 78 | run: echo ${{ steps.docker_build.outputs.digest }} 79 | tag: 80 | name: Tag 81 | needs: build 82 | runs-on: ubuntu-latest 83 | steps: 84 | - 85 | name: Tag Release 86 | uses: "marvinpinto/action-automatic-releases@latest" 87 | with: 88 | repo_token: "${{ secrets.GITHUB_TOKEN }}" 89 | automatic_release_tag: "${{ needs.build.outputs.latest_version }}" 90 | prerelease: false 91 | title: "${{ needs.build.outputs.latest_version }}" 92 | files: | 93 | * 94 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | abuse@squarecows.com. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | When contributing to this repository, please first discuss the change you wish to make via issue, 4 | email, or any other method with the owners of this repository before making a change. 5 | 6 | Please note we have a code of conduct, please follow it in all your interactions with the project. 7 | 8 | ## Pull Request Process 9 | 10 | 1. Ensure any install or build dependencies are removed before the end of the layer when doing a 11 | build. 12 | 2. Update the README.md with details of changes to the interface, this includes new environment 13 | variables, exposed ports, useful file locations and container parameters. 14 | 3. Increase the version numbers in any examples files and the README.md to the new version that this 15 | Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/). 16 | 4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you 17 | do not have permission to do that, you may request the second reviewer to merge it for you. 18 | -------------------------------------------------------------------------------- /Dockerfile: -------------------------------------------------------------------------------- 1 | FROM python:3.10.10-alpine3.17 AS installer 2 | 3 | RUN apk add --no-cache \ 4 | git \ 5 | unzip \ 6 | groff \ 7 | build-base \ 8 | libffi-dev \ 9 | cmake \ 10 | bash \ 11 | curl \ 12 | jq 13 | 14 | COPY get_tags.sh /get_tags.sh 15 | RUN /get_tags.sh && export AWSCLI_VERSION=`cat releases | head -1` && git clone --recursive --depth 1 --branch ${AWSCLI_VERSION} --single-branch https://github.com/aws/aws-cli.git 16 | 17 | WORKDIR /aws-cli 18 | 19 | RUN python -m venv venv && \ 20 | . venv/bin/activate && \ 21 | scripts/installers/make-exe && \ 22 | unzip -q dist/awscli-exe.zip && \ 23 | aws/install --bin-dir /aws-cli-bin && \ 24 | /aws-cli-bin/aws --version 25 | 26 | # reduce image size: remove autocomplete and examples 27 | RUN rm -rf /usr/local/aws-cli/v2/current/dist/aws_completer /usr/local/aws-cli/v2/current/dist/awscli/data/ac.index /usr/local/aws-cli/v2/current/dist/awscli/examples 28 | RUN find /usr/local/aws-cli/v2/current/dist/awscli/data -name completions-1*.json -delete 29 | RUN find /usr/local/aws-cli/v2/current/dist/awscli/botocore/data -name examples-1.json -delete 30 | 31 | 32 | FROM alpine:3 33 | LABEL maintainer=“ric@squarecows.com” 34 | 35 | RUN apk add --update --no-cache \ 36 | less \ 37 | groff \ 38 | jq 39 | COPY --from=installer /usr/local/aws-cli/ /usr/local/aws-cli/ 40 | COPY --from=installer /aws-cli-bin/ /usr/local/bin/ 41 | 42 | RUN adduser -D -u 1000 awsuser && \ 43 | aws --version > /version 44 | 45 | WORKDIR /cfg 46 | ENV HOME=/home/awsuser 47 | USER awsuser 48 | 49 | ENTRYPOINT ["/usr/local/bin/aws"] 50 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "{}" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright 2019 Ric Harvey 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ## AWS Toolkit - [![build](https://github.com/richarvey/aws-docker-toolkit/actions/workflows/main.yml/badge.svg)](https://github.com/richarvey/aws-docker-toolkit/actions/workflows/main.yml) ![docker pulls](https://img.shields.io/docker/pulls/richarvey/awscli) ![docker version](https://img.shields.io/docker/v/richarvey/awscli?sort=semver) 2 | 3 | This is dockerized version of the awscli, which means you can run the tool without directly installing it on your system. It's simple to map your AWS credentials to this container and even set up a __.bash_profile__ so you can just type ```aws``` in the command line. The image is auto-built daily to ensure the Linux base image is constantly updated in the background and that you have the latest awscli version. 4 | 5 | I've finally made a unified version which is super slim and from version ```2.2.10``` it's a mere 97.6Mb and is based upon alpine Linux (yes all the musl libc and OpenSSL issues are taken care of) add to this it is available on both x86_64 and arm64. 6 | 7 | Tags and releases are in line with the AWS CLI version, so you can use that to pull a specific release if needed for example: ```2.2.6``` 8 | ### Why does this version exist? 9 | 10 | Amazon provides a container for this already, it's good but it weighed in a little heavy for me at ~387MB. I wanted this as small as possible and managed to shave off ~290MB on the uncompressed image. 11 | 12 | |Image | Version | Base | Size (uncomnpressed) | Size (compressed) | 13 | |---------------------|-----------------|--------------|----------------------|-------------------| 14 | | amazon/aws-cli | latest | amazon linux | 387MB | ![image size](https://img.shields.io/docker/image-size/amazon/aws-cli) | 15 | | richarvey/awscli | < 2.2.9+ | debian slim | ~178MB | ![image size](https://img.shields.io/docker/image-size/richarvey/awscli/2.2.9) | 16 | | richarvey/awscli | 2.2.10+ | alpine linux | 97.6MB | ![image size](https://img.shields.io/docker/image-size/richarvey/awscli/2.2.10) | 17 | | richarvey/awscli | 2.3.0+ | alpine linux | ~113MB | ![image size](https://img.shields.io/docker/image-size/richarvey/awscli/2.3.0) | 18 | | richarvey/awscli | latest | alpine linux | ~143MB | ![image size](https://img.shields.io/docker/image-size/richarvey/awscli) | 19 | 20 | 21 | __Why else?__ 22 | 23 | Well, I've been doing this since version 1.6.x and I trust my image builds, I know they are lightweight and no bloat. Switching from debian-slim to Alpine Linux has allowed me to make this even smaller so I'm super happy with that. 24 | 25 | ## Downloading 26 | 27 | ``` 28 | docker pull richarvey/awscli:latest 29 | ``` 30 | 31 | See all tags at [https://hub.docker.com/r/richarvey/awscli/tags/](https://hub.docker.com/r/richarvey/awscli/tags/) 32 | 33 | ## Running the toolkit in normal mode 34 | Running in the normal mode gives the CLI tools access to your current working directory and your AWS credentials (potentially ~/.aws). Its controlled by specifying _-v \`pwd\`:/cfg -v ~/.aws:/home/awsuser/.aws_ on the command line. This will be the mode used in all the examples. This is great for limiting the reach of the toolkit onto your system. You'll share your AWS credentials and the current working directory so you can use the CloudFormation file you've been working on or tell S3 to upload/download files. 35 | 36 | ## Running the toolkit in open mode 37 | To give you more access to files outside your current working directory you can swap _-v \`pwd\`:/cfg -v ~/.aws:/home/awsuser/.aws_ for ___-v ~/:/home/awsuser___. This gives docker access to your entire home directory including your docker credentials. 38 | 39 | __NOTE:__ I recommend running these as bash alias' in order to make it a smooth process of using this toolkit and save a lot of typing. 40 | 41 | #### Using the cli 42 | 43 | Run the container and map a local directory (for files you may want to use) and .aws config for credentials 44 | 45 | ``` 46 | docker run -it -v `pwd`:/cfg -v ~/.aws:/home/awsuser/.aws richarvey/awscli:latest ${COMMAND} 47 | ``` 48 | 49 | #### Switching profile 50 | 51 | Instead of including ```--profile SomeProfile``` in each command you can also use the ```-e AWS_PROFILE=SomeProfile``` in the docker command. This can be particularly useful when setting up your bash profile and allows us to use different alias' for different accounts. To run fromt he command line do the following: 52 | 53 | ``` 54 | docker run -it -e AWS_PROFILE=SomeProfile -v `pwd`:/cfg -v ~/.aws:/home/awsuser/.aws richarvey/awscli:latest ${COMMAND} 55 | ``` 56 | 57 | ## Adding to .bash_profile for :latest 58 | 59 | You can set an alias and then use awscli as normal from your shell if desired, this makes it super easy to access. 60 | 61 | ``` 62 | vi ~/.bash_profile 63 | ``` 64 | 65 | ``` 66 | aws() { 67 | docker run -it -v `pwd`:/cfg -v ~/.aws:/home/awsuser/.aws --rm richarvey/awscli:latest "$@"; 68 | } 69 | ``` 70 | 71 | Now when you call ```aws``` from the command line (don't forget to source your bash_profile) you'll have direct access to the aws command as if it were installed on your system. 72 | 73 | For advanced use and multiple profiles try something like the following: 74 | 75 | ``` 76 | vi ~/.bash_profile 77 | ``` 78 | 79 | ``` 80 | # default account 81 | aws() { 82 | docker run -it -v `pwd`:/cfg -v ~/.aws:/home/awsuser/.aws --rm richarvey/awscli:latest "$@"; 83 | } 84 | 85 | # Named profile account from .aws/config file 86 | aws_profile_name() { 87 | docker run -it -e AWS_PROFILE=SomeProfile -v `pwd`:/cfg -v ~/.aws:/home/awsuser/.aws --rm richarvey/awscli:latest "$@"; 88 | } 89 | 90 | ``` 91 | 92 | ## Building yourself 93 | 94 | The build process is now super simple and you can build using the normal docker tools: 95 | 96 | ``` 97 | docker build -t MYBUILD . 98 | ``` 99 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security Policy 2 | 3 | These images are built with minimal software installed to help ensure a smaller vunerability vector. The installed packages are: 4 | 5 | - alpine linux (base image) 6 | - awscli (from source) 7 | - less 8 | - groff 9 | - jq 10 | 11 | ## Supported Versions 12 | 13 | | Version | Supported | 14 | | ------- | ------------------ | 15 | | latest | :white_check_mark: | 16 | | ![docker version](https://img.shields.io/docker/v/richarvey/awscli?sort=semver) | :white_check_mark: | 17 | | previous tags | x | 18 | 19 | ## Reporting a Vulnerability 20 | 21 | If you spot a vulnerability that needs addressing please open an issue and we'll get onto it! Security in these images are top priority. We scan the images both on Github and Dockerhub. 22 | -------------------------------------------------------------------------------- /get_tags.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | echo "Getting all releases" 3 | curl https://api.github.com/repos/aws/aws-cli/tags | jq -r .[].name | grep -v dev > releases 4 | cat releases | head -n1 > latest 5 | 6 | -------------------------------------------------------------------------------- /latest: -------------------------------------------------------------------------------- 1 | 2.11.0 2 | -------------------------------------------------------------------------------- /releases: -------------------------------------------------------------------------------- 1 | 2.11.0 2 | 2.10.4 3 | 2.10.3 4 | 2.10.2 5 | 2.10.1 6 | 2.10.0 7 | 2.9.23 8 | 2.9.22 9 | 2.9.21 10 | 2.9.20 11 | 2.9.19 12 | 2.9.18 13 | 2.9.17 14 | 2.9.16 15 | 2.9.15 16 | 2.9.14 17 | 2.9.13 18 | 2.9.12 19 | 2.9.11 20 | 2.9.10 21 | 2.9.9 22 | 2.9.8 23 | 2.9.7 24 | 2.9.6 25 | 2.9.5 26 | 2.9.4 27 | 2.9.3 28 | 2.9.2 29 | 2.9.1 30 | 2.9.0 31 | --------------------------------------------------------------------------------