Decommission Shared Webmaker Infrastructure on AWS

[cadecairos]

Thimble, Goggles, Popcorn and Profile all shared the same instance and load balancer

Now that we've got Thimble, Goggles, and Popcorn on Heroku, and profile has been shut down, we can get rid of all the resources related to them on heroku.

Load balancers

• butter-production
• goggles-production
• thimble-production
• webmaker-profile2-production
• butter-staging
• goggles-staging
• thimble-staging
• webmaker-profile2-staging

Auto Scale Groups

• wmappcluster-staging-as
• wmappcluster-production-as

EC2 Security Groups

• wmappcluster

Key Pairs

• wmappcluster-03-17-2015

Launch Configurations

• wmappcluster-staging-64
• wmappcluster-production-64

RDS Instances

Don't touch these yet

• butter-production-a
  • Snapshotted
• thimble-production-a
  • Snapshotted
• goggles-production-a
  • Snapshotted
• shared-staging-a
  • Snapshotted

[jbuck]

Be careful with the RDS instances, you probably don't want to shut those
down yet...

On Tue, Oct 13, 2015 at 4:10 PM, Christopher De Cairos <
notifications@github.com> wrote:

Thimble, Goggles, Popcorn and Profile all shared the same instance and
load balancer

Now that we've got Thimble, Goggles, and Popcorn on Heroku, and profile
has been shut down, we can get rid of all the resources related to them on
heroku.
Load balancers

Auto Scale Groups

Security Groups

Key Pairs

Launch Configurations

• RDS Instances

RDS Security Groups

—
Reply to this email directly or view it on GitHub
#215.

[cadecairos]

Indeed, I hit enter on this too soon. I'm currently editing the list in the issue description, and I'll make a note of that.

[simonwex]

Related to: MozillaFoundation/plan#569

[cadecairos]

All that's left here is thimble, so I'm going to add that to the issue to decommission old thimble.