AWS::Signer Construct Library
---AWS CDK v1 has reached End-of-Support on 2023-06-01. This package is no longer being updated, and users should migrate to AWS CDK v2.
For more information on how to migrate, see the Migrating to AWS CDK v2 guide.
AWS Signer is a fully managed code-signing service to ensure the trust and integrity of your code. Organizations validate code against a digital signature to confirm that the code is unaltered and from a trusted publisher. For more information, see What Is AWS Signer?
Table of Contents
Signing Platform
A signing platform is a predefined set of instructions that specifies the signature format and signing algorithms that AWS Signer should use to sign a zip file. For more information go to Signing Platforms in AWS Signer.
AWS Signer provides a pre-defined set of signing platforms. They are available in the CDK as -
Platform.AWS_IOT_DEVICE_MANAGEMENT_SHA256_ECDSA
Platform.AWS_LAMBDA_SHA384_ECDSA
Platform.AMAZON_FREE_RTOS_TI_CC3220SF
Platform.AMAZON_FREE_RTOS_DEFAULT
Signing Profile
A signing profile is a code-signing template that can be used to pre-define the signature specifications for a signing job. A signing profile includes a signing platform to designate the file type to be signed, the signature format, and the signature algorithms. For more information, visit Signing Profiles in AWS Signer.
The following code sets up a signing profile for signing lambda code bundles -
signing_profile = signer.SigningProfile(self, "SigningProfile",
platform=signer.Platform.AWS_LAMBDA_SHA384_ECDSA
)
A signing profile is valid by default for 135 months. This can be modified by specifying the signatureValidityPeriod property.
Metadata
Release files for aws-cdk.aws-signer 1.204.0
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-cdk.aws-signer-1.204.0.tar.gz | 52.8 kB | Without provenance | Details for aws-cdk.aws-signer-1.204.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aws_cdk.aws_signer-1.204.0-py3-none-any.whl | Python 3 | none | any | Details for aws_cdk.aws_signer-1.204.0-py3-none-any.whl |
Total release size: 104.5 kB
Release files / aws-cdk.aws-signer-1.204.0.tar.gz
| Download URL | aws-cdk.aws-signer-1.204.0.tar.gz |
|---|---|
| Size | 52.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e2d191abd777271382c25b5bfc16390a214a8f0a463c4a17c8b4c0034bcf4f3
|
|
BLAKE2b-256 checksum How to use checksums |
a7dac278294f923c80b28c81d76450acfdbf5be6cd308e54f154a9551f9b1b39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / aws_cdk.aws_signer-1.204.0-py3-none-any.whl
| Download URL | aws_cdk.aws_signer-1.204.0-py3-none-any.whl |
|---|---|
| Size | 51.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9bd890b572d139c6ba4973394dc5e17699a50c6f150712faa1305a8f1b3c16cb
|
|
BLAKE2b-256 checksum How to use checksums |
2cef4f8b3e3fca2b2e3ded552c688882f36d280d4265e07e6ed011cf1af94698
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for aws-cdk.aws-signer 1.204.0
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.