# Amazon ECS extends CPU and memory condition keys to RunTask

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

AWS announced on 10 September 2026 that Amazon ECS now supports the ecs:task-cpu and ecs:task-memory IAM condition keys on the RunTask and StartTask APIs. Before this they applied only to RegisterTaskDefinition, CreateService and UpdateService. Policies that reference them are now evaluated when tasks launch through either API.

AWS says administrators can use the keys to enforce consistent CPU and memory limits across every method of launching ECS tasks, helping to prevent unexpected cost overruns and keep workloads within resource policies.

The feature is available in all Regions where Amazon ECS is available, at no additional cost. A policy that limited CPU and memory only on task definitions did not cover tasks started directly, which is the gap this change closes.

## Related pages

- [Lambda functions accept full IAM resource-based policies](/news/lambda-full-resource-based-policies/)
- [IAM raises the default managed policies per role from 10 to 20](/news/managed-policies-per-role-20/)
- [IAM Policy Autopilot reads Terraform plan files](/news/iam-policy-autopilot-terraform-plan/)
- [All of them](/news/)

## Sources

- https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-ecs-expands-condition-key-support/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://iampolicygenerator.com/news/ecs-condition-keys-runtask/

This site is not affiliated with Amazon Web Services. AWS service and product names are used only to describe AWS services.
