Prog Strength Infra
Prog-Strength/prog-strength-infra
IaC Terraform completo para rastreador de musculação AI
Ver no GitHubMCP server que fornece toda a infraestrutura como código (Terraform + HCL) para provisionar o backend do Prog Strength, um rastreador de levantamento AI-nativo. Inclui configuração completa de EC2, VPC, S3 para state, IAM e backup com Litestream, pronto para deploy em produção via GitHub Actions.
Instalação
npx convez-ai Prog-Strength/prog-strength-infra1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Provisionar infraestrutura backend do Prog Strength do zero
- Gerenciar estado Terraform centralizado em S3 com CI/CD
- Configurar rede, compute e backup em AWS de forma reproducível
Veredito

Projeto maduro de IaC com boas práticas (state remoto, CI/CD via GitHub Actions, backup com Litestream). Essencial para quem quer reproduzir o Prog Strength ou aprender arquitetura Terraform para aplicações AI.
README
A tradução para o português deste README ainda está na fila.
prog-strength-infra
Terraform configuration for the Prog Strength backend host (single EC2 instance behind an Elastic IP, in a dedicated VPC with a public subnet). State lives in S3 with native S3 lockfile-based locking.
Bootstrap (already done)
The S3 backend bucket and the IAM user that CI uses are provisioned manually and live outside this repo:
- State bucket:
prog-strength-terraform-backend(us-east-2) - State key:
prod/terraform.tfstate - IAM user: credentials are wired into GitHub Actions via repo secrets.
Required GitHub secrets
CI authenticates to AWS via the IAM user's static keys:
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEY
Local development
terraform init
terraform plan -var-file=environments/prod.tfvars
Applying locally bypasses the PR review path enforced by CI. Prefer the GitHub Actions workflow: open a PR, review the plan, merge to apply.
Variables
Inputs are grouped into four object-typed variables in variables.tf. The operator-facing
overrides for prod live in environments/prod.tfvars.
project
| Field | Default | Notes |
|---|---|---|
name | prog-strength | Used for tags and the name_prefix local. |
environment | prod |
aws
| Field | Default | Notes |
|---|---|---|
region | us-east-2 | |
availability_zone | us-east-2b | Single AZ — no multi-AZ in v1. |
network
| Field | Default |
|---|---|
vpc_cidr | 10.0.0.0/16 |
public_subnet_cidr | 10.0.1.0/24 |
compute
| Field | Default | Notes |
|---|---|---|
instance_type | t4g.small | Graviton; AMI must match arm64. |
ami_name_pattern | Ubuntu 24.04 noble arm64 (gp3) | Filter passed to aws_ami data source. |
ami_owner | 099720109477 (Canonical) | |
ssh_key_name | prog-strength-backend-prod-keys | Key pair must already exist in EC2. |
root_volume_size | 8 | GiB; gp3 encrypted root. |
security_group.ingress_rules | [] | Set in environments/prod.tfvars. SSH/80/443 by default. |
The instance also gets the IAM instance profile produced by the backup
module attached automatically (see main.tf) so on-host services like
Litestream can call AWS without static keys.
backup
Litestream replica bucket + IAM role/policy. Owned by modules/backup/.
| Field | Default | Notes |
|---|---|---|
bucket_name | prog-strength-database-backups | Globally-unique S3 name. Referenced from the backend host's .env. |
noncurrent_version_expiration_days | 30 | Lifecycle rule on the versioned bucket; bounds storage cost. |
The bucket is private (public access fully blocked), versioned, and
SSE-S3 encrypted. The associated IAM role grants s3:Get/Put/Delete/List
on this bucket only and is exposed via an instance profile attached to
aws_instance.backend.
Outputs
| Output | Use |
|---|---|
instance_public_ip | Paste into the registrar's DNS A record for api.progstrength.fitness. |
instance_public_dns | EIP-derived public DNS name. |
instance_id | For SSM, console links, etc. |
vpc_id | |
public_subnet_id | |
security_group_id | |
litestream_bucket_name | Set as LITESTREAM_REPLICA_BUCKET in the backend host's .env. |
api_instance_profile_name | Visibility only — already wired into aws_instance.backend. |
After apply:
terraform output instance_public_ip