Skip to content

fix: move AWS region to ap-south-1 and make state bucket names globally unique - #1

Merged
kartikmanimuthu merged 1 commit into
mainfrom
terraform-apply
Aug 24, 2026
Merged

kartikmanimuthu merged 1 commit into
mainfrom
terraform-apply

Conversation

@kartikmanimuthu

Copy link
Copy Markdown
Contributor

What changed

  • Region: us-east-1 → ap-south-1 — all provider aliases, S3 backends, terraform.tfvars, remote-state lookups, module examples, and docs now target ap-south-1 (Mumbai), the account's preferred region.
  • State bucket names made globally unique — tfstate-<env> → tfstate-<env>-kartik-2026. The bare names were already taken by other accounts; S3 bucket names are globally unique.
  • PostgreSQL engine 16.4 → 16.15 — 16.4 is not offered in ap-south-1; 16.15 is the current available minor.
  • Network AZs updated to ap-south-1a/b/c.

Verified

  • All 10 component roots (bootstrap + dev/staging/prod × network/database/ecs) pass terraform validate.
  • terraform fmt --check clean; pre-commit hooks (fmt, validate, docs, tflint) pass.
  • Dev stack fully applied and live in ap-south-1: VPC + subnets + NAT, RDS PostgreSQL 16.15 (dev-postgres, available), ECS Fargate + ALB — ALB returns HTTP 200 with a healthy target.
  • State lives in tfstate-dev-kartik-2026.

🤖 Generated with Claude Code

…ly unique

- Switch all providers, backends, tfvars, remote-state lookups, and docs
  from us-east-1 to ap-south-1 (Kartik's preferred region).
- Rename state buckets to tfstate-<env>-kartik-2026 — the bare
  tfstate-<env> names were taken in other accounts; S3 bucket names are
  globally unique.
- Bump PostgreSQL engine_version 16.4 -> 16.15 (16.4 not offered in
  ap-south-1).
- Update network AZs to ap-south-1a/b/c.

Co-Authored-By: Claude <noreply@anthropic.com>
@kartikmanimuthu
kartikmanimuthu merged commit 4566cd8 into main Aug 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant