import { Value } from '../../cloudformation/Value';
import { InferenceAcceleratorProps } from './taskdefinition/InferenceAcceleratorProps';
import { TaskDefinitionPlacementConstraintProps } from './taskdefinition/TaskDefinitionPlacementConstraintProps';
import { RuntimePlatformProps } from './taskdefinition/RuntimePlatformProps';
import { ProxyConfigurationProps } from './taskdefinition/ProxyConfigurationProps';
import { VolumeProps } from './taskdefinition/VolumeProps';
import { ContainerDefinitionProps } from './taskdefinition/ContainerDefinitionProps';
import { EphemeralStorageProps } from './taskdefinition/EphemeralStorageProps';
import { Tag } from '../Tag';
import { Attribute } from '../../cloudformation/Attribute';
import { AwsResource } from '../../cloudformation/resources/AwsResource';
export type TaskDefinitionAttributes = {
    TaskDefinitionArn: Attribute<string>;
};
export type TaskDefinition = AwsResource<'AWS::ECS::TaskDefinition', TaskDefinitionProperties, TaskDefinitionAttributes>;
/**
  Registers a new task definition from the supplied <code>family</code> and <code>containerDefinitions</code>. Optionally, you can add data volumes to your containers with the <code>volumes</code> parameter. For more information about task definition parameters and defaults, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_defintions.html">Amazon ECS Task Definitions</a> in the <em>Amazon Elastic Container Service Developer Guide</em>.
  For full documentation go to <a href="http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-taskdefinition.html">the AWS Docs</a>
*/
export declare function taskDefinition(taskDefinitionProps?: TaskDefinitionProperties): TaskDefinition;
/**
  Registers a new task definition from the supplied <code>family</code> and <code>containerDefinitions</code>. Optionally, you can add data volumes to your containers with the <code>volumes</code> parameter. For more information about task definition parameters and defaults, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_defintions.html">Amazon ECS Task Definitions</a> in the <em>Amazon Elastic Container Service Developer Guide</em>.
  For full documentation go to <a href="http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-taskdefinition.html">the AWS Docs</a>
*/
export interface TaskDefinitionProperties {
    /** <code>TaskRoleArn</code>  <a name="cfn-ecs-taskdefinition-taskrolearn"></a>
  The short name or full Amazon Resource Name (ARN) of the AWS Identity and Access Management role that grants containers in the task permission to call AWS APIs on your behalf. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html">Amazon ECS Task Role</a> in the
  Amazon Elastic Container Service Developer Guide: br />
  
  Required: No<br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    taskRoleArn?: Value<string>;
    /** <code>IpcMode</code>  <a name="cfn-ecs-taskdefinition-ipcmode"></a>
  The IPC resource namespace to use for the containers in the task. The valid values are <code>host</code>, <code>task</code>, or <code>none</code>. If <code>host</code> is specified, then all containers within the tasks that specified the <code>host</code> IPC mode on the same container instance share the same IPC resources with the host Amazon EC2 instance. If <code>task</code> is specified, all containers within the specified task share the same IPC resources. If <code>none</code> is specified, then IPC resources within the containers of a task are private and not shared with other containers in a task or on the container instance. If no value is specified, then the IPC resource namespace sharing depends on the Docker daemon setting on the container instance. For more information, see <a href="https://docs.docker.com/engine/reference/run/#ipc-settings---ipc">IPC settings</a> in the
  Docker run reference: br />
  If the <code>host</code> IPC mode is used, be aware that there is a heightened risk of undesired IPC namespace expose. For more information, see <a href="https://docs.docker.com/engine/security/security/">Docker security</a>.<br />
  If you are setting namespaced kernel parameters using <code>systemControls</code> for the containers in the task, the following will apply to your IPC resource namespace. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html">System Controls</a> in the
  Amazon Elastic Container Service Developer Guide:  */
    ipcMode?: Value<string>;
    /** <code>InferenceAccelerators</code>  <a name="cfn-ecs-taskdefinition-inferenceaccelerators"></a>
  The Elastic Inference accelerators to use for the containers in the task.<br />
  
  Required: No<br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    inferenceAccelerators?: InferenceAcceleratorProps[];
    /** <p> */
    memory?: Value<string>;
    /** <code>PlacementConstraints</code>  <a name="cfn-ecs-taskdefinition-placementconstraints"></a>
  An array of placement constraint objects to use for tasks.<br />
  This parameter isn’t supported for tasks run on AWS Fargate.
  
  Required: No<br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    placementConstraints?: TaskDefinitionPlacementConstraintProps[];
    /** <p> */
    cpu?: Value<string>;
    /** <code>RequiresCompatibilities</code>  <a name="cfn-ecs-taskdefinition-requirescompatibilities"></a>
  The task launch types the task definition was validated against. The valid values are <code>EC2</code>, <code>FARGATE</code>, and <code>EXTERNAL</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html">Amazon ECS launch types</a> in the
  Amazon Elastic Container Service Developer Guide: br />
  
  Required: No<br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    requiresCompatibilities?: Value<Value<string>[]>;
    /** <code>NetworkMode</code>  <a name="cfn-ecs-taskdefinition-networkmode"></a>
  The Docker networking mode to use for the containers in the task. The valid values are <code>none</code>, <code>bridge</code>, <code>awsvpc</code>, and <code>host</code>. If no network mode is specified, the default is <code>bridge</code>.<br />
  For Amazon ECS tasks on Fargate, the <code>awsvpc</code> network mode is required. For Amazon ECS tasks on Amazon EC2 Linux instances, any network mode can be used. For Amazon ECS tasks on Amazon EC2 Windows instances, <code>&lt;default&gt;</code> or <code>awsvpc</code> can be used. If the network mode is set to <code>none</code>, you cannot specify port mappings in your container definitions, and the tasks containers do not have external connectivity. The <code>host</code> and <code>awsvpc</code> network modes offer the highest networking performance for containers because they use the EC2 network stack instead of the virtualized network stack provided by the <code>bridge</code> mode.<br />
  With the <code>host</code> and <code>awsvpc</code> network modes, exposed container ports are mapped directly to the corresponding host port (for the <code>host</code> network mode) or the attached elastic network interface port (for the <code>awsvpc</code> network mode), so you cannot take advantage of dynamic host port mappings.<br />
  When using the <code>host</code> network mode, you should not run containers using the root user (UID 0). It is considered best practice to use a non-root user.
  If the network mode is <code>awsvpc</code>, the task is allocated an elastic network interface, and you must specify a <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html#cfn-ecs-service-networkconfiguration">NetworkConfiguration</a> value when you create a service or run a task with the task definition. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html">Task Networking</a> in the
  Amazon Elastic Container Service Developer Guide: br />
  If the network mode is <code>host</code>, you cannot run multiple instantiations of the same task on a single container instance when port mappings are used.<br />
  For more information, see <a href="https://docs.docker.com/engine/reference/run/#network-settings">Network settings</a> in the
  Docker run reference: br />
  
  Required: No<br />
  
  Allowed values: <code>awsvpc | bridge | host | none</code><br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    networkMode?: Value<'awsvpc' | 'bridge' | 'host' | 'none'>;
    /** <code>PidMode</code>  <a name="cfn-ecs-taskdefinition-pidmode"></a>
  The process namespace to use for the containers in the task. The valid values are <code>host</code> or <code>task</code>. On Fargate for Linux containers, the only valid value is <code>task</code>. For example, monitoring sidecars might need <code>pidMode</code> to access information about other containers running in the same task.<br />
  If <code>host</code> is specified, all containers within the tasks that specified the <code>host</code> PID mode on the same container instance share the same process namespace with the host Amazon EC2 instance.<br />
  If <code>task</code> is specified, all containers within the specified task share the same process namespace.<br />
  If no value is specified, the default is a private namespace for each container. For more information, see <a href="https://docs.docker.com/engine/reference/run/#pid-settings---pid">PID settings</a> in the
  Docker run reference: br />
  If the <code>host</code> PID mode is used, there’s a heightened risk of undesired process namespace exposure. For more information, see <a href="https://docs.docker.com/engine/security/security/">Docker security</a>.<br />
  This parameter is not supported for Windows containers.
  This parameter is only supported for tasks that are hosted on AWS Fargate if the tasks are using platform version <code>1.4.0</code> or later (Linux). This isn’t supported for Windows containers on Fargate.
  
  Required: No<br />
  
  Allowed values: <code>host | task</code><br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    pidMode?: Value<'host' | 'task'>;
    /** <code>ExecutionRoleArn</code>  <a name="cfn-ecs-taskdefinition-executionrolearn"></a>
  The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission to make AWS API calls on your behalf. The task execution IAM role is required depending on the requirements of your task. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_execution_IAM_role.html">Amazon ECS task execution IAM role</a> in the
  Amazon Elastic Container Service Developer Guide: br />
  
  Required: No<br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    executionRoleArn?: Value<string>;
    /** <code>RuntimePlatform</code>  <a name="cfn-ecs-taskdefinition-runtimeplatform"></a>
  The operating system that your tasks definitions run on. A platform family is specified only for tasks using the Fargate launch type.<br />
  When you specify a task definition in a service, this value must match the <code>runtimePlatform</code> value of the service.<br />
  
  Required: No<br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    runtimePlatform?: RuntimePlatformProps;
    /** <code>ProxyConfiguration</code>  <a name="cfn-ecs-taskdefinition-proxyconfiguration"></a>
  The configuration details for the App Mesh proxy.<br />
  Your Amazon ECS container instances require at least version 1.26.0 of the container agent and at least version 1.26.0-1 of the <code>ecs-init</code> package to use a proxy configuration. If your container instances are launched from the Amazon ECS optimized AMI version <code>20190301</code> or later, they contain the required versions of the container agent and <code>ecs-init</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html">Amazon ECS-optimized Linux AMI</a> in the
  Amazon Elastic Container Service Developer Guide: br />
  
  Required: No<br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    proxyConfiguration?: ProxyConfigurationProps;
    /** <code>Volumes</code>  <a name="cfn-ecs-taskdefinition-volumes"></a>
  The list of data volume definitions for the task. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_data_volumes.html">Using data volumes in tasks</a> in the
  Amazon Elastic Container Service Developer Guide: br />
  The <code>host</code> and <code>sourcePath</code> parameters aren’t supported for tasks run on AWS Fargate.
  
  Required: No<br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    volumes?: VolumeProps[];
    /** <code>ContainerDefinitions</code>  <a name="cfn-ecs-taskdefinition-containerdefinitions"></a>
  A list of container definitions in JSON format that describe the different containers that make up your task. For more information about container definition parameters and defaults, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_defintions.html">Amazon ECS Task Definitions</a> in the
  Amazon Elastic Container Service Developer Guide: br />
  
  Required: No<br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    containerDefinitions?: ContainerDefinitionProps[];
    /** <code>Family</code>  <a name="cfn-ecs-taskdefinition-family"></a>
  The name of a family that this task definition is registered to. Up to 255 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed.<br />
  A family groups multiple versions of a task definition. Amazon ECS gives the first task definition that you registered to a family a revision number of 1. Amazon ECS gives sequential revision numbers to each task definition that you add.<br />
  To use revision numbers when you update a task definition, specify this property. If you don’t specify a value, AWS CloudFormation generates a new task definition each time that you update it.
  
  Required: No<br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    family?: Value<string>;
    /** <code>EphemeralStorage</code>  <a name="cfn-ecs-taskdefinition-ephemeralstorage"></a>
  The ephemeral storage settings to use for tasks run with the task definition.<br />
  
  Required: No<br />
  
  Update requires: <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement">Replacement</a> */
    ephemeralStorage?: EphemeralStorageProps;
    /** <p> */
    tags?: Tag[];
}
