By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Asset Parameters in Cloud Formation template generated by AWS CDK

0

I am attempting to use AWS CDK to create a CloudFormation template that is reusable. The template (generated from the "cdk synth" command) contains some resources, a lambda function and a custom resource to trigger the lambda function. It also contains some parameters to be fetched from the user for passing to the lambda. Since CDK generates and includes "asset" parameters like Asset for S3 Bucket, S3 Key and Artifact Hash in the template related to the Lambda assets, the template is not really reusable unless we use CDK to deploy the app. We would like to be able to use this synthesized CloudFormation template to create stacks independently. Is this possible? Is there a way to work around the Asset Parameters in the cdk app so that we can generate reusable templates? Thank you!

Topics
ServerlessComputeManagement & Governance
Tags
AWS LambdaAWS CloudFormation
Language
English
AWS-User-vnambiar
asked 2 years ago880 views
2 Answers
0

One option would be to change the way you build Lambda functions in your stack code. Instead of using new lambda.Function(), you could use lambda.fromFunctionName() or lambda.fromFunctionArn() to point to an existing Lambda function that you have uploaded previously using some other method.

However, this is not a best practice. The better practice would be to deploy the stack using AWS CodeBuild, which can run your CDK application for you in a Linux container context.

AWS
EXPERT
MichaelFischer
answered 2 years ago
  • AWS-User-vnambiar
    2 years ago

    Thank you @Michael_F! So the lambda itself should probably not be deployed as part of this stack and rather referenced by its ARN, is that right? Could you please elaborate on why this is not a best practice, and why the stack should be deployed using AWS CodeBuild? As I mentioned earlier, we're mainly interested in the template generated by "cdk synth" and would like that template to be reusable so that we can use it independently to deploy stacks in CloudFormation. We also want to make the template available through the AWS marketplace. Thanks!

0

I have pretty much the same question as I also want to use the CloudFormation template in the AWS Marketplace. I'm currently building lambdas as Assets and it's convenient, but they end up in a private stack-specific S3 bucket. My understanding is that for the lambdas to be accessible by customers deploying the template, they need to be built "out of stack" (e.g. using a build script) and uploaded to a public S3 bucket. Is that correct?

namedgraph
answered 8 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content