7 Platform Control Plane Foundations
This chapter covers
- Managing Cloud Account Baseline Settings
- Defining the Transit Network Layer
- Separating Customer Identity
- Deploying the Cloud Service Control Plane
Previously, we started building the Epetech engineering platform by gathering the required resources. We also bootstrapped the initial pipeline, which manages the service accounts and roles that we will use in our infrastructure pipelines. We had to run the configuration from our laptops initially to create the service accounts and the role to manage permissions. But from this point on, both are now managed directly by the pipeline whenever we make changes to the repository. We began with the same developer tools we will provide our internal customers, like source control, secrets management, and pipeline orchestration. Remember that our goal in this section of the book will be to establish the foundation for the Epetech engineering platform. With the initial bootstrap of the IAM roles pipeline, we can proceed to the foundational components of the platform. The overall product goal for our engineering platform is to provide Epetech developers access to all the resources they need to build, release, and operate software independently, without the usual engineering friction. Every component of our platform needs to be resilient. This goes beyond merely including redundancy to minimize the impact of failure.