7 express infrastructure resources as terraform

[jaylong255]

Ticket(s)

1. https://github.com/jaylong255/cyberworld-site/issues/7

Related PR(s)

1. #0

Changes

1. Adds a Terraform module that expresses the unique AWS resources used to serve a static frontend from an s3 bucket behind a CloudFront CDN
2. Launches a staging environment for the CyberWorld static frontend
3. Adds a CI/CD pipeline that uses a GitHub Action that interfaces with Terraform Cloud to manage environments in AWS through pull requests related to code stored in the terraform subfolder.

Checklist

• [x] PR Name: Please name this PR in format of [TICKET_ID]: [BRIEF DESCRIPTION]. For example: MONO-0000: Implement component X to use with Y
• [x] Ticket(s) and Related PR(s): Add the tickets that this PR will resolve once merge. You can also add a list of related PR(s); this is useful when to communicate that another PR must be reviewed first.
• [x] Change Description: Please update the above change list to provide a list of changes done. This will be added to the commit when merged for a useful commit description.
  • This can be omitted in the rare case that the PR is very small and the title alone clearly explains what it does.
• [x] Tests: All code should have strong tests. If you have questions about this please ask one of the code owners. All tests need to pass CI for all test matrix combinations for your PR to be considered for merge.
• [x] Code Owner Review: Please add at least one repository code owner as a reviewer. You are welcome to add anyone else you'd like feedback from.
• [x] Squash Commit with Details: It's hard to keep a perfect commit record so we prefer squash commits. When doing squash commits the commit name should auto fill the the PR name (formatted as defined in the PR Name section above) plus (#123) where the number is the PR number. Set the commit paragraph text to be the changes list above (don't include "Changes" header, just the list).

[jaylong255]

@diego3158 this pr is super-badass. Typically, a repo for a static frontend like this just has the application code. Often if a frontend developer wants to show off their ability to work beyond frontend, they will set up a deployment pipeline. Since I have a background as a Cloud Architect, I'm pretty familiar with Infrastructure as Code (IaC). Specifically Terraform. What I've done here is package in the Terraform code that manages actual infrastructure resources in AWS. So not only can you review and track the code that powers the app. You can actually review and track the code that expresses the infrastructure resources that the app is deployed to.

I'll add some comments on the Terraform code, too to explain what all we're launching. It's actually not that complicated. It's only 5 resources total, and some of those are security policies that allow and limit access. There's only 2 you should care about at first: the bucket and the CDN.