Replicated S3

I can now deploy S3 buckets that are linked and replicated.

Config updating, multiple environments

The application at this state represents (theoretically) passing in config and mutating the stack based on that.

The problem I'm running into here is simple: I have "env" config files in project-config and when I try to reference them with cdk synth -c project=$env, the cdk synth doesn't update based on the values I pass. Need to reread the articles and see what I'm missing:

• https://www.rehanvdm.com/blog/4-methods-to-configure-multiple-environments-in-the-aws-cdk
• https://xebia.com/blog/managing-multiple-environments-in-the-aws-cdk-using-yaml-configuration-files/
• https://taimos.de/blog/deploying-your-cdk-app-to-different-stages-and-environments

Full stack creation

This release represents a CDK application that can deploy the stack described in the problem prompt. It only deploys one NAT gateway, one DB, and one instance, but those values are easily updated.

The main problem I have right now is that the security groups are imprecise and are depending on the default SGs created by the constructs. The reason for this is that I'm not able to pass custom SGs from one stack to another without getting cyclic dependency warnings.