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!
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
I am now an certified AWS Solution Architect Professional! I am very proud of this. It’s probably the most difficult test I have ever taken. 2.5 years of AWS experience and 40+ hours of training video.
CLI Assume Role with MFA (assume-role-mfa.sh)This script will assume a cross-account role using your MFA device and output the credentials into a named profile. 1234567891011121314151617181920212223#!
I am now an AWS Certified Developer - Associate! I had about 8 hours to kill so I bought some Udemy Practice Tests - a week later I had my cert! Lets talk about how moving to the cloud can save you $