AWSLive-testedattested

ECS Fargate Service

Full Fargate stack: cluster, task definition, service with ALB integration, autoscaling, and Cloud Map discovery.

terraformAWSaws

Compare Serverless Containers across clouds →

Part of: AWS Production Landing Zone

aws-ecs-fargate-servicevizier v1.2.0

Verification

Live-tested

Really deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.

Conformance

  • Static validation (fmt · validate · tflint)
  • Security scan clean (Checkov)
  • Plan test superseded by live test

Provenance

Functional

  • Live-tested - applied, verified, destroyed

Last verified 2026-06-11 · how we verify

Verify this download

cosign · sha-256

Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.

# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub

# 2. This module's Sigstore bundle
curl -o aws-ecs-fargate-service-1.0.0.sigstore.json \
  https://www.iac-bazaar.com/api/artifacts/aws-ecs-fargate-service/signature

# 3. Verify the tarball you downloaded
cosign verify-blob \
  --key cosign.pub \
  --bundle aws-ecs-fargate-service-1.0.0.sigstore.json \
  aws-ecs-fargate-service-1.0.0.tar.gz
# → Verified OK

# 4. (optional) confirm the checksum too
echo "1087200b6d95b7776393d456d941dde2c0141079aa08dda85e532cc93eb2f4c7  aws-ecs-fargate-service-1.0.0.tar.gz" | sha256sum -c

Use it from the registry

terraform · opentofu
module "ecs_fargate_service" {
  source  = "www.iac-bazaar.com/iac-bazaar/aws-ecs-fargate-service/aws"
  version = "1.0.0"
}

Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.

Cite it in your README

badge · attribution

Paste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.

README.md, GitLab, Gitea
[![IaC Bazaar: live-tested](https://www.iac-bazaar.com/api/artifacts/aws-ecs-fargate-service/badge)](https://www.iac-bazaar.com/catalog/aws-ecs-fargate-service?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Terraform module 1.0.0, live-tested on IaC Bazaar: [ECS Fargate Service](https://www.iac-bazaar.com/catalog/aws-ecs-fargate-service?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

```hcl
module "ecs_fargate_service" {
  source  = "www.iac-bazaar.com/iac-bazaar/aws-ecs-fargate-service/aws"
  version = "1.0.0"
}
```

Preview:IaC Bazaar: live-tested

Inputs & outputs

Create a free account to read this module's contract

The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.

A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.

Documentation

aws-ecs-fargate-service

Full Fargate stack: cluster, task definition, service with ALB integration, autoscaling, and Cloud Map discovery. Works with Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.

What you get (and why it is worth paying for):

  • The container definition is built from typed variables and jsonencoded once — no hand-rolled JSON, no task-definition drift between plans
  • Private networking by default (no public IP), scoped security group using modern standalone rule resources, all-egress only where required
  • Least-privilege IAM: execution role gets secret-read access to exactly the ARNs you inject; separate task role for application permissions
  • Deployment circuit breaker with automatic rollback
  • Target-tracking autoscaling (CPU and/or memory) with desired_count handed over to the scaler after first deploy (ignore_changes)
  • Optional Cloud Map (A records) for east-west discovery
  • Container Insights + retention-managed, optionally KMS-encrypted logs

Requirements

  • Terraform or OpenTofu >= 1.6
  • AWS provider >= 6.0, < 7.0
  • An existing VPC + subnets; an existing ALB target group if you set load_balancer (pair with the aws-alb module); an existing Cloud Map private DNS namespace if you set service_discovery

License

Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).

Usage code & full reference need an account

The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.

  • Usage
  • Inputs
  • Outputs
  • Notes

Related modules

Static validatedLive test pending

aws-app-runner

auto_deployments takes every push to the image tag straight to production with no review, which quietly makes the deployment gate "who can push". Off by default, egress routed through your VPC, and the pull role kept separate from the run role.

View module
Static validatedLive test pending

aws-amplify-app

Every branch build is served at a public amplifyapp.com URL, and basic auth, the switch that puts a password on it, is off; auto branch creation builds every branch anyone pushes; the repository token lands in state; and environment variables are plaintext. Basic auth on every non-production branch (public by name), auto creation off, exactly one production branch, the custom domain attached.

View module
Live-tested

aws-lambda

Lambda with execution role, log group, triggers, aliases, and zip/container packaging handled.

View module
Live-tested

aws-step-functions

A Step Functions state machine (STANDARD or EXPRESS) with a least-privilege execution role, a managed CloudWatch log group, X-Ray tracing, and encryption at rest - working out of the box from a single name.

View module
Static validatedLive test pending

ibm-code-engine-app

A Code Engine project and application with managed_domain_mappings local_private, because the field defaults to local_public and an application deployed with no opinion about it answers the world. scale_min_instances is one rather than zero, run_as_user is not root, and a private image without its pull secret is refused - that failure otherwise arrives long after the apply.

View module
Static validatedLive test pending

oci-container-instances

A container with no health check is restarted only when its process exits, so a deadlocked one stays; containers run as root unless the security context says otherwise; and a public IP on the instance is an internet-facing container with only an NSG in front. Every container gets a check that restarts it and runs non-root on a read-only filesystem; the instance stays private.

View module