terraform-setup

Invoke the terraform-setup skill, which guides you through environment selection, IAM permission verification, repository cloning, terraform.tfvars configuration, and terraform apply. The deployment uses the aws-ecs stack with ECS Fargate and typically takes 20-30 minutes.

The deploying identity needs broad permissions including ec2, ecs, rds, docdb, s3, iam, cloudfront, secretsmanager, and others listed in the skill's IAM policy. The skill does not create these roles; it tells you what is needed and can guide you through setup.

No. The core services (registry, auth-server, mcpgw) pull pre-built images from public ECR. Docker is only needed if you enable the observability pipeline (Grafana and metrics-service images) or want to deploy custom builds.

Common causes include deploying to a region without DocumentDB support, leaving documentdb_admin_password empty, or leaving registry_name empty which crash-loops the registry container. The skill validates all of these before applying.

Yes, but this skill deploys in CloudFront-only mode by default. To use a custom domain, set enable_route53_dns to true, configure base_domain and session_cookie_domain in terraform.tfvars, and create a Route53 hosted zone.

The stack costs roughly $170-330 per month in us-east-1, dominated by Aurora, DocumentDB, ECS, and two Application Load Balancers. Running terraform destroy with the pre-destroy cleanup tears everything down.