Skip to content

[FEATURE] ECS/Fargate Task Definition and Integration #91

Description

@ditahkk

Feature Description

Design ECS Task Definition pattern with IAM roles, CloudWatch integration, and multiple triggering mechanisms for Fargate deployment.

Use Case

Customers choosing container deployment need proper ECS/Fargate configuration with various triggering options for their compliance automation needs.

Proposed Solution

  • Single container per task pattern
  • Task-level IAM roles configuration
  • CloudWatch Logs integration
  • Triggering mechanisms: EventBridge → ECS RunTask, Lambda Orchestrator → ECS API, Step Functions → ECS Task State, Manual invocation

Alternatives Considered

  • EC2 launch type - evaluated in platform selection
  • Long-running container design - rejected for ephemeral model

Additional Context

  • Fargate Spot for non-critical workloads
  • Resource sizing: 256 CPU, 512MB RAM initial
  • Health check endpoints

Metadata

Metadata

Assignees

Labels

Type

Fields

No fields configured for Story.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions