Move Dev/QA Stacks to a different AWS Region.

[chand1012]

This should be done both for this repo and for the pre-processing stack. This will allow us to remain more organized and allow us to remove the list of state machine ARNS from the notification stack so that all production code is properly watched by the stack. Here is a list of things that will have to be done in preparation for the move.

• [ ] Stacks will have to be assigned a region in their definitions (see here and here).
• [ ] Development Stacks on us-east-1 should be deleted.
• [ ] Secrets will have to be copied over to us-east-2 (list below).
• [ ] Development URLs will have to be changed on the frontend. (After new URLs are generated by deployment).

Secrets that will need to be copied

• TWITCH_CLIENT_ID
• TWITCH_CLIENT_SECRET
• MONGODB_FULL_URI
• YT_CREDENTIALS

[chand1012]

I compared the prices and US East 1 (Virginia) and US East 2 (Ohio) cost the same.

[RusseII]

1.

Development URLs will have to be changed on the frontend. (After new URLs are generated by deployment).

Nitpick but can we call these vercel serverless functions for anything in the /api folder, and only say frontend for the actual frontend app?

2. https://github.com/pillargg/pillar.gg/blob/4fae3a97ba470a66bb4fc6fc46c907cb56aaf2d0/api/_apiUrls.js is there a reason we aren't just setting those in ENV variables vs using NODE_ENV === 'development' ?

3.

Development Stacks on us-east-1 should be deleted.

You'll need to allow the s3 buckets to be deleted via CDK before doing the cleanup