Skip to main content
LOWECSReliability

ECS Resource Limits Missing

ecs-resources-missing

What this rule checks

Detects ECS task definitions without CPU/memory limits.

How to fix it

  1. 1Set CPU and memory at task level for Fargate
  2. 2Set container-level memory limits for EC2
FlaggedNeither task-level Cpu/Memory nor any container-level limit is set, so a runaway container has no ceiling and scheduling is unpredictable. The check flags a task definition when it has no task-level sizing and a container carries no CPU/memory limit.
import { App, Stack } from 'aws-cdk-lib';
import { Construct } from 'constructs';
import * as ecs from 'aws-cdk-lib/aws-ecs';

// FLAGGED: no task-level sizing and no container CPU/memory limits.
new ecs.CfnTaskDefinition(this, 'Task', {
  containerDefinitions: [
    {
      name: 'app',
      image: 'nginx:1.27.3',
      logConfiguration: {
        logDriver: 'awslogs',
        options: { 'awslogs-group': '/ecs/app', 'awslogs-region': 'us-east-1', 'awslogs-stream-prefix': 'app' },
      },
    },
  ],
});
FixedSetting Cpu and Memory at the task level gives the task a hard resource envelope, which the check accepts as configured sizing even when individual containers omit their own limits.
import { App, Stack } from 'aws-cdk-lib';
import { Construct } from 'constructs';
import * as ecs from 'aws-cdk-lib/aws-ecs';

// FIXED: task-level CPU and memory sizing (Fargate-style).
new ecs.CfnTaskDefinition(this, 'Task', {
  cpu: '256',
  memory: '512',
  containerDefinitions: [
    {
      name: 'app',
      image: 'nginx:1.27.3',
      logConfiguration: {
        logDriver: 'awslogs',
        options: { 'awslogs-group': '/ecs/app', 'awslogs-region': 'us-east-1', 'awslogs-stream-prefix': 'app' },
      },
    },
  ],
});

CDK Insights pinpoints the exact file and line in your CDK source for every finding, so you can jump straight to the fix.

Affected resource types

AWS::ECS::TaskDefinition

AWS documentation

Read the AWS guidance

Intentional? Suppress this finding

Sometimes a flag is deliberate โ€” a genuinely public endpoint, say. You can dismiss ecs-resources-missing and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "ecs-resources-missing", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::ecs-resources-missing',
  reason: 'Why this is intentional',
});

Use the rule ID ecs-resources-missing shown above โ€” not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs โ†’

Catch this in your stack

$ npx cdk-insights scan

CDK Insights runs this and 118+ other rules locally against your synthesised CDK app โ€” free, no account, your code never leaves your machine.

More ECS rules