feat: add Terraform for the AWS infrastructure (Phase 7) - #9
Merged
Merged
Conversation
Provision the cloud stack as code: a production-shaped three-tier VPC (public / private-app / private-data across two AZs, single NAT), a private RDS Postgres 16 instance with no public endpoint, an S3 bucket for raw documents, and a least-privilege IAM task role scoped to the specific Bedrock models the service calls plus the one bucket. - network.tf: VPC, six subnets, IGW, single NAT gateway, route tables - rds.tf: private Postgres, security groups chained by reference, RDS-managed master password in Secrets Manager (no secret in state) - s3.tf: account-ID-named bucket with public access fully blocked - iam.tf: task role with cross-region Bedrock inference-profile scoping Verified end to end with apply -> inspect -> destroy (29 resources, zero residue). State and the provider cache are git-ignored; the provider lock file is committed for reproducible versions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Provision the cloud stack as code: a production-shaped three-tier VPC (public / private-app / private-data across two AZs, single NAT), a private RDS Postgres 16 instance with no public endpoint, an S3 bucket for raw documents, and a least-privilege IAM task role scoped to the specific Bedrock models the service calls plus the one bucket.
Verified end to end with apply -> inspect -> destroy (29 resources, zero residue). State and the provider cache are git-ignored; the provider lock file is committed for reproducible versions.