ADO, AWS General, Environments and AWS Account Basics

This page records the basic configuration items shared across environments: the pipeline project used for automation, the AWS accounts in play, and the naming conventions used for each environment.

Environments are named consistently across tooling: dev, test, and prod. Each maps to its own AWS account and its own pipeline configuration, and no environment shares infrastructure with another.

The automation pipelines that build and deploy the example service are defined in a dedicated pipeline project. Access to trigger a deployment is limited to members of the platform team, and every run is logged with the identity of the person who triggered it.