# AWSC - AWS Commander
AWSC is a tool inspired by [k9s](https://github.com/derailed/k9s) - the goal is to create a similarly easy to use terminal-based UI for the AWS API.
## Installation
### Requirements
AWSC has been tested with and therefore requires python 3.8 or later.
### Stable releases
AWSC is available on pypi and can be installed via pip.
`bash $ pip3 install awsc ``
### Edge versions
You can install the latest git revision from the root directory of the repository by issuing:
`bash $ sudo python3 setup.py install `
## First use
Through either installation method, the awsc binary should become available.
Upon launching AWSC, you are prompted to set an encryption key (password) for your database of access credentials. You will have to enter this encryption key every time you launch AWSC.
You will then be taken to the list of AWS contexts and you should see an empty list. You can either add a new context by pressing a - you’ll have to add your access and secret key manually; or you can import the current AWS CLI context by pressing i.
For navigation , refer to the top right hotkey display on each screen.
### Command palette
The command palette can be accessed by pressing :. This allows you to navigate between the different AWS resources. Most resources have short names that are accepted, but the full name of the resource without spaces should also be accepted. For an exhaustive list of commands that are available, type ‘help’ and press enter.
### Defaults
You can configure a default context, region and ssh key in their relevant screens. These are remembered and automatically set on each launch. Your default SSH key is only used if the keypair for the instance you are accessing does not already have an associated SSH key.
## Version history
Refer to the [changelog](CHANGELOG.md) for release notes on versions.
Metadata
Release files for awsc 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| awsc-0.3.1.tar.gz | 53.1 kB | Without provenance | Details for awsc-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| awsc-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for awsc-0.3.1-py3-none-any.whl |
Total release size: 145.8 kB
Release files / awsc-0.3.1.tar.gz
| Download URL | awsc-0.3.1.tar.gz |
|---|---|
| Size | 53.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2c2665828d57d23d11f642a32984555517934aba2a8e65d1835b91ceeef3cb1
|
|
BLAKE2b-256 checksum How to use checksums |
1bc5ed2956df975e554e04fcf7c6f0f53e403da9c5b99438d6e3e5a171e0d5cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.8
|
Release files / awsc-0.3.1-py3-none-any.whl
| Download URL | awsc-0.3.1-py3-none-any.whl |
|---|---|
| Size | 92.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
778c08cf9dfef447e129019f87c834a93b3d3e7b4e8119a91613390eca22c2e7
|
|
BLAKE2b-256 checksum How to use checksums |
c6037774e7b882f50b25ab7e5ed6efbcda7022a0c4cbdd7fdd4a37be8b15ad2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.8
|
Security for awsc 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.