GSP
Quick Navigator
Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
Paws::ECS::Task(3) User Contributed Perl Documentation Paws::ECS::Task(3)

Paws::ECS::Task

This class represents one of two things:

Arguments in a call to a service

Use the attributes of this class as arguments to methods. You shouldn't make instances of this class. Each attribute should be used as a named argument in the calls that expect this type of object.

As an example, if Att1 is expected to be a Paws::ECS::Task object:

  $service_obj->Method(Att1 => { Attachments => $value, ..., Version => $value  });

Results returned from an API call

Use accessors for each attribute. If Att1 is expected to be an Paws::ECS::Task object:

  $result = $service_obj->Method(...);
  $result->Att1->Attachments

Details on a task in a cluster.

The Elastic Network Adapter associated with the task if the task uses the "awsvpc" network mode.

The attributes of the task

The availability zone of the task.

The capacity provider associated with the task.

The ARN of the cluster that hosts the task.

The connectivity status of a task.

The Unix timestamp for when the task last went into "CONNECTED" status.

The ARN of the container instances that host the task.

The containers associated with the task.

The number of CPU units used by the task as expressed in a task definition. It can be expressed as an integer using CPU units, for example 1024. It can also be expressed as a string using vCPUs, for example "1 vCPU" or "1 vcpu". String values are converted to an integer indicating the CPU units when the task definition is registered.

If you are using the EC2 launch type, this field is optional. Supported values are between 128 CPU units (0.125 vCPUs) and 10240 CPU units (10 vCPUs).

If you are using the Fargate launch type, this field is required and you must use one of the following values, which determines your range of supported values for the "memory" parameter:

  • 256 (.25 vCPU) - Available "memory" values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)
  • 512 (.5 vCPU) - Available "memory" values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)
  • 1024 (1 vCPU) - Available "memory" values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)
  • 2048 (2 vCPU) - Available "memory" values: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)
  • 4096 (4 vCPU) - Available "memory" values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)

The Unix timestamp for when the task was created (the task entered the "PENDING" state).

The desired status of the task. For more information, see Task Lifecycle (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-lifecycle.html).

Whether or not execute command functionality is enabled for this task. If "true", this enables execute command functionality on all containers in the task.

The ephemeral storage settings for the task.

The Unix timestamp for when the task execution stopped.

The name of the task group associated with the task.

The health status for the task, which is determined by the health of the essential containers in the task. If all essential containers in the task are reporting as "HEALTHY", then the task status also reports as "HEALTHY". If any essential containers in the task are reporting as "UNHEALTHY" or "UNKNOWN", then the task status also reports as "UNHEALTHY" or "UNKNOWN", accordingly.

The Amazon ECS container agent does not monitor or report on Docker health checks that are embedded in a container image (such as those specified in a parent image or from the image's Dockerfile) and not specified in the container definition. Health check parameters that are specified in a container definition override any Docker health checks that exist in the container image.

The Elastic Inference accelerator associated with the task.

The last known status of the task. For more information, see Task Lifecycle (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-lifecycle.html).

The infrastructure on which your task is running. For more information, see Amazon ECS launch types (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html) in the Amazon Elastic Container Service Developer Guide.

The amount of memory (in MiB) used by the task as expressed in a task definition. It can be expressed as an integer using MiB, for example 1024. It can also be expressed as a string using GB, for example "1GB" or "1 GB". String values are converted to an integer indicating the MiB when the task definition is registered.

If you are using the EC2 launch type, this field is optional.

If you are using the Fargate launch type, this field is required and you must use one of the following values, which determines your range of supported values for the "cpu" parameter:

  • 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available "cpu" values: 256 (.25 vCPU)
  • 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available "cpu" values: 512 (.5 vCPU)
  • 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available "cpu" values: 1024 (1 vCPU)
  • Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available "cpu" values: 2048 (2 vCPU)
  • Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available "cpu" values: 4096 (4 vCPU)

One or more container overrides.

The platform version on which your task is running. A platform version is only specified for tasks using the Fargate launch type. If one is not specified, the "LATEST" platform version is used by default. For more information, see AWS Fargate Platform Versions (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform_versions.html) in the Amazon Elastic Container Service Developer Guide.

The Unix timestamp for when the container image pull began.

The Unix timestamp for when the container image pull completed.

The Unix timestamp for when the task started (the task transitioned from the "PENDING" state to the "RUNNING" state).

The tag specified when a task is started. If the task is started by an Amazon ECS service, then the "startedBy" parameter contains the deployment ID of the service that starts it.

The stop code indicating why a task was stopped. The "stoppedReason" may contain additional details.

The Unix timestamp for when the task was stopped (the task transitioned from the "RUNNING" state to the "STOPPED" state).

The reason that the task was stopped.

The Unix timestamp for when the task stops (transitions from the "RUNNING" state to "STOPPED").

The metadata that you apply to the task to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define.

The following basic restrictions apply to tags:

  • Maximum number of tags per resource - 50
  • For each resource, each tag key must be unique, and each tag key can have only one value.
  • Maximum key length - 128 Unicode characters in UTF-8
  • Maximum value length - 256 Unicode characters in UTF-8
  • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.
  • Tag keys and values are case-sensitive.
  • Do not use "aws:", "AWS:", or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for AWS use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

The Amazon Resource Name (ARN) of the task.

The ARN of the task definition that creates the task.

The version counter for the task. Every time a task experiences a change that triggers a CloudWatch event, the version counter is incremented. If you are replicating your Amazon ECS task state with CloudWatch Events, you can compare the version of a task reported by the Amazon ECS API actions with the version reported in CloudWatch Events for the task (inside the "detail" object) to verify that the version in your event stream is current.

This class forms part of Paws, describing an object used in Paws::ECS

The source code is located here: <https://github.com/pplu/aws-sdk-perl>

Please report bugs to: <https://github.com/pplu/aws-sdk-perl/issues>

2022-06-01 perl v5.40.2
Search for    or go to Top of page |  Section 3 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.