search

douglasnaphas / hatgame

A web application for virtually playing the Hat Game. Players put things into a hat, then take them out and act on them.
Apache License 2.0
0 stars 0 forks source link

Set up a separate AWS account/organization for hatgame #4

Closed douglasnaphas closed 4 years ago

douglasnaphas commented 4 years ago

It would be best to have a separate AWS account or accounts, and/or one or more AWS organizations. The goals are:

  1. Keep hatgame separate from my other applications, like Mad Liberation and CSRFX.
  2. Keep prod, test/staging, and dev resources separate from each other within an application.
douglasnaphas commented 4 years ago

I'm going to close this and not do it.

I'm not going to keep my different applications or environments in different AWS accounts.

The reason for this is that support plans are billed on a per-account basis!

The following scenario, which I would be risking if I go with a multi-account setup (which would be a prerequisite to using AWS Organizations), is unacceptable:

  1. I make an org.
  2. I have one account for hatgame, and one for Mad Liberation.
  3. I have in the future potentially many accounts for many applications.
  4. If I have an issue in an app that requires support intervention, I upgrade temporarily from Basic to Business support for that account and that account only.
  5. If in the same month I have issues in five other accounts that require support intervention, and I upgrade the corresponding accounts from Basic to Business, I would pay $600 in support fees for the month!

The benefits of separate accounts do not justify this potential cost. Note that if I don't pay the cost in the above scenario, I would risk an outage, or an impact to production apps, because I couldn't get support on them.

With all my apps in one account, I could get all the apps with issues in the above scenario with only one $100 support fee for the month.