route53-transfer
Backup and restore Route53 zones, or transfer between AWS accounts.
Installation
pip install route53-transfer
Usage
Backup a zone
Backup the example.com zone to a CSV file.
route53-transfer backup example.com backup.csv
Use STDOUT instead of a file
route53-transfer backup example.com -
Restore a zone
Restore the example.com zone from a CSV file.
route53-transfer load example.com backup.csv
Use - to load from STDIN instead.
Migrate between accounts
Use the command line switches to override the access and secret keys. Dump from one account, load into another.
route53-transfer --access-key-id=ACCOUNT1 --secret-key=SECRET dump example.com route53-transfer --access-key-id=ACCOUNT2 --secret-key=SECRET load example.com
1 maintainer
Metadata
1 maintainer
Release files for route53-transfer 0.1.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 |
|---|---|---|---|---|
| route53-transfer-0.1.1.tar.gz | 3.8 kB | Without provenance | Details for route53-transfer-0.1.1.tar.gz |
Release files / route53-transfer-0.1.1.tar.gz
| Download URL | route53-transfer-0.1.1.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
baf044da792bebcab3f824f34c17362ddda87f03e01f50a6d180ecc902b0efa0
|
|
BLAKE2b-256 checksum How to use checksums |
babd391c75ed08f4188ca7429cad48bcfe418776592b275551642844b14288fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for route53-transfer 0.1.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.
