chore: health check matcher support to 204 no content

[tataihono]

Closes AI-6

Add support for custom health check matcher in ECS task module and update CMS service to use "204" matcher.

Changes

• Add health_check_matcher as optional variable in ECS task module (default: "200")
• Apply matcher to ALB target group resource
• Update CMS service config to use "204" matcher

[linear]

AI-6 Add health check matcher support to ECS task module

[infracost]

💰 Infracost report

Monthly estimate generated

Estimate details (includes details of unsupported resources)

Key: * usage cost, ~ changed, + added, - removed

──────────────────────────────────
Key: * usage cost, ~ changed, + added, - removed

*Usage costs can be estimated by updating Infracost Cloud settings, see docs for other options.

912 cloud resources were detected:
∙ 126 were estimated
∙ 784 were free
∙ 2 are not supported yet, see https://infracost.io/requested-resources:
  ∙ 1 x aws_s3_bucket_accelerate_configuration
  ∙ 1 x aws_s3_bucket_request_payment_configuration

_{This comment will be updated when code changes.}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 5adb35e

Command	Status	Duration	Result
nx affected --target=subgraph-check --base=98bd...	✅ Succeeded	<1s	View ↗
nx affected --target=extract-translations --bas...	✅ Succeeded	<1s	View ↗
nx affected --target=lint --base=98bd101550bd06...	✅ Succeeded	4s	View ↗
nx affected --target=type-check --base=98bd1015...	✅ Succeeded	<1s	View ↗
nx run-many --target=codegen --all --parallel=3	✅ Succeeded	1s	View ↗
nx run-many --target=prisma-generate --all --pa...	✅ Succeeded	4s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-01-16 03:47:17 UTC

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 5adb35e

Command	Status	Duration	Result
nx run-many --target=codegen --all --parallel=3	✅ Succeeded	1s	View ↗
nx run-many --target=prisma-generate --all --pa...	✅ Succeeded	4s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-01-16 03:46:11 UTC

[jesus-film-bot]

Ran Plan for dir: infrastructure workspace: default

Show Output

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place

Terraform will perform the following actions:

  # module.prod.module.api-media.module.ecs-task.aws_ecs_service.ecs_service will be updated in-place
~ resource "aws_ecs_service" "ecs_service" {
      ~ desired_count                      = 2 -> 1
        id                                 = "arn:aws:ecs:us-east-2:410965620680:service/jfp-ecs-cluster-prod/api-media-prod-service"
        name                               = "api-media-prod-service"
        tags                               = {}
        # (18 unchanged attributes hidden)

        # (5 unchanged blocks hidden)
    }

  # module.prod.module.arclight.module.ecs-task.aws_ecs_service.ecs_service will be updated in-place
~ resource "aws_ecs_service" "ecs_service" {
      ~ desired_count                      = 1 -> 4
        id                                 = "arn:aws:ecs:us-east-2:410965620680:service/jfp-ecs-cluster-prod/arclight-prod-service"
        name                               = "arclight-prod-service"
        tags                               = {}
        # (18 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

  # module.stage.module.arclight.module.ecs-task.aws_ecs_service.ecs_service will be updated in-place
~ resource "aws_ecs_service" "ecs_service" {
      ~ desired_count                      = 1 -> 4
        id                                 = "arn:aws:ecs:us-east-2:410965620680:service/jfp-ecs-cluster-stage/arclight-stage-service"
        name                               = "arclight-stage-service"
        tags                               = {}
        # (18 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

Plan: 0 to add, 3 to change, 0 to destroy.
╷
│ Warning: Deprecated Resource
│ 
│   with module.datadog.datadog_integration_aws.sandbox,
│   on modules/aws/datadog/main.tf line 118, in resource "datadog_integration_aws" "sandbox":
│  118: resource "datadog_integration_aws" "sandbox" {
│ 
│ **This resource is deprecated - use the `datadog_integration_aws_account`
│ resource instead**:
│ https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/integration_aws_account
╵
╷
│ Warning: Deprecated attribute
│ 
│   on .terraform/modules/datadog.datadog_log_forwarder/modules/log_forwarder/main.tf line 2, in locals:
│    2:   bucket_name = var.bucket_name != "" ? var.bucket_name : "datadog-forwarder-${data.aws_caller_identity.current.account_id}-${data.aws_region.current.name}"
│ 
│ The attribute "name" is deprecated. Refer to the provider documentation for
│ details.
│ 
│ (and 2 more similar warnings elsewhere)
╵

• ▶️ To apply this plan, comment:

  atlantis apply -d infrastructure

• 🚮 To delete this plan and lock, click here
• 🔁 To plan this project again, comment:

  atlantis plan -d infrastructure

Plan: 0 to add, 3 to change, 0 to destroy.

---

• ⏩ To apply all unapplied plans from this Pull Request, comment:

  atlantis apply

• 🚮 To delete all plans and locks from this Pull Request, comment:

  atlantis unlock

[tataihono]

terraform unlock

[jesus-film-bot]

Did you mean to use atlantis instead of terraform?

[tataihono]

atlantis unlock

[jesus-film-bot]

All Atlantis locks for this PR have been unlocked and plans discarded