- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
account_id
Type: STRING
capacity_provider_strategy
Type: UNORDERED_LIST_STRUCT
Provider name: capacityProviderStrategy
Description: The capacity provider strategy the service uses. When using the DescribeServices API, this field is omitted if the service was created using a launch type.
base
INT32
base
0
is used.capacity_provider
STRING
capacityProvider
weight
INT32
weight
weight
value is taken into consideration after the base
value, if defined, is satisfied. If no weight
value is specified, the default value of 0
is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0
can’t be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0
, any RunTask
or CreateService
actions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1
, then when the base
is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1
for capacityProviderA and a weight of 4
for capacityProviderB, then for every one task that’s run using capacityProviderA, four tasks would use capacityProviderB.cluster_arn
Type: STRING
Provider name: clusterArn
Description: The Amazon Resource Name (ARN) of the cluster that hosts the service.
created_at
Type: TIMESTAMP
Provider name: createdAt
Description: The Unix timestamp for the time when the service was created.
created_by
Type: STRING
Provider name: createdBy
Description: The principal that created the service.
deployment_configuration
Type: STRUCT
Provider name: deploymentConfiguration
Description: Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
alarms
STRUCT
alarms
alarm_names
UNORDERED_LIST_STRING
alarmNames
enable
BOOLEAN
enable
rollback
BOOLEAN
rollback
deployment_circuit_breaker
STRUCT
deploymentCircuitBreaker
ECS
) deployment type. enable
BOOLEAN
enable
rollback
BOOLEAN
rollback
maximum_percent
INT32
maximumPercent
ECS
) deployment type, the maximumPercent
parameter represents an upper limit on the number of your service’s tasks that are allowed in the RUNNING
or PENDING
state during a deployment, as a percentage of the desiredCount
(rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA
service scheduler and has a desiredCount
of four tasks and a maximumPercent
value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default maximumPercent
value for a service using the REPLICA
service scheduler is 200%. If a service is using either the blue/green (CODE_DEPLOY
) or EXTERNAL
deployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in the RUNNING
state while the container instances are in the DRAINING
state. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service.minimum_healthy_percent
INT32
minimumHealthyPercent
ECS
) deployment type, the minimumHealthyPercent
represents a lower limit on the number of your service’s tasks that must remain in the RUNNING
state during a deployment, as a percentage of the desiredCount
(rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount
of four tasks and a minimumHealthyPercent
of 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. For services that do not use a load balancer, the following should be noted:RUNNING
state before the task is counted towards the minimum healthy percent total.minimumHealthyPercent
is 100%. The default minimumHealthyPercent
value for a service using the DAEMON
service schedule is 0% for the CLI, the Amazon Web Services SDKs, and the APIs and 50% for the Amazon Web Services Management Console. The minimum number of healthy tasks during a deployment is the desiredCount
multiplied by the minimumHealthyPercent
/100, rounded up to the nearest integer value. If a service is using either the blue/green (CODE_DEPLOY
) or EXTERNAL
deployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING
state while the container instances are in the DRAINING
state. If a service is using either the blue/green (CODE_DEPLOY
) or EXTERNAL
deployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.deployment_controller
Type: STRUCT
Provider name: deploymentController
Description: The deployment controller type the service is using.
type
STRING
type
ECS
) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration.CODE_DEPLOY
) deployment type uses the blue/green deployment model powered by CodeDeploy, which allows you to verify a new deployment of a service before sending production traffic to it.EXTERNAL
) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.deployments
Type: UNORDERED_LIST_STRUCT
Provider name: deployments
Description: The current state of deployments for the service.
capacity_provider_strategy
UNORDERED_LIST_STRUCT
capacityProviderStrategy
base
INT32
base
0
is used.capacity_provider
STRING
capacityProvider
weight
INT32
weight
weight
value is taken into consideration after the base
value, if defined, is satisfied. If no weight
value is specified, the default value of 0
is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0
can’t be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0
, any RunTask
or CreateService
actions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1
, then when the base
is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1
for capacityProviderA and a weight of 4
for capacityProviderB, then for every one task that’s run using capacityProviderA, four tasks would use capacityProviderB.created_at
TIMESTAMP
createdAt
desired_count
INT32
desiredCount
failed_tasks
INT32
failedTasks
RUNNING
state, or if it fails any of its defined health checks and is stopped. fargate_ephemeral_storage
STRUCT
fargateEphemeralStorage
kms_key_id
STRING
kmsKeyId
id
STRING
id
launch_type
STRING
launchType
network_configuration
STRUCT
networkConfiguration
awsvpc
networking mode.awsvpc_configuration
STRUCT
awsvpcConfiguration
assign_public_ip
STRING
assignPublicIp
DISABLED
.security_groups
UNORDERED_LIST_STRING
securityGroups
AwsVpcConfiguration
. subnets
UNORDERED_LIST_STRING
subnets
AwsVpcConfiguration
. pending_count
INT32
pendingCount
PENDING
status.platform_family
STRING
platformFamily
platformFamily
value as the service, for example, LINUX.
.platform_version
STRING
platformVersion
LATEST
platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide.rollout_state
STRING
rolloutState
rolloutState
of a service is only returned for services that use the rolling update (ECS
) deployment type that aren’t behind a Classic Load Balancer. IN_PROGRESS
state. When the service reaches a steady state, the deployment transitions to a COMPLETED
state. If the service fails to reach a steady state and circuit breaker is turned on, the deployment transitions to a FAILED
state. A deployment in FAILED
state doesn’t launch any new tasks. For more information, see DeploymentCircuitBreaker.rollout_state_reason
STRING
rolloutStateReason
running_count
INT32
runningCount
RUNNING
status.service_connect_configuration
STRUCT
serviceConnectConfiguration
enabled
BOOLEAN
enabled
log_configuration
STRUCT
logConfiguration
log_driver
STRING
logDriver
awslogs
, splunk
, and awsfirelens
. For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs
, fluentd
, gelf
, json-file
, journald
, logentries
,syslog
, splunk
, and awsfirelens
. For more information about using the awslogs
log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide. For more information about using the awsfirelens
log driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide. options
MAP_STRING_STRING
options
sudo docker version –format ‘{{.Server.APIVersion}}’
secret_options
UNORDERED_LIST_STRUCT
secretOptions
name
STRING
name
value_from
STRING
valueFrom
namespace
STRING
namespace
services
UNORDERED_LIST_STRUCT
services
client_aliases
UNORDERED_LIST_STRUCT
clientAliases
ServiceConnectService
, you must provide at least one clientAlias
with one port
.dns_name
STRING
dnsName
dnsName
is the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn’t need to be fully-qualified. The name can include up to 127 characters. The name can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). The name can’t start with a hyphen. If this parameter isn’t specified, the default value of discoveryName.namespace
is used. If the discoveryName
isn’t specified, the port mapping name from the task definition is used in portName.namespace
. To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names are database
, db
, or the lowercase name of a database, such as mysql
or redis
. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.port
INT32
port
discovery_name
STRING
discoveryName
discoveryName
is the name of the new Cloud Map service that Amazon ECS creates for this Amazon ECS service. This must be unique within the Cloud Map namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can’t start with a hyphen. If the discoveryName
isn’t specified, the port mapping name from the task definition is used in portName.namespace
.ingress_port_override
INT32
ingressPortOverride
portMapping
in the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service. In awsvpc
mode and Fargate, the default value is the container port number. The container port number is in the portMapping
in the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy.port_name
STRING
portName
portName
must match the name of one of the portMappings
from all the containers in the task definition of this Amazon ECS service.timeout
STRUCT
timeout
idle_timeout_seconds
INT32
idleTimeoutSeconds
0
can be set to disable idleTimeout
. The idleTimeout
default for HTTP
/HTTP2
/GRPC
is 5 minutes. The idleTimeout
default for TCP
is 1 hour.per_request_timeout_seconds
INT32
perRequestTimeoutSeconds
0
can be set to disable perRequestTimeout
. perRequestTimeout
can only be set if Service Connect appProtocol
isn’t TCP
. Only idleTimeout
is allowed for TCP
appProtocol
.tls
STRUCT
tls
issuer_certificate_authority
STRUCT
issuerCertificateAuthority
aws_pca_authority_arn
STRING
awsPcaAuthorityArn
kms_key
STRING
kmsKey
role_arn
STRING
roleArn
service_connect_resources
UNORDERED_LIST_STRUCT
serviceConnectResources
discovery_arn
STRING
discoveryArn
discovery_name
STRING
discoveryName
discoveryName
is the name of the new Cloud Map service that Amazon ECS creates for this Amazon ECS service. This must be unique within the Cloud Map namespace. The name can contain up to 64 characters. The name can include lowercase letters, numbers, underscores (_), and hyphens (-). The name can’t start with a hyphen. If the discoveryName
isn’t specified, the port mapping name from the task definition is used in portName.namespace
.status
STRING
status
PRIMARY
deployment.task_definition
STRING
taskDefinition
updated_at
TIMESTAMP
updatedAt
volume_configurations
UNORDERED_LIST_STRUCT
volumeConfigurations
configuredAtLaunch
. You can configure different settings like the size, throughput, volumeType, and ecryption in ServiceManagedEBSVolumeConfiguration. The name
of the volume must match the name
from the task definition.managed_ebs_volume
STRUCT
managedEBSVolume
encrypted
BOOLEAN
encrypted
Encrypted
parameter of the CreateVolume API in the Amazon EC2 API Reference.filesystem_type
STRING
filesystemType
ext3
, ext4
, and xfs
. If no value is specified, the xfs
filesystem type is used by default.iops
INT32
iops
gp3
, io1
, and io2
volumes, this represents the number of IOPS that are provisioned for the volume. For gp2
volumes, this represents the baseline performance of the volume and the rate at which the volume accumulates I/O credits for bursting. The following are the supported values for each volume type.gp3
: 3,000 - 16,000 IOPSio1
: 100 - 64,000 IOPSio2
: 100 - 256,000 IOPSio1
and io2
volume types. The default for gp3
volumes is 3,000 IOPS
. This parameter is not supported for st1
, sc1
, or standard
volume types. This parameter maps 1:1 with the Iops
parameter of the CreateVolume API in the Amazon EC2 API Reference.kms_key_id
STRING
kmsKeyId
KmsKeyId
parameter of the CreateVolume API in the Amazon EC2 API Reference. role_arn
STRING
roleArn
AmazonECSInfrastructureRolePolicyForVolumes
IAM policy with this role. For more information, see Amazon ECS infrastructure IAM role in the Amazon ECS Developer Guide.size_in_gib
INT32
sizeInGiB
Size
parameter of the CreateVolume API in the Amazon EC2 API Reference. The following are the supported volume size values for each volume type.gp2
and gp3
: 1-16,384io1
and io2
: 4-16,384st1
and sc1
: 125-16,384standard
: 1-1,024snapshot_id
STRING
snapshotId
SnapshotId
parameter of the CreateVolume API in the Amazon EC2 API Reference.tag_specifications
UNORDERED_LIST_STRUCT
tagSpecifications
TagSpecifications.N
parameter of the CreateVolume API in the Amazon EC2 API Reference.propagate_tags
STRING
propagateTags
SERVICE
specified in ServiceVolumeConfiguration
. If no value is specified, the tags aren’t propagated.resource_type
STRING
resourceType
throughput
INT32
throughput
Throughput
parameter of the CreateVolume API in the Amazon EC2 API Reference. gp3
volume type.volume_type
STRING
volumeType
VolumeType
parameter of the CreateVolume API in the Amazon EC2 API Reference. For more information, see Amazon EBS volume types in the Amazon EC2 User Guide. The following are the supported volume types.gp2
|gp3
io1
|io2
st1
sc1
standard
name
STRING
name
Volume
object in the task definition.desired_count
Type: INT32
Provider name: desiredCount
Description: The desired number of instantiations of the task definition to keep running on the service. This value is specified when the service is created with CreateService, and it can be modified with UpdateService.
enable_ecs_managed_tags
Type: BOOLEAN
Provider name: enableECSManagedTags
Description: Determines whether to use Amazon ECS managed tags for the tasks in the service. For more information, see Tagging Your Amazon ECS Resources in the Amazon Elastic Container Service Developer Guide.
enable_execute_command
Type: BOOLEAN
Provider name: enableExecuteCommand
Description: Determines whether the execute command functionality is turned on for the service. If true
, the execute command functionality is turned on for all containers in tasks as part of the service.
events
Type: UNORDERED_LIST_STRUCT
Provider name: events
Description: The event stream for your service. A maximum of 100 of the latest events are displayed.
created_at
TIMESTAMP
createdAt
id
STRING
id
message
STRING
message
health_check_grace_period_seconds
Type: INT32
Provider name: healthCheckGracePeriodSeconds
Description: The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started.
launch_type
Type: STRING
Provider name: launchType
Description: The launch type the service is using. When using the DescribeServices API, this field is omitted if the service was created using a capacity provider strategy.
load_balancers
Type: UNORDERED_LIST_STRUCT
Provider name: loadBalancers
Description: A list of Elastic Load Balancing load balancer objects. It contains the load balancer name, the container name, and the container port to access from the load balancer. The container name is as it appears in a container definition.
container_name
STRING
containerName
container_port
INT32
containerPort
containerPort
in the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they’re launched on must allow ingress traffic on the hostPort
of the port mapping.load_balancer_name
STRING
loadBalancerName
target_group_arn
STRING
targetGroupArn
ECS
deployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using the CODE_DEPLOY
deployment controller, you’re required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. awsvpc
network mode, you must choose ip
as the target type, not instance
. Do this when creating your target groups because tasks that use the awsvpc
network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.network_configuration
Type: STRUCT
Provider name: networkConfiguration
Description: The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the awsvpc
networking mode.
awsvpc_configuration
STRUCT
awsvpcConfiguration
assign_public_ip
STRING
assignPublicIp
DISABLED
.security_groups
UNORDERED_LIST_STRING
securityGroups
AwsVpcConfiguration
. subnets
UNORDERED_LIST_STRING
subnets
AwsVpcConfiguration
. pending_count
Type: INT32
Provider name: pendingCount
Description: The number of tasks in the cluster that are in the PENDING
state.
placement_constraints
Type: UNORDERED_LIST_STRUCT
Provider name: placementConstraints
Description: The placement constraints for the tasks in the service.
expression
STRING
expression
distinctInstance
. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide.type
STRING
type
distinctInstance
to ensure that each task in a particular group is running on a different container instance. Use memberOf
to restrict the selection to a group of valid candidates.placement_strategy
Type: UNORDERED_LIST_STRUCT
Provider name: placementStrategy
Description: The placement strategy that determines how tasks for the service are placed.
field
STRING
field
spread
placement strategy, valid values are instanceId
(or host
, which has the same effect), or any platform or custom attribute that’s applied to a container instance, such as attribute:ecs.availability-zone
. For the binpack
placement strategy, valid values are cpu
and memory
. For the random
placement strategy, this field is not used.type
STRING
type
random
placement strategy randomly places tasks on available candidates. The spread
placement strategy spreads placement across available candidates evenly based on the field
parameter. The binpack
strategy places tasks on available candidates that have the least available amount of the resource that’s specified with the field
parameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.platform_family
Type: STRING
Provider name: platformFamily
Description: The operating system that your tasks in the service run on. A platform family is specified only for tasks using the Fargate launch type. All tasks that run as part of this service must use the same platformFamily
value as the service (for example, LINUX
).
platform_version
Type: STRING
Provider name: platformVersion
Description: The platform version to run your service on. A platform version is only specified for tasks that are hosted on Fargate. If one isn’t specified, the LATEST
platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide.
propagate_tags
Type: STRING
Provider name: propagateTags
Description: Determines whether to propagate the tags from the task definition or the service to the task. If no value is specified, the tags aren’t propagated.
role_arn
Type: STRING
Provider name: roleArn
Description: The ARN of the IAM role that’s associated with the service. It allows the Amazon ECS container agent to register container instances with an Elastic Load Balancing load balancer.
running_count
Type: INT32
Provider name: runningCount
Description: The number of tasks in the cluster that are in the RUNNING
state.
scheduling_strategy
Type: STRING
Provider name: schedulingStrategy
Description: The scheduling strategy to use for the service. For more information, see Services. There are two service scheduler strategies available.
REPLICA
-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions.DAEMON
-The daemon scheduling strategy deploys exactly one task on each active container instance. This task meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks. It stop tasks that don’t meet the placement constraints. DAEMON
scheduling strategy.service_arn
Type: STRING
Provider name: serviceArn
Description: The ARN that identifies the service. For more information about the ARN format, see Amazon Resource Name (ARN) in the Amazon ECS Developer Guide.
service_name
Type: STRING
Provider name: serviceName
Description: The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster. However, you can have similarly named services in multiple clusters within a Region or across multiple Regions.
service_registries
Type: UNORDERED_LIST_STRUCT
Provider name: serviceRegistries
Description: The details for the service discovery registries to assign to this service. For more information, see Service Discovery.
container_name
STRING
containerName
bridge
or host
network mode, you must specify a containerName
and containerPort
combination from the task definition. If the task definition that your service task specifies uses the awsvpc
network mode and a type SRV DNS record is used, you must specify either a containerName
and containerPort
combination or a port
value. However, you can’t specify both.container_port
INT32
containerPort
bridge
or host
network mode, you must specify a containerName
and containerPort
combination from the task definition. If the task definition your service task specifies uses the awsvpc
network mode and a type SRV DNS record is used, you must specify either a containerName
and containerPort
combination or a port
value. However, you can’t specify both.port
INT32
port
awsvpc
network mode and SRV records are used.registry_arn
STRING
registryArn
status
Type: STRING
Provider name: status
Description: The status of the service. The valid values are ACTIVE
, DRAINING
, or INACTIVE
.
tags
Type: UNORDERED_LIST_STRING
task_definition
Type: STRING
Provider name: taskDefinition
Description: The task definition to use for tasks in the service. This value is specified when the service is created with CreateService, and it can be modified with UpdateService.
task_sets
Type: UNORDERED_LIST_STRUCT
Provider name: taskSets
Description: Information about a set of Amazon ECS tasks in either an CodeDeploy or an EXTERNAL
deployment. An Amazon ECS task set includes details such as the desired number of tasks, how many tasks are running, and whether the task set serves production traffic.
capacity_provider_strategy
UNORDERED_LIST_STRUCT
capacityProviderStrategy
base
INT32
base
0
is used.capacity_provider
STRING
capacityProvider
weight
INT32
weight
weight
value is taken into consideration after the base
value, if defined, is satisfied. If no weight
value is specified, the default value of 0
is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0
can’t be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0
, any RunTask
or CreateService
actions using the capacity provider strategy will fail. An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1
, then when the base
is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1
for capacityProviderA and a weight of 4
for capacityProviderB, then for every one task that’s run using capacityProviderA, four tasks would use capacityProviderB.cluster_arn
STRING
clusterArn
computed_desired_count
INT32
computedDesiredCount
desiredCount
by the task set’s scale
percentage. The result is always rounded up. For example, if the computed desired count is 1.2, it rounds up to 2 tasks.created_at
TIMESTAMP
createdAt
external_id
STRING
externalId
externalId
parameter contains the CodeDeploy deployment ID. If a task set is created for an external deployment and is associated with a service discovery registry, the externalId
parameter contains the ECS_TASK_SET_EXTERNAL_ID
Cloud Map attribute.fargate_ephemeral_storage
STRUCT
fargateEphemeralStorage
kms_key_id
STRING
kmsKeyId
id
STRING
id
launch_type
STRING
launchType
load_balancers
UNORDERED_LIST_STRUCT
loadBalancers
container_name
STRING
containerName
container_port
INT32
containerPort
containerPort
in the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they’re launched on must allow ingress traffic on the hostPort
of the port mapping.load_balancer_name
STRING
loadBalancerName
target_group_arn
STRING
targetGroupArn
ECS
deployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide. For services using the CODE_DEPLOY
deployment controller, you’re required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide. awsvpc
network mode, you must choose ip
as the target type, not instance
. Do this when creating your target groups because tasks that use the awsvpc
network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.network_configuration
STRUCT
networkConfiguration
awsvpc_configuration
STRUCT
awsvpcConfiguration
assign_public_ip
STRING
assignPublicIp
DISABLED
.security_groups
UNORDERED_LIST_STRING
securityGroups
AwsVpcConfiguration
. subnets
UNORDERED_LIST_STRING
subnets
AwsVpcConfiguration
. pending_count
INT32
pendingCount
PENDING
status during a deployment. A task in the PENDING
state is preparing to enter the RUNNING
state. A task set enters the PENDING
status when it launches for the first time or when it’s restarted after being in the STOPPED
state.platform_family
STRING
platformFamily
platform_version
STRING
platformVersion
running_count
INT32
runningCount
RUNNING
status during a deployment. A task in the RUNNING
state is running and ready for use.scale
STRUCT
scale
unit
STRING
unit
value
DOUBLE
value
desiredCount
, to scale the task set. Accepted values are numbers between 0 and 100.service_arn
STRING
serviceArn
service_registries
UNORDERED_LIST_STRUCT
serviceRegistries
container_name
STRING
containerName
bridge
or host
network mode, you must specify a containerName
and containerPort
combination from the task definition. If the task definition that your service task specifies uses the awsvpc
network mode and a type SRV DNS record is used, you must specify either a containerName
and containerPort
combination or a port
value. However, you can’t specify both.container_port
INT32
containerPort
bridge
or host
network mode, you must specify a containerName
and containerPort
combination from the task definition. If the task definition your service task specifies uses the awsvpc
network mode and a type SRV DNS record is used, you must specify either a containerName
and containerPort
combination or a port
value. However, you can’t specify both.port
INT32
port
awsvpc
network mode and SRV records are used.registry_arn
STRING
registryArn
stability_status
STRING
stabilityStatus
STEADY_STATE
:runningCount
is equal to the computedDesiredCount
.pendingCount
is 0
.DRAINING
status.STABILIZING
.stability_status_at
TIMESTAMP
stabilityStatusAt
started_by
STRING
startedBy
startedBy
parameter is CODE_DEPLOY
. If an external deployment created the task set, the startedBy
field isn’t used.status
STRING
status
task_definition
STRING
taskDefinition
task_set_arn
STRING
taskSetArn
updated_at
TIMESTAMP
updatedAt