Before we can build and deploy our cloud-native components we need to build and deploy the cloud accounts that they will run in. Far too often insufficient attention is paid to the architecture of cloud accounts. As we discussed in Chapter 2, The Anatomy of Cloud Native Systems, there is a great deal of thought that needs to put into the design of cloud accounts to ensure proper bulkheads. We certainly need to have separate accounts for production and development. In production, components could be spread across multiple accounts, such as separate accounts for front-office and back-office components. To support regulatory compliance, while also minimizing the scope of compliance, we may isolate certain components with higher sensitivity to their own accounts with additional access restrictions and procedures. A master account for consolidated billing is always recommended, as is a separate recovery account, as we will discuss later in the Disaster recovery section.
Once we...