Installation
$ pip install aws-backup-clientExample
Currently, we use the following:
EC2 AMI Image
$ ec2-ami-backup --instance-id=i-xxxxxxxx --instance-id=i-yyyyyyyy \
> --instance-name=name1 --instance-name=*name2*\
> --instance-tag=key/value --instance-tag=key2/*value2* \
> --image-description='weekly backup image' \
> --image-max-number=2 \
> --image-expiration='14days' \
> --aws-access-key-id=AKIXXXXXXXXXXXXXXXX \
> --aws-secret-access-key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx \
> --aws-region=ap-northeast-1 \
> --aws-time-diff='9hours' \
> --client-time-diff='9hours' \
> --client-time-format='%Y-%m-%dT%H-%M-%S' \
> --log-level=10 \
> --reboot \
> --prefix='weekly-' \
> --dry-run
> --keep-snapshotFollowing least any one input is required:
–instance-id
–instance-name
–instance-tag
1 maintainer
Metadata
1 maintainer
Release files for aws-backup-client 0.0.6
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 | |
|---|---|---|---|---|
| aws-backup-client-0.0.6.tar.gz | 6.3 kB | Without provenance | Details |
Release files / aws-backup-client-0.0.6.tar.gz
| Download URL | aws-backup-client-0.0.6.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34b928a966a91645e44a139dec5fb40ee088cbb01262f7715f3ad482dc991587
|
|
BLAKE2b-256 checksum How to use checksums |
0b203b50a5ae54da5444ef01362ca3ec65f0dddf22d01dfcb737102424d54e04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for aws-backup-client 0.0.6
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.
