We occasionally have a client who does not allow us to create IAM roles in their AWS account. In this scenario we must define the roles in CloudFormation, they create them, and we inject the role ARNs
When updating a lambda with a DynamoDB Streams event source I got a mapping already exists error
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…
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.
My AWS Amplify + React app throws an Uncaught TypeError when running the production build, but works just fine with react-scripts start.
While working on a multi-stack AWS SAM package I came across this rather obscure error: Error: Unable to upload artifact ../../spa-hosting.yaml referenced by Location parameter of Hosting resource. ‘S3Uploader’ object is not subscriptable