Certificate Uploader
Upload ACM/IAM Server Certificates and apply them to ELBs
Requirements
Python 2.7 or 3.6
Installation
pip install cert-uploader
Usage
Help Text
cert-uploader --help
cert-uploader iam --help
cert-uploader acm --help
IAM
Scan for certificates in the current directory and upload to IAM:
cert-uploader --scan \
iam \
--certificate-name cert-name
Upload a new certificate to IAM:
cert-uploader --certificate-path path/to/certificate.crt \
--private-key-path path/to/key.pem \
--certificate-chain-path path/to/chain.crt \
iam \
--certificate-name cert-name
Upload a new certificate to IAM and assign it to a load balancer:
cert-uploader --certificate-path path/to/certificate.crt \
--private-key-path path/to/key.pem \
--certificate-chain-path path/to/chain.crt \
--load-balancer load-balancer-name \
iam \
--certificate-name cert-name
Upload a new IAM certificate at the path "/test" and assign it to a load balancer:
cert-uploader --certificate-path path/to/certificate.crt \
--private-key-path path/to/key.pem \
--certificate-chain-path path/to/chain.crt \
--load-balancer load-balancer-name \
iam \
--certificate-name cert-name \
--iam-path /test
Upload a new IAM certificate and assign it to a load balancer on port 8443:
cert-uploader --load-balancer load-balancer-name \
--port 8443 \
--certificate-path path/to/certificate.crt \
--private-key-path path/to/key.pem \
--certificate-chain-path path/to/chain.crt \
iam \
--certificate-name cert-name
Assign an existing IAM certificate to a load balancer:
cert-uploader --load-balancer load-balancer-name \
iam \
--certificate-name cert-name
ACM
Scan for certificates in the current directory and upload to ACM:
cert-uploader --scan \
acm \
--region region-name
Upload a new certificate to ACM:
cert-uploader --certificate-path path/to/certificate.crt \
--private-key-path path/to/key.pem \
--certificate-chain-path path/to/chain.crt \
acm
Upload a new certificate to ACM and add tags:
cert-uploader --certificate-path path/to/certificate.crt \
--private-key-path path/to/key.pem \
--certificate-chain-path path/to/chain.crt \
acm \
--tag Name=cert \
--tag App=app1
Upload a new certificate to ACM and assign it to a load balancer:
cert-uploader --certificate-path path/to/certificate.crt \
--private-key-path path/to/key.pem \
--certificate-chain-path path/to/chain.crt \
--load-balancer load-balancer-name \
acm \
--tag Name=cert \
--tag App=app1
Upload a new ACM certificate and assign it to a load balancer on port 8443:
cert-uploader --load-balancer load-balancer-name \
--port 8443 \
--certificate-path path/to/certificate.crt \
--private-key-path path/to/key.pem \
--certificate-chain-path path/to/chain.crt \
acm
Assign an existing ACM certificate to a load balancer:
cert-uploader --load-balancer load-balancer-name \
acm \
--certificate-arn arn:aws:acm:REGION:ACCOUNT:certificate/CERTIFICATE_ID
Credentials
Profile
AWS credentials can be passed in using the --profile command line argument:
cert-uploader --certificate-path path/to/certificate.crt \
--private-key-path path/to/key.pem \
--certificate-chain-path path/to/chain.crt \
--profile profile-name \
acm
or by setting the AWS_PROFILE environment variable:
export AWS_PROFILE=profile-name
cert-uploader --certificate-path path/to/certificate.crt \
--private-key-path path/to/key.pem \
--certificate-chain-path path/to/chain.crt \
acm
Access Keys
If a profile is not configured, the AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_DEFAULT_REGION
environment variables can be set and used for authentication.
Roles
Roles can be assumed using the --role command line argument:
cert-uploader --certificate-path path/to/certificate.crt \
--private-key-path path/to/key.pem \
--certificate-chain-path path/to/chain.crt \
--role role-arn \
acm
Metadata
Release files for cert-uploader 1.1.12
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 |
|---|---|---|---|---|
| cert-uploader-1.1.12.tar.gz | 11.9 kB | Without provenance | Details for cert-uploader-1.1.12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cert_uploader-1.1.12-py2-none-any.whl | Python 2 | none | any | Details for cert_uploader-1.1.12-py2-none-any.whl |
Total release size: 26.1 kB
Release files / cert-uploader-1.1.12.tar.gz
| Download URL | cert-uploader-1.1.12.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
028cc0f5aad1096a76e47a0b8fcc4afcf5796bf35f8d88b41a9dbbe3460ada0d
|
|
BLAKE2b-256 checksum How to use checksums |
13b6c2b34c451b1a0e600296f7bebdb1a2bb32081ad87a41746655cf67d0892e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/2.7.15
|
Release files / cert_uploader-1.1.12-py2-none-any.whl
| Download URL | cert_uploader-1.1.12-py2-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
2136d9436e420f53a9e9738508c95cef361e6f5c54a69f94b4602a0b7db598dd
|
|
BLAKE2b-256 checksum How to use checksums |
657d88e9b7a8f773c9b46d4f4c0af6d31fb1657dd28267b9989c73a146ba9621
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/2.7.15
|
Security for cert-uploader 1.1.12
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.