Capy 0.9.7 has an AWS SSM Parameter Store target adapter, not a Lambda target adapter. Use capy deploy to configure an AWS SSM target, then reference the parameters from your Lambda or task definition according to AWS’s deployment model.
For an AWS language base image that uses /lambda-entrypoint.sh, install Capy in the image and wrap that existing entrypoint. Keep the handler in CMD so the Lambda entrypoint receives it:
Set SECRETS_BLOB and PROJECT_KEY together in the function environment. capy run decrypts once during a cold start and starts the Lambda runtime with the resulting environment. It needs egress to reach the Capy service at startup.
Custom images must preserve their own runtime interface client startup command instead. See AWS container-image requirements.
For a zip build, use your build or IaC tooling to deliver values through the platform’s own configuration. Capy does not provide a Lambda-specific target in this release. Last modified on October 2, 2026
