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!
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…
Writing CloudFormation or SAM templates without by hand is very powerful, but can also be quite frustrating without a good IDE setup…
AWS is taking over the wold. So it’s time we had a workshop to learn it. -Damian Montero, FloridaJS
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#!
Unlike an embarrassing Facebook post, developers can’t simply say “That wasn’t me, I got hacked” and expect it all to go away… Sarcasm aside, security without passwords is not only convenient, it keeps the password from landing in the wrong hands.
Effort is not work. Carrying a piano up the stairs is the same amount of work as using an elevator, but tremendously more effort. Your focus should be on delivering quality code, not the intricacies of deployments. It should be as easy as: Deploy Infrastructure Deploy Code Repeat as necessary