Tear down Moped test deployment resources

[mddilley]

To comply with the BitSight security recommendations, we've been told that we need to add security headers to our Moped test deployment. Since we don't use this deployment anymore, we should tear down the remaining pieces of it so this item will drop off our list from ISO.

See this doc for more details.

• [x] Remove record in Route53
• [x] Remove CloudFront distribution that it points to
• [x] Remove secrets entry - might be worth checking the repo for references, but this mentions Heroku so it feels very outdated
  • Another secret that looks outdated and removable - also has a Heroku endpoint in the secret
• [x] While we are at it, this prod SQS secret and this staging SQS secret are also outdated. We no longer use SQS for any of our applications.
• [x] Anything else?

[frankhereford]

Hey @mddilley 👋

All of this is done. The four secrets that you identified in the issue have been scheduled for deletion in 7 days. It's kinda cool - the secrets manager makes you have a test period while it won't respond, but still remembers the data.

Thanks for your time today this afternoon. When I called you, I had given myself the wrong understanding that this work was related to when you and i worked on the moped test deployment pipeline. I 100% see now that -- of course -- this is all about the ISO's request.

Last thing - I'm going to add you to this issue right before I close it because you totally did all the work -- allll of the work -- when you scoped it. It's the perfect check-list, and thanks for letting me do it! 🙏

Anything else?

Nothing else comes to mind that is lingering cruft, but I'll let you know if anything comes to mind.

[frankhereford]

There was something else. I just removed (after making a final snapshot) the RDS instance that served as the database for our moped test deployments. 👋

[frankhereford]

Found another item -- the VPC itself. vpc-080460d8b02988e02 / moped-test. I spoke with @mddilley and I'm going to run this one down next sprint or this one if i get my plate cleared. 😅 Thanks Mike!

[mddilley]

@frankhereford I was going through my notes from the week, and it reminded me that we talked about CloudFormation in relation to zappa during refinement the other day. Then, I realized that we used it in the Moped test deployments so I'm linking some more things that could be from the original Heroku test deployment or the newer full stack ones that we worked on.

• [x] CloudFormation stack
  • This stack could help point to some resources that it created
• [x] API Gateway
• [x] Lambda
• [x] IAM user
• [x][x][x] Maybe some IAM roles too

[frankhereford]

Thanks again @mddilley for the superb list. I got everything you listed. That was very helpful to see the CloudFormation stack. It was also interesting to get into the API gateway, if only to remove things, because there is a lot in there we don't use that looks useful to me. Thanks again!