AWS::ECS::TaskDefinition Ulimit - Amazon CloudFormation
SyntaxProperties
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

This is the new Amazon CloudFormation Template Reference Guide. Please update your bookmarks and links. For help getting started with CloudFormation, see the Amazon CloudFormation User Guide.

AWS::ECS::TaskDefinition Ulimit

The ulimit settings to pass to the container.

Amazon ECS tasks hosted on Amazon Fargate use the default resource limit values set by the operating system with the exception of the nofile resource limit parameter which Amazon Fargate overrides. The nofile resource limit sets a restriction on the number of open files that a container can use. The default nofile soft limit is 65535 and the default hard limit is 65535.

You can specify the ulimit settings for a container in a task definition.

Syntax

To declare this entity in your Amazon CloudFormation template, use the following syntax:

JSON

{
  "HardLimit" : Integer,
  "Name" : String,
  "SoftLimit" : Integer
}

YAML

  HardLimit: Integer
  Name: String
  SoftLimit: Integer

Properties

HardLimit

The hard limit for the ulimit type. The value can be specified in bytes, seconds, or as a count, depending on the type of the ulimit.

Required: Yes

Type: Integer

Update requires: Replacement

Name

The type of the ulimit.

Required: Yes

Type: String

Allowed values: core | cpu | data | fsize | locks | memlock | msgqueue | nice | nofile | nproc | rss | rtprio | rttime | sigpending | stack

Update requires: Replacement

SoftLimit

The soft limit for the ulimit type. The value can be specified in bytes, seconds, or as a count, depending on the type of the ulimit.

Required: Yes

Type: Integer

Update requires: Replacement