The latest articles on DEV Community by Matti Mårds (@mamaar). https://dev.to/mamaar https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F201847%2Ffb2ca0d2-ec56-42c0-b24e-9123fd4e0f2b.jpeg https://dev.to/mamaar en Matti Mårds Fri, 26 Jul 2019 13:24:52 +0000 https://dev.to/mamaar/aws-cdk-4249 https://dev.to/mamaar/aws-cdk-4249 <p>I have moved my infrastructure definitions to TypeScript and enjoy having the entire stack in the same language.</p> <p>For the Lambda functions, I want to compile and bundle the code at deployment. </p> <p>I started out defining the stack using inheritance, as the CDK documentation's "Getting Started" page. This quickly showed some difficulties, as Webpack's compiler runs asynchronously, and object constructors do not. </p> <p>I changed over to a more functional approach of building the stack. Instead of inheriting from <code>cdk.Stack</code>, I instantiate it and pass the object to resources as normally.</p> <div class="ltag_gist-liquid-tag"> </div> <div class="ltag_gist-liquid-tag"> </div> <p>I have taken the same approach on a couple of custom CloudFormation resources with success. Now I am looking forward to the future of programming my AWS stack and not statically defining it.</p> aws functional typescript devops