To make prebuilt SPA installers with CDK I like to keep environment configuration outside of the minified code via a config.json file. This allows me to build the app once and move it between environments and stages.
Some AWS customers don’t use the CLI, and will not grant an external contractor CLI access. Trying to get access is a waste of time and resources. Do not fear, there is a solution!
AWS Athena provides SQL queries over S3 data. The service depends on S3, Glue, and Athena itself so getting permissions set up can be tricky. Here is what worked for me.
I struggled WAY too long trying to sort out the permissions for EFS. Turns out, there are 2 layers. The IAM role, and the Posix permissions. Both throw a similar looking access denied. Finally!
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 a 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.
Writing CloudFormation or SAM templates without by hand is very powerful, but can also be quite frustrating without a good IDE setup…
My AWS Amplify + React app throws an Uncaught TypeError when running the production build, but works just fine with react-scripts start.
AWS is taking over the wold. So it’s time we had a workshop to learn it. -Damian Montero, FloridaJS
"Error: Unable to upload artifact referenced by Location parameter of resource. 'S3Uploader' object is not subscriptable."
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