aws-ssm-copy-parameters
Copy parameters from a AWS parameter store to another
Options
usage: aws-ssm-copy [options] PARAMETER [PARAMETER ...]
positional arguments:
PARAMETER source path
optional arguments:
-h, --help show this help message and exit
--one-level, -1 one-level copy
--recursive, -r recursive copy
--overwrite, -f existing values
--keep-going, -k as much as possible, even after an error
--dry-run, -N only show what is to be copied
--source-region REGION to get the parameters from
--source-profile NAME to obtain the parameters from
--region REGION to copy the parameters to
--profile NAME to copy the parameters to
--target-path NAME to copy the parameters to
--key-id ID to use for parameter values in the destination
--clear-key-id, -C clear the kms key id associated with the parameter
--with-tags, -W copy the tags too, existing tags will be removed
Examples
Copy all parameters under /dev to a new profile:
aws-ssm-copy --profile binx-io --recursive /dev
Copy all parameters under /dev to /production, with a dry run first:
aws-ssm-copy -r --dry-run --target-path /production /dev
Read more about copying aws ssm parameters from one account to another.
Metadata
Release files for aws-ssm-copy 0.5.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 |
|---|---|---|---|---|
| aws-ssm-copy-0.5.3.tar.gz | 8.8 kB | Without provenance | Details for aws-ssm-copy-0.5.3.tar.gz |
Release files / aws-ssm-copy-0.5.3.tar.gz
| Download URL | aws-ssm-copy-0.5.3.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab4fd83109b2d7d47b53e2c7af42379b1c7b2f20ce8d1c533a87cf71b512cccd
|
|
BLAKE2b-256 checksum How to use checksums |
e65ca5e1c0e0253c5723bb9bb258acbd4907c9a078174ad00ba760e654ce7057
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.8
|
Security for aws-ssm-copy 0.5.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.