Help: Logical ID Changed in my CDK App
I recently came across a weird error in a private package CDK deployment: {dynamo table name} already exists in stack {current stack arn} Upon further investigation it turned out t
I recently came across a weird error in a private package CDK deployment: {dynamo table name} already exists in stack {current stack arn} Upon further investigation it turned out t
I recently discovered the Electron React Boilerplate project and wanted to use the AWS Amplify Authenticator. Lo and Behold: it’s ugly…
Update 2/7/2022: Read Synth CDK app to Custom Bucket instead. Consulting requires you to work within the client’s parameters. Some clients have internal standards and want you to deliver your white-label CDK app as CloudFormation. Call me old fashioned but…
I was deploying an IAM user policy using AWS CloudFormation and granted CRUD access to the bucket, but the user could not rename or move a file using the web console.