service-owned-infrastructure

Structure service-owned infrastructure by creating a dedicated `infrastructure/` directory within your service repository to hold Terraform configurations. This allows service teams to version and deploy infrastructure code alongside their application code independently.

The boundary separates central platform team-managed shared resources from service-specific resources defined in the service repository. Service teams manage their own infrastructure code for service-owned resources, while the platform team handles shared platform infrastructure.

Service teams consume Terraform remote state to reference shared platform infrastructure outputs. This allows service-owned infrastructure code to integrate with central resources without requiring the platform team to manage the service-specific deployments.

Yes, service-owned infrastructure is designed to remove the bottleneck of central platform teams. It empowers service teams to manage their own infrastructure as code, enabling faster deployments and clearer ownership within their own repositories.

You should not move infrastructure as code into service repositories for shared platform resources that require centralized governance. The approach is specifically designed for service-specific resources, keeping shared infrastructure under platform team ownership.