The `aws-cdk-aws-signer` library provides AWS Cloud Development Kit (CDK) constructs for defining AWS Signer resources. It simplifies the creation and management of signing profiles, allowing you to sign code and artifacts with robust cryptographic integrity. This entry reflects version 1.204.0, part of the CDK v1 series, which typically follows a rapid release cadence with new features and bug fixes.
pip install aws-cdk-aws-signerVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to define a basic AWS Signer Signing Profile using the `aws-cdk-aws-signer` construct library. It creates a profile suitable for AWS Lambda code signing with a 30-day validity period and exports its ARN.
For CDK v2, use the `aws_cdk.aws_signer` module directly from `aws-cdk-lib`. If you must use v1, ensure your project exclusively uses v1 dependencies and syntax. Migration guides exist for moving from CDK v1 to v2.
Consult the AWS Signer documentation for a list of supported regions and ensure your CDK stack is deployed to one of them. You can specify the region when initializing your CDK stack (e.g., `cdk.Stack(app, 'MyStack', env=cdk.Environment(region='us-east-1'))`).
Always explicitly specify a valid `signer.Platform` when creating a `SigningProfile`, e.g., `platform=signer.Platform.AWS_LAMBDA_SHA384_ECDSA`. Refer to the AWS Signer documentation for available platform IDs.
Always consider and explicitly set `signature_validity` using `cdk.Duration` to match your organizational security policies and operational requirements for signed artifacts.
Ensure the package is installed: `pip install aws-cdk-aws-signer`. If using CDK v2, change the import to `from aws_cdk_lib import aws_signer` and install `aws-cdk-lib` instead.
Add the `platform` argument with a valid `signer.Platform` enum value, e.g., `platform=signer.Platform.AWS_LAMBDA_SHA384_ECDSA`.
Ensure the IAM user or role used for CDK deployment has permissions for `signer:*` actions, especially `signer:PutSigningProfile`, `signer:GetSigningProfile`, and `iam:*` for role creation. Review CloudFormation event logs for specific permission failures.