Skip to content

accounts

Eric Odell edited this page Mar 17, 2020 · 104 revisions

Amazon Web Services Accounts

Why do we use AWS Accounts?

  • to deliver secure, cost effective, efficient, reliable and useful products

How do we use AWS Accounts to deliver secure, cost effective, efficient, reliable and useful products?

  • Through automation using a devsecops shared responsibility model

What is a product team?

  • A product team is a group of people that support a product owned by a product owner.
  • Be nice to them, they can make your bacon.

Will we have an account strategy?

  • Yes. As detailed in this document.

How will our cloud strategy be enforced?

  • With automation using something like this
  • Through standard request process.

Will our account strategy be consistent with Well architected framework?

  • Yes

Will this document be consistent with our Cloud Strategy Document?

  • Yes

Will our cloud strategy be consistent with Control Tower?

  • Yes by adopting the use of Control Tower ASAP

What is the exception process?

Why do we need an account strategy document?

  • To create ordered, reusable, governed, secure, cost effective, reliable and efficient deployment of resources that create useful products. The alternative leads to poor hygiene.

Will we use a single AWS Account?

  • No

Will we use a multi-account strategy?

  • Yes

Why use a multi-account strategy?

  • limit complexity for each product team
  • provide separation of product teams
  • provide easy cost per product team

Will our account strategy provide applications inventory

  • NO, unless applications are placed in separate accounts

Will our account strategy provide portability of applications?

  • NO, unless applications are placed in separate accounts

Will our account strategy enforce application independence

  • NO, unless applications are placed in separate accounts

Will our account strategy provide ease of application retirement

  • NO, unless applications are placed in separate accounts

What is our multi-account strategy for product teams and their products?

development and production

Will we support recharge?

Never! Accounts are single payer, we will not support recharge to more than one payment stream for an account

What is our multi-account strategy for core services?

Shared core service accounts

Clone this wiki locally