AWS Parameter Store
Parameters store (vault) for your backend software project using AWS Parameter Store
Why AWS Parameter Store
Usually in every backend project there is a use of environment variables for holding values that can differ for each environment or need to be change from time to time. Sometimes these parameters can hold sensitive data like passwords or other secrets, there for need to be stored in a safe place.
There are some solutions for that, some of them requires setup time, knowledge and additional servers (e.g. Hashicorp Vault).
One alternative for storing such data is AWS Parameter Store, this service ia part of the AWS Systems Manager service (https://docs.aws.amazon.com/systems-manager/latest/userguide/what-is-systems-manager.html) AWS Parameter Store is a simple solution to store these parameters and tracking who change what and when.
Example
In AWS Parameter Store every parameter has a path.
Here for example we have two parameters for dev environment and two for stage.
/dev/DB_HOST
/dev/DB_USER
/dev/DB_PWD
/stage/DB_HOST
/stage/DB_USER
/stage/DB_PWD
To load parameters for dev environment see this code snippet
from awspstore import get_parameters
get_parameters(
path='dev', # Parameters path
update_environ=True, # Update the environ
dump_parameters=True # Dump all loaded parameters to standard output
)
Parameters dump into standard output. Notice tha the password is masked, by default every parameter that it's name suggesting that it contains a password or other secret will be masked.
DEBUG __init__.py(54) method: dump DB_HOST: my.awesome-db.net
DEBUG __init__.py(54) method: dump DB_USER: db_dev_user
DEBUG __init__.py(54) method: dump DB_PWD: ***********
Things to set before using
Define these environment variables:
AWS_DEFAULT_REGION = us-west-2
AWS_ACCESS_KEY_ID = AKIAIOSFODNN7EXAMPLE
AWS_SECRET_ACCESS_KEY = wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Metadata
Release files for awspstore 1.4.3
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 |
|---|---|---|---|---|
| awspstore-1.4.3.tar.gz | 4.7 kB | Without provenance | Details for awspstore-1.4.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| awspstore-1.4.3-py3-none-any.whl | Python 3 | none | any | Details for awspstore-1.4.3-py3-none-any.whl |
Total release size: 9.1 kB
Release files / awspstore-1.4.3.tar.gz
| Download URL | awspstore-1.4.3.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a90ea37ae8dab13747c287f009d772346cacce923f848d25c7253ba8c127d36f
|
|
BLAKE2b-256 checksum How to use checksums |
27003415e169186874746c56a167a6da31a0c8a11ab3c6da7b848b936225583e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / awspstore-1.4.3-py3-none-any.whl
| Download URL | awspstore-1.4.3-py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1875890d6ee85efa7e27db2918fb4723caaf448c1136d3799a44cd80bd4e4d97
|
|
BLAKE2b-256 checksum How to use checksums |
0ea40ae2d21bdec5a75ae54618befcb431b241136c1b83879621f903661dfe81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for awspstore 1.4.3
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.