AWS Accounts Setup

The example service runs across a small set of dedicated AWS accounts, one per environment tier plus a shared services account for logging and image distribution. Each account is provisioned through the same bootstrapping process so that guardrails stay consistent.

Account identifiers, role names, and region selections are treated as configuration rather than being hard-coded into any pipeline. Placeholders such as <account-id> and <region> are used throughout this documentation in place of real values.

New accounts are enrolled into central billing and logging before any workload is deployed into them, and access is granted through federated roles rather than long-lived credentials.