AWS Config Rule: ECS Task Definition Memory Hard Limit

Description: Checks if Amazon Elastic Container Service (ECS) task definitions have a set memory limit for its container definitions. The rule is NON_COMPLIANT for a task definition if the ‘memory’ parameter is absent for one container definition. Note: This rule only evaluates the latest active revision of an Amazon ECS task definition.

Trigger type: Configuration changes

AWS Region: All supported AWS regions except China (Beijing), Asia Pacific (Jakarta), Middle East (UAE), Asia Pacific (Hyderabad), Asia Pacific (Osaka), Asia Pacific (Melbourne), AWS GovCloud (US-East), AWS GovCloud (US-West), Israel (Tel Aviv), Europe (Spain), China (Ningxia), Europe (Zurich) Region

A task definition is a blueprint for your application. It is a text file in JSON format that describes the parameters and one or more containers that form your application.

This config rules checks if a memory limit is set in the latest active version of a Task Definition. The rule will be marked non-compliant if the 'memory' parameter is not set for the task definition.

In order to resolve this you will need to create a new revision for your particular non-compliant task definition. To do so head on over to the Elastic Container Service (ECS) and click on Task definitions from the left menu. From the list, click on the definition that is not compliant and then choose the latest revision.

At the properties screen, if you click on the JSON tab, you can check that the 'memory' parameter is not present.

To resolve the issue, click on Create New Revision button at the top right, then you can select Create new revision. Once there, locate the Container main card to configure the Memory hard limit that better suits your workload's needs.

Review the following screenshot as visual reference:

Want to know more about StackZone and how to make your cloud management simple and secure?

Check our how it works section with easy to follow videos or just create your own StackZone Account here