- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`account_id
Type: STRING
alarms
Type: STRUCT
Provider name: alarms
Description: The CloudWatch alarms that determine when a service deployment fails.
alarm_names
UNORDERED_LIST_STRING
alarmNames
status
STRING
status
DISABLED
.triggered_alarm_names
UNORDERED_LIST_STRING
triggeredAlarmNames
capacity_provider_strategy
Type: UNORDERED_LIST_STRUCT
Provider name: capacityProviderStrategy
Description: The capacity provider strategy that are associated with the task set.
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 the service that hosts the task set exists in.
computed_desired_count
Type: INT32
Provider name: computedDesiredCount
Description: The computed desired count for the task set. This is calculated by multiplying the service’s 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
Type: TIMESTAMP
Provider name: createdAt
Description: The Unix timestamp for the time when the task set was created.
deployment_circuit_breaker
Type: STRUCT
Provider name: deploymentCircuitBreaker
Description: The circuit breaker configuration that determines a service deployment failed.
failure_count
INT32
failureCount
status
STRING
status
DISABLED
.threshold
INT32
threshold
0.5 * desired task count
deployment_configuration
Type: STRUCT
Provider name: deploymentConfiguration
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%. The Amazon ECS scheduler uses this parameter to replace unhealthy tasks by starting replacement tasks first and then stopping the unhealthy tasks, as long as cluster resources for starting replacement tasks are available. For more information about how the scheduler replaces unhealthy tasks, see Amazon ECS services. If a service is using either the blue/green (CODE_DEPLOY
) or EXTERNAL
deployment types, and tasks in the service use the EC2 launch type, the maximum percent value is set to the default value. The maximum percent value 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. maximumPercent
value for a service that uses either the blue/green (CODE_DEPLOY
) or EXTERNAL
deployment types and has tasks that use the EC2 launch type. CODE_DEPLOY
) or EXTERNAL
deployment types, and the tasks in the service use the Fargate launch type, the maximum percent value is not used. The value is still 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. If any tasks are unhealthy and if maximumPercent
doesn’t allow the Amazon ECS scheduler to start replacement tasks, the scheduler stops the unhealthy tasks one-by-one — using the minimumHealthyPercent
as a constraint — to clear up capacity to launch replacement tasks. For more information about how the scheduler replaces unhealthy tasks, see Amazon ECS services . 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. The minimum healthy percent value 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. minimumHealthyPercent
value for a service that uses either the blue/green (CODE_DEPLOY
) or EXTERNAL
deployment types and has tasks that use the EC2 launch type. 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.fargate_ephemeral_storage
Type: STRUCT
Provider name: fargateEphemeralStorage
Description: The Fargate ephemeral storage settings for the task set.
kms_key_id
STRING
kmsKeyId
finished_at
Type: TIMESTAMP
Provider name: finishedAt
Description: The time the service deployment finished. The format is yyyy-MM-dd HH:mm:ss.SSSSSS.
id
Type: STRING
Provider name: id
Description: The ID of the task set.
launch_type
Type: STRING
Provider name: launchType
Description: The launch type the tasks in the task set are using. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide.
load_balancers
Type: UNORDERED_LIST_STRUCT
Provider name: loadBalancers
Description: Details on a load balancer that are used with a task set.
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 network configuration for the task set.
awsvpc_configuration
STRUCT
awsvpcConfiguration
assign_public_ip
STRING
assignPublicIp
create-service
or update-service
, the default is DISABLED
.deploymentController
is ECS
, the value must be DISABLED
.security_groups
UNORDERED_LIST_STRING
securityGroups
subnets
UNORDERED_LIST_STRING
subnets
pending_count
Type: INT32
Provider name: pendingCount
Description: The number of tasks in the task set that are in the 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
Type: STRING
Provider name: platformFamily
Description: The operating system that your tasks in the set are running on. A platform family is specified only for tasks that use the Fargate launch type. All tasks in the set must have the same value.
platform_version
Type: STRING
Provider name: platformVersion
Description: The Fargate platform version where the tasks in the task set are running. A platform version is only specified for tasks run on Fargate. For more information, see Fargate platform versions in the Amazon Elastic Container Service Developer Guide.
rollback
Type: STRUCT
Provider name: rollback
Description: The rollback options the service deployment uses when the deployment fails.
reason
STRING
reason
service_revision_arn
STRING
serviceRevisionArn
started_at
TIMESTAMP
startedAt
running_count
Type: INT32
Provider name: runningCount
Description: The number of tasks in the task set that are in the RUNNING
status during a deployment. A task in the RUNNING
state is running and ready for use.
scale
Type: STRUCT
Provider name: scale
Description: A floating-point percentage of your desired number of tasks to place and keep running in the task set.
unit
STRING
unit
value
DOUBLE
value
desiredCount
, to scale the task set. Accepted values are numbers between 0 and 100.service_arn
Type: STRING
Provider name: serviceArn
Description: The Amazon Resource Name (ARN) of the service the task set exists in.
service_deployment_arn
Type: STRING
Provider name: serviceDeploymentArn
Description: The ARN of the service deployment.
service_registries
Type: UNORDERED_LIST_STRUCT
Provider name: serviceRegistries
Description: The details for the service discovery registries to assign to this task set. 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
source_service_revisions
Type: UNORDERED_LIST_STRUCT
Provider name: sourceServiceRevisions
Description: The currently deployed workload configuration.
arn
STRING
arn
pending_task_count
INT32
pendingTaskCount
requested_task_count
INT32
requestedTaskCount
running_task_count
INT32
runningTaskCount
stability_status
Type: STRING
Provider name: stabilityStatus
Description: The stability status. This indicates whether the task set has reached a steady state. If the following conditions are met, the task set are in STEADY_STATE
:
runningCount
is equal to the computedDesiredCount
.pendingCount
is 0
.DRAINING
status.STABILIZING
.stability_status_at
Type: TIMESTAMP
Provider name: stabilityStatusAt
Description: The Unix timestamp for the time when the task set stability status was retrieved.
started_at
Type: TIMESTAMP
Provider name: startedAt
Description: The time the service deployment statred. The format is yyyy-MM-dd HH:mm:ss.SSSSSS.
started_by
Type: STRING
Provider name: startedBy
Description: The tag specified when a task set is started. If an CodeDeploy deployment created the task set, the startedBy
parameter is CODE_DEPLOY
. If an external deployment created the task set, the startedBy
field isn’t used.
status
Type: STRING
Provider name: status
Description: The status of the task set. The following describes each state.
status_reason
Type: STRING
Provider name: statusReason
Description: Information about why the service deployment is in the current status. For example, the circuit breaker detected a failure.
stopped_at
Type: TIMESTAMP
Provider name: stoppedAt
Description: The time the service deployment stopped. The format is yyyy-MM-dd HH:mm:ss.SSSSSS. The service deployment stops when any of the following actions happen:
tags
Type: UNORDERED_LIST_STRING
target_service_revision
Type: STRUCT
Provider name: targetServiceRevision
Description: The workload configuration being deployed.
arn
STRING
arn
pending_task_count
INT32
pendingTaskCount
requested_task_count
INT32
requestedTaskCount
running_task_count
INT32
runningTaskCount
task_definition
Type: STRING
Provider name: taskDefinition
Description: The task definition that the task set is using.
task_set_arn
Type: STRING
Provider name: taskSetArn
Description: The Amazon Resource Name (ARN) of the task set.
updated_at
Type: TIMESTAMP
Provider name: updatedAt
Description: The Unix timestamp for the time when the task set was last updated.