{"id":33916838,"url":"https://github.com/loong64/aws-cli","last_synced_at":"2026-06-02T00:01:14.327Z","repository":{"id":326154580,"uuid":"1102184224","full_name":"loong64/aws-cli","owner":"loong64","description":"Universal Command Line Interface for Amazon Web Services","archived":false,"fork":false,"pushed_at":"2026-05-14T21:49:39.000Z","size":9,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"master","last_synced_at":"2026-05-14T23:40:51.189Z","etag":null,"topics":["aws","cloud-aws-cli","cloud-management","loong64","loongarch64"],"latest_commit_sha":null,"homepage":"https://github.com/aws/aws-cli","language":"Dockerfile","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/loong64.png","metadata":{"files":{"readme":"README.rst","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2025-11-23T01:08:11.000Z","updated_at":"2025-11-26T04:01:57.000Z","dependencies_parsed_at":"2026-04-16T23:01:32.796Z","dependency_job_id":null,"html_url":"https://github.com/loong64/aws-cli","commit_stats":null,"previous_names":["loong64/aws-cli"],"tags_count":102,"template":false,"template_full_name":null,"purl":"pkg:github/loong64/aws-cli","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/loong64%2Faws-cli","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/loong64%2Faws-cli/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/loong64%2Faws-cli/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/loong64%2Faws-cli/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/loong64","download_url":"https://codeload.github.com/loong64/aws-cli/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/loong64%2Faws-cli/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":33798943,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-06-01T02:00:06.963Z","response_time":115,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["aws","cloud-aws-cli","cloud-management","loong64","loongarch64"],"created_at":"2025-12-12T07:32:43.245Z","updated_at":"2026-06-02T00:01:14.300Z","avatar_url":"https://github.com/loong64.png","language":"Dockerfile","funding_links":[],"categories":[],"sub_categories":[],"readme":"=======\naws-cli\n=======\n\n.. image:: https://github.com/aws/aws-cli/actions/workflows/run-tests.yml/badge.svg\n   :target: https://github.com/aws/aws-cli/actions/workflows/run-tests.yml\n   :alt: Build Status\n\n\nThis package provides a unified command line interface to Amazon Web Services.\n\nThe aws-cli package works on Python versions:\n\n* 3.9.x\n* 3.10.x\n* 3.11.x\n* 3.12.x\n* 3.13.x\n\n.. attention::\n   We recommend that all customers regularly monitor the\n   `Amazon Web Services Security Bulletins website`_ for any important security bulletins related to\n   aws-cli.\n\n Jump to:\n\n-  `Notices \u003c#notices\u003e`__\n-  `Installation \u003c#installation\u003e`__\n-  `Getting Started \u003c#getting-started\u003e`__\n-  `Getting Help \u003c#getting-help\u003e`__\n-  `More Resources \u003c#more-resources\u003e`__\n\n\n-------\nNotices\n-------\nOn 2024-11-13, support for macOS version 10.15 was dropped.\nTo use up-to-date versions of AWS CLI v2, customers using macOS 10.15 or prior\nshould upgrade to macOS 11 or later. For more information, please see\nthis `blog post \u003chttps://aws.amazon.com/blogs/developer/macos-support-policy-updates-for-the-aws-cli-v2/\u003e`__.\n\n\n------------\nInstallation\n------------\n\nAWS CLI v2 can easily be installed on most standard platforms:\n\n* `MacOS pkg installer \u003chttps://awscli.amazonaws.com/AWSCLIV2.pkg\u003e`__\n\n* `Linux x86-64 executable installer \u003chttps://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip\u003e`__\n\n* `Linux arm64 (aarch64) executable installer \u003chttps://awscli.amazonaws.com/awscli-exe-linux-aarch64.zip\u003e`__\n\n* `Windows MSI installer \u003chttps://awscli.amazonaws.com/AWSCLIV2.msi\u003e`__\n\nYou can find more detailed installation instructions `here \u003chttps://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html\u003e`__.\n\nIf you want to run the ``v2`` development branch of the CLI, see the\n\"CLI Dev Version\" section below.\n\n\n------------\nCLI Releases\n------------\n\nThe release notes for the AWS CLI can be found `here \u003chttps://github.com/aws/aws-cli/blob/v2/CHANGELOG.rst\u003e`__.\n\n\n------------------\nCommand Completion\n------------------\n\nThe aws-cli package includes a very useful command completion feature.\nThis feature is not automatically installed so you need to configure it manually.\nTo enable tab completion for bash either use the built-in command ``complete``::\n\n    $ complete -C aws_completer aws\n\nOr add ``bin/aws_bash_completer`` file under ``/etc/bash_completion.d``,\n``/usr/local/etc/bash_completion.d`` or any other ``bash_completion.d`` location.\n\nFor tcsh::\n\n    $ complete aws 'p/*/`aws_completer`/'\n\nYou should add this to your startup scripts to enable it for future sessions.\n\nFor zsh please refer to ``bin/aws_zsh_completer.sh``.  Source that file, e.g.\nfrom your ``~/.zshrc``, and make sure you run ``compinit`` before::\n\n    $ source bin/aws_zsh_completer.sh\n\nFor now the bash compatibility auto completion (``bashcompinit``) is used.\nFor further details please refer to the top of ``bin/aws_zsh_completer.sh``.\n\n---------------\nGetting Started\n---------------\n\nBefore using aws-cli, you need to tell it about your AWS credentials.  You\ncan do this in several ways:\n\n* Environment variables\n* Shared credentials file\n* Config file\n* IAM Role\n\nThe quickest way to get started is to run the ``aws configure`` command::\n\n    $ aws configure\n    AWS Access Key ID: foo\n    AWS Secret Access Key: bar\n    Default region name [us-west-2]: us-west-2\n    Default output format [None]: json\n\nTo use environment variables, do the following::\n\n    $ export AWS_ACCESS_KEY_ID=\u003caccess_key\u003e\n    $ export AWS_SECRET_ACCESS_KEY=\u003csecret_key\u003e\n\nTo use the shared credentials file, create an INI formatted file like this::\n\n    [default]\n    aws_access_key_id=foo\n    aws_secret_access_key=bar\n\n    [testing]\n    aws_access_key_id=foo\n    aws_secret_access_key=bar\n\nand place it in ``~/.aws/credentials`` (or in\n``%UserProfile%\\.aws/credentials`` on Windows). If you wish to place the\nshared credentials file in a different location than the one specified above,\nyou need to tell aws-cli where to find it.  Do this by setting\nthe appropriate environment variable::\n\n    $ export AWS_SHARED_CREDENTIALS_FILE=/path/to/shared_credentials_file\n\nTo use a config file, create a configuration file like this::\n\n    [default]\n    aws_access_key_id=\u003cdefault access key\u003e\n    aws_secret_access_key=\u003cdefault secret key\u003e\n    # Optional, to define default region for this profile.\n    region=us-west-1\n\n    [profile testing]\n    aws_access_key_id=\u003ctesting access key\u003e\n    aws_secret_access_key=\u003ctesting secret key\u003e\n    region=us-west-2\n\nand place it in ``~/.aws/config`` (or in ``%UserProfile%\\.aws\\config`` on Windows). If you wish to place the config file in a different location than the one\nspecified above, you need to tell aws-cli where to find it.  Do this by setting\nthe appropriate environment variable::\n\n    $ export AWS_CONFIG_FILE=/path/to/config_file\n\nAs you can see, you can have multiple ``profiles`` defined in both the shared\ncredentials file and the  configuration file. You can then specify which\nprofile to use by using the ``--profile`` option. If no profile is specified\nthe ``default`` profile is used.\n\nIn the config file, except for the default profile, you\n**must** prefix each config section of a profile group with ``profile``.\nFor example, if you have a profile named \"testing\" the section header would\nbe ``[profile testing]``.\n\nThe final option for credentials is highly recommended if you are\nusing aws-cli on an EC2 instance.  IAM Roles are\na great way to have credentials installed automatically on your\ninstance.  If you are using IAM Roles, aws-cli will find them and use\nthem automatically.\n\n----------------------------\nOther Configurable Variables\n----------------------------\n\nIn addition to credentials, a number of other variables can be\nconfigured either with environment variables, configuration file\nentries or both.  The following table documents these.\n\n============================= =========== ============================= ================================= ==================================\nVariable                      Option      Config Entry                  Environment Variable              Description\n============================= =========== ============================= ================================= ==================================\nprofile                       --profile   profile                       AWS_PROFILE                       Default profile name\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\nregion                        --region    region                        AWS_DEFAULT_REGION                Default AWS Region\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\nconfig_file                                                             AWS_CONFIG_FILE                   Alternate location of config\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\ncredentials_file                                                        AWS_SHARED_CREDENTIALS_FILE       Alternate location of credentials\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\noutput                        --output    output                        AWS_DEFAULT_OUTPUT                Default output style\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\nca_bundle                     --ca-bundle ca_bundle                     AWS_CA_BUNDLE                     CA Certificate Bundle\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\naccess_key                                aws_access_key_id             AWS_ACCESS_KEY_ID                 AWS Access Key\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\nsecret_key                                aws_secret_access_key         AWS_SECRET_ACCESS_KEY             AWS Secret Key\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\ntoken                                     aws_session_token             AWS_SESSION_TOKEN                 AWS Token (temp credentials)\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\ncli_timestamp_format                      cli_timestamp_format                                            Output format of timestamps\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\nmetadata_service_timeout                  metadata_service_timeout      AWS_METADATA_SERVICE_TIMEOUT      EC2 metadata timeout\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\nmetadata_service_num_attempts             metadata_service_num_attempts AWS_METADATA_SERVICE_NUM_ATTEMPTS EC2 metadata retry count\n----------------------------- ----------- ----------------------------- --------------------------------- ----------------------------------\nparameter_validation                      parameter_validation                                            Toggles local parameter validation\n============================= =========== ============================= ================================= ==================================\n\n^^^^^^^^\nExamples\n^^^^^^^^\n\nIf you get tired of specifying a ``--region`` option on the command line\nall of the time, you can specify a default region to use whenever no\nexplicit ``--region`` option is included using the ``region`` variable.\nTo specify this using an environment variable::\n\n    $ export AWS_DEFAULT_REGION=us-west-2\n\nTo include it in your config file::\n\n    [default]\n    aws_access_key_id=\u003cdefault access key\u003e\n    aws_secret_access_key=\u003cdefault secret key\u003e\n    region=us-west-1\n\nSimilarly, the ``profile`` variable can be used to specify which profile to use\nif one is not explicitly specified on the command line via the\n``--profile`` option.  To set this via environment variable::\n\n    $ export AWS_PROFILE=testing\n\nThe ``profile`` variable can not be specified in the configuration file\nsince it would have to be associated with a profile and would defeat the\npurpose.\n\n^^^^^^^^^^^^^^^^^^^\nFurther Information\n^^^^^^^^^^^^^^^^^^^\n\nFor more information about configuration options, please refer the\n`AWS CLI Configuration Variables topic \u003chttp://docs.aws.amazon.com/cli/latest/topic/config-vars.html#cli-aws-help-config-vars\u003e`_. You can access this topic\nfrom the CLI as well by running ``aws help config-vars``.\n\n\n----------------------------------------\nAccessing Services With Global Endpoints\n----------------------------------------\n\nSome services, such as *AWS Identity and Access Management* (IAM)\nhave a single, global endpoint rather than different endpoints for\neach region.\n\nTo make access to these services simpler, aws-cli will automatically\nuse the global endpoint unless you explicitly supply a region (using\nthe ``--region`` option) or a profile (using the ``--profile`` option).\nTherefore, the following::\n\n    $ aws iam list-users\n\nwill automatically use the global endpoint for the IAM service\nregardless of the value of the ``AWS_DEFAULT_REGION`` environment\nvariable or the ``region`` variable specified in your profile.\n\n--------------------\nJSON Parameter Input\n--------------------\n\nMany options that need to be provided are simple string or numeric\nvalues.  However, some operations require JSON data structures\nas input parameters either on the command line or in files.\n\nFor example, consider the command to authorize access to an EC2\nsecurity group.  In this case, we will add ingress access to port 22\nfor all IP addresses::\n\n    $ aws ec2 authorize-security-group-ingress --group-name MySecurityGroup \\\n      --ip-permissions '{\"FromPort\":22,\"ToPort\":22,\"IpProtocol\":\"tcp\",\"IpRanges\":[{\"CidrIp\": \"0.0.0.0/0\"}]}'\n\n--------------------------\nFile-based Parameter Input\n--------------------------\n\nSome parameter values are so large or so complex that it would be easier\nto place the parameter value in a file and refer to that file rather than\nentering the value directly on the command line.\n\nLet's use the ``authorize-security-group-ingress`` command shown above.\nRather than provide the value of the ``--ip-permissions`` parameter directly\nin the command, you could first store the values in a file.  Let's call\nthe file ``ip_perms.json``::\n\n    {\"FromPort\":22,\n     \"ToPort\":22,\n     \"IpProtocol\":\"tcp\",\n     \"IpRanges\":[{\"CidrIp\":\"0.0.0.0/0\"}]}\n\nThen, we could make the same call as above like this::\n\n    $ aws ec2 authorize-security-group-ingress --group-name MySecurityGroup \\\n        --ip-permissions file://ip_perms.json\n\nThe ``file://`` prefix on the parameter value signals that the parameter value\nis actually a reference to a file that contains the actual parameter value.\naws-cli will open the file, read the value and use that value as the\nparameter value.\n\nThis is also useful when the parameter is really referring to file-based\ndata.  For example, the ``--user-data`` option of the ``aws ec2 run-instances``\ncommand or the ``--public-key-material`` parameter of the\n``aws ec2 import-key-pair`` command.\n\n--------------\nCommand Output\n--------------\n\nThe default output for commands is currently JSON.  You can use the\n``--query`` option to extract the output elements from this JSON document.\nFor more information on the expression language used for the ``--query``\nargument, you can read the\n`JMESPath Tutorial \u003chttp://jmespath.org/tutorial.html\u003e`__.\n\n^^^^^^^^\nExamples\n^^^^^^^^\n\nGet a list of IAM user names::\n\n    $ aws iam list-users --query Users[].UserName\n\nGet a list of key names and their sizes in an S3 bucket::\n\n    $ aws s3api list-objects --bucket b --query Contents[].[Key,Size]\n\nGet a list of all EC2 instances and include their Instance ID, State Name,\nand their Name (if they've been tagged with a Name)::\n\n    $ aws ec2 describe-instances --query \\\n      'Reservations[].Instances[].[InstanceId,State.Name,Tags[?Key==`Name`] | [0].Value]'\n\n\nYou may also find the `jq \u003chttp://stedolan.github.com/jq/\u003e`_ tool useful in\nprocessing the JSON output for other uses.\n\nThere is also an ASCII table format available.  You can select this style with\nthe ``--output table`` option or you can make this style your default output\nstyle via environment variable or config file entry as described above.\nTry adding ``--output table`` to the above commands.\n\n\n---------------\nCLI Dev Version\n---------------\n\nIf you are just interested in using the latest released version of the AWS CLI,\nplease see the Installation_ section above.  This section is for anyone who\nwants to install the development version of the CLI.  You normally would not\nneed to do this unless:\n\n* You are developing a feature for the CLI and plan on submitting a Pull\n  Request.\n* You want to test the latest changes of the CLI before they make it into an\n  official release.\n\nThe latest changes to the CLI are in the ``v2`` branch on github.  This is\n**NOT** the default branch when you clone the git repository, so you'll need\nto make sure you ``git checkout v2``.\n\nIf you just want to install a snapshot of the latest development version of\nthe CLI, you can use the ``requirements-dev-lock.txt`` file included in this repo.\nThis file points to the development version of our dependencies::\n\n    $ cd \u003cpath_to_awscli\u003e \u0026\u0026 git checkout v2\n    $ pip install -r requirements-dev-lock.txt\n    $ pip install -e .\n\nVerify that the AWS CLI is correctly installed. Note that the word ``source`` should appear in the output::\n\n    $ aws --version\n    aws-cli/2.2.30 Python/3.8.11 Darwin/20.4.0 source/x86_64 prompt/off\n\nGenerate the autocompletion index::\n\n    $ ./scripts/gen-ac-index --include-builtin-index\n\nVerify the autocompletion index is generated by entering auto-prompt mode::\n\n    $ aws --cli-auto-prompt\n\n------------\nGetting Help\n------------\nThe best way to interact with our team is through GitHub. You can `open\nan issue \u003chttps://github.com/aws/aws-cli/issues/new/choose\u003e`__ and\nchoose from one of our templates for guidance, bug reports, or feature\nrequests.\n\nYou may find help from the community on `Stack\nOverflow \u003chttps://stackoverflow.com/\u003e`__ with the tag\n`aws-cli \u003chttps://stackoverflow.com/questions/tagged/aws-cli\u003e`__ or on\nthe `AWS Discussion Forum for\nCLI \u003chttps://forums.aws.amazon.com/forum.jspa?forumID=150\u003e`__. If you\nhave a support plan with `AWS Premium\nSupport \u003chttps://aws.amazon.com/premiumsupport\u003e`__, you can also create\na new support case.\n\nPlease check for open similar\n`issues \u003chttps://github.com/aws/aws-cli/issues/\u003e`__ before opening\nanother one.\n\nThe AWS CLI implements AWS service APIs. For general issues regarding\nthe services or their limitations, you may find the `Amazon Web Services\nDiscussion Forums \u003chttps://forums.aws.amazon.com/\u003e`__ helpful.\n\n\n--------------\nMore Resources\n--------------\n\n-  `Changelog \u003chttps://github.com/aws/aws-cli/blob/v2/CHANGELOG.rst\u003e`__\n-  `AWS CLI\n   Documentation \u003chttps://docs.aws.amazon.com/cli/index.html\u003e`__\n-  `AWS CLI User\n   Guide \u003chttps://docs.aws.amazon.com/cli/latest/userguide/\u003e`__\n-  `AWS CLI Command\n   Reference \u003chttps://awscli.amazonaws.com/v2/documentation/api/latest/reference/index.html\u003e`__\n-  `Amazon Web Services Discussion\n   Forums \u003chttps://forums.aws.amazon.com/\u003e`__\n-  `AWS Support \u003chttps://console.aws.amazon.com/support/home#/\u003e`__\n\n\n.. _`Amazon Web Services Security Bulletins website`: https://aws.amazon.com/security/security-bulletins\n.. _`download the tarball`: https://pypi.org/project/awscli/\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Floong64%2Faws-cli","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Floong64%2Faws-cli","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Floong64%2Faws-cli/lists"}