Skip to content

AWS

AWS resources follow the same prv-{team}-{type}-{qualifier} pattern, adapted to AWS constructs.

AWS Identity Center (formerly SSO) permission sets and groups map to our role nomenclature:

prv-{owner}-role-aws-idc[-{scope}][-{env}]-{perm}
Role GroupPermission SetPurpose
prv-plt-role-aws-idc-prd-adminAdministratorAccessProduction admin
prv-plt-role-aws-idc-stg-adminAdministratorAccessStaging admin
prv-eng-role-aws-idc-dev-developerPowerUserAccessDev environment developer
prv-fin-role-aws-billing-readBillingReadOnlyBilling read-only
prv-sec-role-aws-idc-prd-readSecurityAuditAccessSecurity audit read
Role GroupPurpose
prv-plt-role-aws-org-adminAWS Organizations management
prv-fin-role-aws-org-billingOrganization billing access

AWS accounts follow this naming pattern:

{ORG}-{purpose}[-{env}]
AccountPurpose
prv-rootManagement account (Organizations root)
prv-securitySecurity tooling (GuardDuty, SecurityHub)
prv-loggingCentralized logging
prv-shared-servicesShared infrastructure
prv-workloads-prdProduction workloads
prv-workloads-stgStaging workloads
prv-workloads-devDevelopment workloads
prv-sbxSandbox/experimentation

All AWS resources should be tagged with standard keys:

Tag KeyExample ValuePurpose
orgprvOrganization identifier
teamplt, eng, secOwning team
envprd, stg, dev, sbxEnvironment
purposeci-runner, monitoringWhat this resource does
cost-centerplt, engChargeback/showback
prv-plt-admin-aws@{domain}

The AWS root account email. Credentials in vault with two-person access. Used only for:

  • Initial Organizations setup
  • Emergency breakglass
  • Account recovery

Day-to-day admin work goes through Identity Center with time-boxed role grants.

  • Never use the root account for daily operations.
  • All access via Identity Center role groups.
  • Production admin roles time-boxed to 30 days max.
  • Billing access separate from infrastructure access.
  • All accounts in Organizations (no standalone accounts).