Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris.
# Contoh Amazon ECS menggunakan AWS CLI
Contoh kode berikut menunjukkan kepada Anda cara melakukan tindakan dan menerapkan skenario umum AWS Command Line Interface dengan menggunakan Amazon ECS.
*Tindakan* merupakan kutipan kode dari program yang lebih besar dan harus dijalankan dalam konteks. Sementara tindakan menunjukkan cara memanggil fungsi layanan individual, Anda dapat melihat tindakan dalam konteks dalam skenario terkait.
Setiap contoh menyertakan tautan ke kode sumber lengkap, di mana Anda dapat menemukan instruksi tentang cara mengatur dan menjalankan kode dalam konteks.
**Topics**
+ [Tindakan](#actions)
## Tindakan
### `capacity-provider-update`
Contoh kode berikut menunjukkan cara menggunakan`capacity-provider-update`.
**AWS CLI**
**Perbarui penyedia kapasitas di cluster ECS**
`update-capacity-provider`Contoh berikut menunjukkan bagaimana kita dapat memodifikasi parameter penyedia kapasitas dalam cluster ECS.
```
aws ecs update-capacity-provider \
--name Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-EC2CapacityProvider-3fIpdkLywwFt \
--auto-scaling-group-provider "managedScaling={status=DISABLED,targetCapacity=50,minimumScalingStepSize=2,maximumScalingStepSize=30,instanceWarmupPeriod=200},managedTerminationProtection=DISABLED,managedDraining=DISABLED"
```
Output:
```
{
"capacityProvider": {
"capacityProviderArn": "arn:aws:ecs:us-west-2:123456789012:capacity-provider/Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-EC2CapacityProvider-3fIpdkLywwFt",
"name": "Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-EC2CapacityProvider-3fIpdkLywwFt",
"status": "ACTIVE",
"autoScalingGroupProvider": {
"autoScalingGroupArn": "arn:aws:autoscaling:us-west-2:123456789012:autoScalingGroup:424941d1-b43f-4a17-adbb-08b6a6e397e1:autoScalingGroupName/Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-ECSAutoScalingGroup-f44jrQHS2nRB",
"managedScaling": {
"status": "ENABLED",
"targetCapacity": 100,
"minimumScalingStepSize": 1,
"maximumScalingStepSize": 10000,
"instanceWarmupPeriod": 300
},
"managedTerminationProtection": "DISABLED",
"managedDraining": "ENABLED"
},
"updateStatus": "UPDATE_IN_PROGRESS",
"tags": []
}
}
```
Untuk informasi selengkapnya tentang Penyedia Kapasitas, lihat [Penyedia kapasitas Amazon ECS untuk jenis peluncuran EC2 di Panduan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/asg-capacity-providers.html) Pengembang *Amazon ECS.*
+ Untuk detail API, lihat [CapacityProviderUpdate](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/capacity-provider-update.html)di *Referensi AWS CLI Perintah*.
### `create-capacity-provider`
Contoh kode berikut menunjukkan cara menggunakan`create-capacity-provider`.
**AWS CLI**
**Untuk membuat penyedia kapasitas**
create-capacity-providerContoh berikut membuat penyedia kapasitas yang menggunakan grup Auto Scaling bernama myASG, telah mengelola penskalaan dan perlindungan terminasi terkelola yang diaktifkan. Konfigurasi ini digunakan untuk auto scaling klaster Amazon ECS.
```
aws ecs create-capacity-provider \
--name "MyCapacityProvider" \
--auto-scaling-group-provider "autoScalingGroupArn=arn:aws:autoscaling:us-east-1:123456789012:autoScalingGroup:57ffcb94-11f0-4d6d-bf60-3bac5EXAMPLE:autoScalingGroupName/MyASG,managedScaling={status=ENABLED,targetCapacity=100},managedTerminationProtection=ENABLED"
```
Output:
```
{
"capacityProvider": {
"capacityProviderArn": "arn:aws:ecs:us-east-1:123456789012:capacity-provider/MyCapacityProvider",
"name": "MyCapacityProvider",
"status": "ACTIVE",
"autoScalingGroupProvider": {
"autoScalingGroupArn": "arn:aws:autoscaling:us-east-1:132456789012:autoScalingGroup:57ffcb94-11f0-4d6d-bf60-3bac5EXAMPLE:autoScalingGroupName/MyASG",
"managedScaling": {
"status": "ENABLED",
"targetCapacity": 100,
"minimumScalingStepSize": 1,
"maximumScalingStepSize": 10000,
"instanceWarmupPeriod": 300
},
"managedTerminationProtection": "ENABLED"
},
"tags": []
}
```
Untuk informasi selengkapnya, lihat [penskalaan otomatis klaster Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-auto-scaling.html) di Panduan Pengembang *Amazon ECS.*
+ Untuk detail API, lihat [CreateCapacityProvider](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/create-capacity-provider.html)di *Referensi AWS CLI Perintah*.
### `create-cluster`
Contoh kode berikut menunjukkan cara menggunakan`create-cluster`.
**AWS CLI**
**Contoh 1: Untuk membuat cluster baru**
`create-cluster`Contoh berikut membuat cluster bernama `MyCluster` dan memungkinkan CloudWatch Container Insights dengan observabilitas yang ditingkatkan.
```
aws ecs create-cluster \
--cluster-name MyCluster \
--settings name=containerInsights,value=enhanced
```
Output:
```
{
"cluster": {
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster",
"clusterName": "MyCluster",
"status": "ACTIVE",
"registeredContainerInstancesCount": 0,
"pendingTasksCount": 0,
"runningTasksCount": 0,
"activeServicesCount": 0,
"statistics": [],
"settings": [
{
"name": "containerInsights",
"value": "enhanced"
}
],
"tags": []
}
}
```
Untuk informasi selengkapnya, lihat [Membuat Cluster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create_cluster.html) di *Panduan Pengembang Amazon ECS*.
**Contoh 2: Untuk membuat cluster baru menggunakan penyedia kapasitas**
`create-cluster`Contoh berikut membuat cluster dan mengaitkan dua penyedia kapasitas yang ada dengannya. `create-capacity-provider`Perintah ini digunakan untuk membuat penyedia kapasitas. Menentukan strategi penyedia kapasitas default adalah opsional, tetapi disarankan. Dalam contoh ini, kita membuat sebuah cluster bernama `MyCluster` dan mengasosiasikan `MyCapacityProvider1` dan penyedia `MyCapacityProvider2` kapasitas dengannya. Strategi penyedia kapasitas default ditentukan yang menyebarkan tugas secara merata di kedua penyedia kapasitas.
```
aws ecs create-cluster \
--cluster-name MyCluster \
--capacity-providers MyCapacityProvider1 MyCapacityProvider2 \
--default-capacity-provider-strategy capacityProvider=MyCapacityProvider1,weight=1 capacityProvider=MyCapacityProvider2,weight=1
```
Output:
```
{
"cluster": {
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster",
"clusterName": "MyCluster",
"status": "PROVISIONING",
"registeredContainerInstancesCount": 0,
"pendingTasksCount": 0,
"runningTasksCount": 0,
"activeServicesCount": 0,
"statistics": [],
"settings": [
{
"name": "containerInsights",
"value": "enabled"
}
],
"capacityProviders": [
"MyCapacityProvider1",
"MyCapacityProvider2"
],
"defaultCapacityProviderStrategy": [
{
"capacityProvider": "MyCapacityProvider1",
"weight": 1,
"base": 0
},
{
"capacityProvider": "MyCapacityProvider2",
"weight": 1,
"base": 0
}
],
"attachments": [
{
"id": "0fb0c8f4-6edd-4de1-9b09-17e470ee1918",
"type": "asp",
"status": "PRECREATED",
"details": [
{
"name": "capacityProviderName",
"value": "MyCapacityProvider1"
},
{
"name": "scalingPlanName",
"value": "ECSManagedAutoScalingPlan-a1b2c3d4-5678-90ab-cdef-EXAMPLE11111"
}
]
},
{
"id": "ae592060-2382-4663-9476-b015c685593c",
"type": "asp",
"status": "PRECREATED",
"details": [
{
"name": "capacityProviderName",
"value": "MyCapacityProvider2"
},
{
"name": "scalingPlanName",
"value": "ECSManagedAutoScalingPlan-a1b2c3d4-5678-90ab-cdef-EXAMPLE22222"
}
]
}
],
"attachmentsStatus": "UPDATE_IN_PROGRESS"
}
}
```
Untuk informasi selengkapnya, lihat [Penyedia kapasitas klaster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html) di *Panduan Pengembang Amazon ECS*.
**Contoh 3: Untuk membuat cluster baru dengan beberapa tag**
`create-cluster`Contoh berikut membuat cluster dengan beberapa tag. *Untuk informasi selengkapnya tentang menambahkan tag menggunakan sintaks singkatan, lihat [Menggunakan Sintaks Shorthand dengan Antarmuka AWS Baris Perintah di Panduan Pengguna CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-shorthand.html).AWS *
```
aws ecs create-cluster \
--cluster-name MyCluster \
--tags key=key1,value=value1 key=key2,value=value2
```
Output:
```
{
"cluster": {
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster",
"clusterName": "MyCluster",
"status": "ACTIVE",
"registeredContainerInstancesCount": 0,
"pendingTasksCount": 0,
"runningTasksCount": 0,
"activeServicesCount": 0,
"statistics": [],
"tags": [
{
"key": "key1",
"value": "value1"
},
{
"key": "key2",
"value": "value2"
}
]
}
}
```
Untuk informasi selengkapnya, lihat [Membuat Cluster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create_cluster.html) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [CreateCluster](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/create-cluster.html)di *Referensi AWS CLI Perintah*.
### `create-service`
Contoh kode berikut menunjukkan cara menggunakan`create-service`.
**AWS CLI**
**Contoh 1: Untuk membuat layanan dengan tugas Fargate**
`create-service`Contoh berikut menunjukkan cara membuat layanan menggunakan tugas Fargate.
```
aws ecs create-service \
--cluster MyCluster \
--service-name MyService \
--task-definition sample-fargate:1 \
--desired-count 2 \
--launch-type FARGATE \
--platform-version LATEST \
--network-configuration 'awsvpcConfiguration={subnets=[subnet-12344321],securityGroups=[sg-12344321],assignPublicIp=ENABLED}' \
--tags key=key1,value=value1 key=key2,value=value2 key=key3,value=value3
```
Output:
```
{
"service": {
"serviceArn": "arn:aws:ecs:us-west-2:123456789012:service/MyCluster/MyService",
"serviceName": "MyService",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster",
"loadBalancers": [],
"serviceRegistries": [],
"status": "ACTIVE",
"desiredCount": 2,
"runningCount": 0,
"pendingCount": 0,
"launchType": "FARGATE",
"platformVersion": "LATEST",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/sample-fargate:1",
"deploymentConfiguration": {
"maximumPercent": 200,
"minimumHealthyPercent": 100
},
"deployments": [
{
"id": "ecs-svc/1234567890123456789",
"status": "PRIMARY",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/sample-fargate:1",
"desiredCount": 2,
"pendingCount": 0,
"runningCount": 0,
"createdAt": 1557119253.821,
"updatedAt": 1557119253.821,
"launchType": "FARGATE",
"platformVersion": "1.3.0",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "ENABLED"
}
}
}
],
"roleArn": "arn:aws:iam::123456789012:role/aws-service-role/ecs.amazonaws.com/AWSServiceRoleForECS",
"events": [],
"createdAt": 1557119253.821,
"placementConstraints": [],
"placementStrategy": [],
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "ENABLED"
}
},
"schedulingStrategy": "REPLICA",
"tags": [
{
"key": "key1",
"value": "value1"
},
{
"key": "key2",
"value": "value2"
},
{
"key": "key3",
"value": "value3"
}
],
"enableECSManagedTags": false,
"propagateTags": "NONE"
}
}
```
Untuk informasi selengkapnya, lihat [Membuat Layanan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-service-console-v2.html) di *Panduan Pengembang Amazon ECS*.
**Contoh 2: Untuk membuat layanan menggunakan tipe peluncuran EC2**
`create-service`Contoh berikut menunjukkan cara membuat layanan yang dipanggil `ecs-simple-service` dengan tugas yang menggunakan tipe peluncuran EC2. Layanan ini menggunakan definisi `sleep360` tugas dan mempertahankan 1 instantiasi tugas.
```
aws ecs create-service \
--cluster MyCluster \
--service-name ecs-simple-service \
--task-definition sleep360:2 \
--desired-count 1
```
Output:
```
{
"service": {
"serviceArn": "arn:aws:ecs:us-west-2:123456789012:service/MyCluster/ecs-simple-service",
"serviceName": "ecs-simple-service",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster",
"loadBalancers": [],
"serviceRegistries": [],
"status": "ACTIVE",
"desiredCount": 1,
"runningCount": 0,
"pendingCount": 0,
"launchType": "EC2",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/sleep360:2",
"deploymentConfiguration": {
"maximumPercent": 200,
"minimumHealthyPercent": 100
},
"deployments": [
{
"id": "ecs-svc/1234567890123456789",
"status": "PRIMARY",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/sleep360:2",
"desiredCount": 1,
"pendingCount": 0,
"runningCount": 0,
"createdAt": 1557206498.798,
"updatedAt": 1557206498.798,
"launchType": "EC2"
}
],
"events": [],
"createdAt": 1557206498.798,
"placementConstraints": [],
"placementStrategy": [],
"schedulingStrategy": "REPLICA",
"enableECSManagedTags": false,
"propagateTags": "NONE"
}
}
```
Untuk informasi selengkapnya, lihat [Membuat Layanan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-service-console-v2.html) di *Panduan Pengembang Amazon ECS*.
**Contoh 3: Untuk membuat layanan yang menggunakan pengontrol penyebaran eksternal**
`create-service`Contoh berikut membuat layanan yang menggunakan controller deployment eksternal.
```
aws ecs create-service \
--cluster MyCluster \
--service-name MyService \
--deployment-controller type=EXTERNAL \
--desired-count 1
```
Output:
```
{
"service": {
"serviceArn": "arn:aws:ecs:us-west-2:123456789012:service/MyCluster/MyService",
"serviceName": "MyService",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster",
"loadBalancers": [],
"serviceRegistries": [],
"status": "ACTIVE",
"desiredCount": 1,
"runningCount": 0,
"pendingCount": 0,
"launchType": "EC2",
"deploymentConfiguration": {
"maximumPercent": 200,
"minimumHealthyPercent": 100
},
"taskSets": [],
"deployments": [],
"roleArn": "arn:aws:iam::123456789012:role/aws-service-role/ecs.amazonaws.com/AWSServiceRoleForECS",
"events": [],
"createdAt": 1557128207.101,
"placementConstraints": [],
"placementStrategy": [],
"schedulingStrategy": "REPLICA",
"deploymentController": {
"type": "EXTERNAL"
},
"enableECSManagedTags": false,
"propagateTags": "NONE"
}
}
```
Untuk informasi selengkapnya, lihat [Membuat Layanan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-service-console-v2.html) di *Panduan Pengembang Amazon ECS*.
**Contoh 4: Untuk membuat layanan baru di belakang penyeimbang beban**
`create-service`Contoh berikut menunjukkan cara membuat layanan yang berada di belakang penyeimbang beban. Anda harus memiliki penyeimbang beban yang dikonfigurasi di Wilayah yang sama dengan instance container Anda. Contoh ini menggunakan `--cli-input-json` opsi dan file input JSON yang disebut `ecs-simple-service-elb.json` dengan konten berikut.
```
aws ecs create-service \
--cluster MyCluster \
--service-name ecs-simple-service-elb \
--cli-input-json file://ecs-simple-service-elb.json
```
Isi dari `ecs-simple-service-elb.json`:
```
{
"serviceName": "ecs-simple-service-elb",
"taskDefinition": "ecs-demo",
"loadBalancers": [
{
"loadBalancerName": "EC2Contai-EcsElast-123456789012",
"containerName": "simple-demo",
"containerPort": 80
}
],
"desiredCount": 10,
"role": "ecsServiceRole"
}
```
Output:
```
{
"service": {
"status": "ACTIVE",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/ecs-demo:1",
"pendingCount": 0,
"loadBalancers": [
{
"containerName": "ecs-demo",
"containerPort": 80,
"loadBalancerName": "EC2Contai-EcsElast-123456789012"
}
],
"roleArn": "arn:aws:iam::123456789012:role/ecsServiceRole",
"desiredCount": 10,
"serviceName": "ecs-simple-service-elb",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster",
"serviceArn": "arn:aws:ecs:us-west-2:123456789012:service/ecs-simple-service-elb",
"deployments": [
{
"status": "PRIMARY",
"pendingCount": 0,
"createdAt": 1428100239.123,
"desiredCount": 10,
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/ecs-demo:1",
"updatedAt": 1428100239.123,
"id": "ecs-svc/1234567890123456789",
"runningCount": 0
}
],
"events": [],
"runningCount": 0
}
}
```
Untuk informasi selengkapnya, lihat [Menggunakan load balancing untuk mendistribusikan lalu lintas layanan Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html) di Panduan Pengembang *Amazon ECS.*
**Contoh 5: Untuk mengonfigurasi volume Amazon EBS pada pembuatan layanan**
`create-service`Contoh berikut menunjukkan cara mengonfigurasi volume Amazon EBS untuk setiap tugas yang dikelola oleh layanan. Anda harus memiliki peran infrastruktur Amazon ECS yang dikonfigurasi dengan kebijakan `AmazonECSInfrastructureRolePolicyForVolumes` terkelola yang dilampirkan. Anda harus menentukan definisi tugas dengan nama volume yang sama seperti pada `create-service` permintaan. Contoh ini menggunakan `--cli-input-json` opsi dan file input JSON yang disebut `ecs-simple-service-ebs.json` dengan konten berikut.
```
aws ecs create-service \
--cli-input-json file://ecs-simple-service-ebs.json
```
Isi dari `ecs-simple-service-ebs.json`:
```
{
"cluster": "mycluster",
"taskDefinition": "mytaskdef",
"serviceName": "ecs-simple-service-ebs",
"desiredCount": 2,
"launchType": "FARGATE",
"networkConfiguration":{
"awsvpcConfiguration":{
"assignPublicIp": "ENABLED",
"securityGroups": ["sg-12344321"],
"subnets":["subnet-12344321"]
}
},
"volumeConfigurations": [
{
"name": "myEbsVolume",
"managedEBSVolume": {
"roleArn":"arn:aws:iam::123456789012:role/ecsInfrastructureRole",
"volumeType": "gp3",
"sizeInGiB": 100,
"iops": 3000,
"throughput": 125,
"filesystemType": "ext4"
}
}
]
}
```
Output:
```
{
"service": {
"serviceArn": "arn:aws:ecs:us-west-2:123456789012:service/mycluster/ecs-simple-service-ebs",
"serviceName": "ecs-simple-service-ebs",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/mycluster",
"loadBalancers": [],
"serviceRegistries": [],
"status": "ACTIVE",
"desiredCount": 2,
"runningCount": 0,
"pendingCount": 0,
"launchType": "EC2",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/mytaskdef:3",
"deploymentConfiguration": {
"deploymentCircuitBreaker": {
"enable": false,
"rollback": false
},
"maximumPercent": 200,
"minimumHealthyPercent": 100
},
"deployments": [
{
"id": "ecs-svc/7851020056849183687",
"status": "PRIMARY",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/mytaskdef:3",
"desiredCount": 0,
"pendingCount": 0,
"runningCount": 0,
"failedTasks": 0,
"createdAt": "2025-01-21T11:32:38.034000-06:00",
"updatedAt": "2025-01-21T11:32:38.034000-06:00",
"launchType": "EC2",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "DISABLED"
}
},
"rolloutState": "IN_PROGRESS",
"rolloutStateReason": "ECS deployment ecs-svc/7851020056849183687 in progress.",
"volumeConfigurations": [
{
"name": "myEBSVolume",
"managedEBSVolume": {
"volumeType": "gp3",
"sizeInGiB": 100,
"iops": 3000,
"throughput": 125,
"roleArn": "arn:aws:iam::123456789012:role/ecsInfrastructureRole",
"filesystemType": "ext4"
}
}
]
}
],
"roleArn": "arn:aws:iam::123456789012:role/aws-service-role/ecs.amazonaws.com/AWSServiceRoleForECS",
"events": [],
"createdAt": "2025-01-21T11:32:38.034000-06:00",
"placementConstraints": [],
"placementStrategy": [],
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "DISABLED"
}
},
"healthCheckGracePeriodSeconds": 0,
"schedulingStrategy": "REPLICA",
"deploymentController": {
"type": "ECS"
},
"createdBy": "arn:aws:iam::123456789012:user/AIDACKCEVSQ6C2EXAMPLE",
"enableECSManagedTags": false,
"propagateTags": "NONE",
"enableExecuteCommand": false,
"availabilityZoneRebalancing": "DISABLED"
}
}
```
Untuk informasi selengkapnya, lihat [Menggunakan volume Amazon EBS dengan Amazon ECS di Panduan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html) Pengembang *Amazon ECS.*
+ Untuk detail API, lihat [CreateService](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/create-service.html)di *Referensi AWS CLI Perintah*.
### `create-task-set`
Contoh kode berikut menunjukkan cara menggunakan`create-task-set`.
**AWS CLI**
**Untuk membuat set tugas**
`create-task-set`Contoh berikut membuat tugas yang ditetapkan dalam layanan yang menggunakan controller deployment eksternal.
```
aws ecs create-task-set \
--cluster MyCluster \
--service MyService \
--task-definition MyTaskDefinition:2 \
--network-configuration "awsvpcConfiguration={subnets=[subnet-12344321],securityGroups=[sg-12344321]}"
```
Output:
```
{
"taskSet": {
"id": "ecs-svc/1234567890123456789",
"taskSetArn": "arn:aws:ecs:us-west-2:123456789012:task-set/MyCluster/MyService/ecs-svc/1234567890123456789",
"status": "ACTIVE",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/MyTaskDefinition:2",
"computedDesiredCount": 0,
"pendingCount": 0,
"runningCount": 0,
"createdAt": 1557128360.711,
"updatedAt": 1557128360.711,
"launchType": "EC2",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "DISABLED"
}
},
"loadBalancers": [],
"serviceRegistries": [],
"scale": {
"value": 0.0,
"unit": "PERCENT"
},
"stabilityStatus": "STABILIZING",
"stabilityStatusAt": 1557128360.711
}
}
```
+ Untuk detail API, lihat [CreateTaskSet](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/create-task-set.html)di *Referensi AWS CLI Perintah*.
### `delete-account-setting`
Contoh kode berikut menunjukkan cara menggunakan`delete-account-setting`.
**AWS CLI**
**Untuk menghapus pengaturan akun untuk pengguna IAM tertentu atau peran IAM**
Contoh berikut `delete-account-setting` menghapus pengaturan akun untuk pengguna IAM tertentu atau peran IAM.
```
aws ecs delete-account-setting \
--name serviceLongArnFormat \
--principal-arn arn:aws:iam::123456789012:user/MyUser
```
Output:
```
{
"setting": {
"name": "serviceLongArnFormat",
"value": "enabled",
"principalArn": "arn:aws:iam::123456789012:user/MyUser"
}
}
```
Untuk informasi selengkapnya, lihat [Nama Sumber Daya Amazon (ARNs) dan IDs](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-resource-ids.html) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [DeleteAccountSetting](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/delete-account-setting.html)di *Referensi AWS CLI Perintah*.
### `delete-attributes`
Contoh kode berikut menunjukkan cara menggunakan`delete-attributes`.
**AWS CLI**
**Untuk menghapus satu atau beberapa atribut kustom dari sumber daya Amazon ECS**
Berikut ini `delete-attributes` menghapus atribut dengan nama `stack` dari instance container.
```
aws ecs delete-attributes \
--attributes name=stack,targetId=arn:aws:ecs:us-west-2:130757420319:container-instance/1c3be8ed-df30-47b4-8f1e-6e68ebd01f34
```
Output:
```
{
"attributes": [
{
"name": "stack",
"targetId": "arn:aws:ecs:us-west-2:130757420319:container-instance/1c3be8ed-df30-47b4-8f1e-6e68ebd01f34",
"value": "production"
}
]
}
```
+ Untuk detail API, lihat [DeleteAttributes](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/delete-attributes.html)di *Referensi AWS CLI Perintah*.
### `delete-capacity-provider`
Contoh kode berikut menunjukkan cara menggunakan`delete-capacity-provider`.
**AWS CLI**
**Contoh 1: Untuk menghapus penyedia kapasitas menggunakan Amazon Resource Name (ARN)**
`delete-capacity-provider`Contoh berikut menghapus penyedia kapasitas dengan menentukan Amazon Resource Name (ARN) dari penyedia kapasitas. ARN serta status penghapusan penyedia kapasitas dapat diambil menggunakan perintah. `describe-capacity-providers`
```
aws ecs delete-capacity-provider \
--capacity-provider arn:aws:ecs:us-west-2:123456789012:capacity-provider/ExampleCapacityProvider
```
Output:
```
{
"capacityProvider": {
"capacityProviderArn": "arn:aws:ecs:us-west-2:123456789012:capacity-provider/ExampleCapacityProvider",
"name": "ExampleCapacityProvider",
"status": "ACTIVE",
"autoScalingGroupProvider": {
"autoScalingGroupArn": "arn:aws:autoscaling:us-west-2:123456789012:autoScalingGroup:a1b2c3d4-5678-90ab-cdef-EXAMPLE11111:autoScalingGroupName/MyAutoScalingGroup",
"managedScaling": {
"status": "ENABLED",
"targetCapacity": 100,
"minimumScalingStepSize": 1,
"maximumScalingStepSize": 10000
},
"managedTerminationProtection": "DISABLED"
},
"updateStatus": "DELETE_IN_PROGRESS",
"tags": []
}
}
```
Untuk informasi selengkapnya, lihat [Penyedia kapasitas klaster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html) di *Panduan Pengembang Amazon ECS*.
**Contoh 2: Untuk menghapus penyedia kapasitas menggunakan nama**
`delete-capacity-provider`Contoh berikut menghapus penyedia kapasitas dengan menentukan nama pendek penyedia kapasitas. Nama pendek serta status penghapusan penyedia kapasitas dapat diambil menggunakan perintah. `describe-capacity-providers`
```
aws ecs delete-capacity-provider \
--capacity-provider ExampleCapacityProvider
```
Output:
```
{
"capacityProvider": {
"capacityProviderArn": "arn:aws:ecs:us-west-2:123456789012:capacity-provider/ExampleCapacityProvider",
"name": "ExampleCapacityProvider",
"status": "ACTIVE",
"autoScalingGroupProvider": {
"autoScalingGroupArn": "arn:aws:autoscaling:us-west-2:123456789012:autoScalingGroup:a1b2c3d4-5678-90ab-cdef-EXAMPLE11111:autoScalingGroupName/MyAutoScalingGroup",
"managedScaling": {
"status": "ENABLED",
"targetCapacity": 100,
"minimumScalingStepSize": 1,
"maximumScalingStepSize": 10000
},
"managedTerminationProtection": "DISABLED"
},
"updateStatus": "DELETE_IN_PROGRESS",
"tags": []
}
}
```
Untuk informasi selengkapnya, lihat [Penyedia kapasitas klaster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [DeleteCapacityProvider](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/delete-capacity-provider.html)di *Referensi AWS CLI Perintah*.
### `delete-cluster`
Contoh kode berikut menunjukkan cara menggunakan`delete-cluster`.
**AWS CLI**
**Untuk menghapus klaster kosong**
`delete-cluster`Contoh berikut menghapus cluster kosong yang ditentukan.
```
aws ecs delete-cluster --cluster MyCluster
```
Output:
```
{
"cluster": {
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster",
"status": "INACTIVE",
"clusterName": "MyCluster",
"registeredContainerInstancesCount": 0,
"pendingTasksCount": 0,
"runningTasksCount": 0,
"activeServicesCount": 0
"statistics": [],
"tags": []
}
}
```
Untuk informasi selengkapnya, lihat [Menghapus Cluster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/delete_cluster.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [DeleteCluster](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/delete-cluster.html)di *Referensi AWS CLI Perintah*.
### `delete-service`
Contoh kode berikut menunjukkan cara menggunakan`delete-service`.
**AWS CLI**
**Untuk menghapus layanan**
`ecs delete-service`Contoh berikut menghapus layanan tertentu dari cluster. Anda dapat menyertakan `--force` parameter untuk menghapus layanan meskipun belum diskalakan ke nol tugas.
```
aws ecs delete-service --cluster MyCluster --service MyService1 --force
```
Untuk informasi selengkapnya, lihat [Menghapus Layanan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/delete-service.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [DeleteService](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/delete-service.html)di *Referensi AWS CLI Perintah*.
### `delete-task-definitions`
Contoh kode berikut menunjukkan cara menggunakan`delete-task-definitions`.
**AWS CLI**
**Untuk menghapus definisi tugas**
`delete-task-definitions`Contoh berikut menghapus definisi tugas INACTIVE.
```
aws ecs delete-task-definitions \
--task-definition curltest:1
```
Output:
```
{
"taskDefinitions": [
{
"taskDefinitionArn": "arn:aws:ecs:us-east-1:123456789012:task-definition/curltest:1",
"containerDefinitions": [
{
"name": "ctest",
"image": "mreferre/eksutils",
"cpu": 0,
"portMappings": [],
"essential": true,
"entryPoint": [
"sh",
"-c"
],
"command": [
"curl ${ECS_CONTAINER_METADATA_URI_V4}/task"
],
"environment": [],
"mountPoints": [],
"volumesFrom": [],
"logConfiguration": {
"logDriver": "awslogs",
"options": {
"awslogs-create-group": "true",
"awslogs-group": "/ecs/curltest",
"awslogs-region": "us-east-1",
"awslogs-stream-prefix": "ecs"
}
}
}
],
"family": "curltest",
"taskRoleArn": "arn:aws:iam::123456789012:role/ecsTaskExecutionRole",
"executionRoleArn": "arn:aws:iam::123456789012:role/ecsTaskExecutionRole",
"networkMode": "awsvpc",
"revision": 1,
"volumes": [],
"status": "DELETE_IN_PROGRESS",
"compatibilities": [
"EC2",
"FARGATE"
],
"requiresCompatibilities": [
"FARGATE"
],
"cpu": "256",
"memory": "512",
"registeredAt": "2021-09-10T12:56:24.704000+00:00",
"deregisteredAt": "2023-03-14T15:20:59.419000+00:00",
"registeredBy": "arn:aws:sts::123456789012:assumed-role/Admin/jdoe"
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [Definisi Tugas Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [DeleteTaskDefinitions](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/delete-task-definitions.html)di *Referensi AWS CLI Perintah*.
### `delete-task-set`
Contoh kode berikut menunjukkan cara menggunakan`delete-task-set`.
**AWS CLI**
**Untuk menghapus set tugas**
`delete-task-set`Contoh berikut menunjukkan cara menghapus set tugas. Anda dapat menyertakan `--force` parameter untuk menghapus set tugas meskipun belum diskalakan ke nol.
```
aws ecs delete-task-set \
--cluster MyCluster \
--service MyService \
--task-set arn:aws:ecs:us-west-2:123456789012:task-set/MyCluster/MyService/ecs-svc/1234567890123456789 \
--force
```
Output:
```
{
"taskSet": {
"id": "ecs-svc/1234567890123456789",
"taskSetArn": "arn:aws:ecs:us-west-2:123456789012:task-set/MyCluster/MyService/ecs-svc/1234567890123456789",
"status": "DRAINING",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/sample-fargate:2",
"computedDesiredCount": 0,
"pendingCount": 0,
"runningCount": 0,
"createdAt": 1557130260.276,
"updatedAt": 1557130290.707,
"launchType": "EC2",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12345678"
],
"securityGroups": [
"sg-12345678"
],
"assignPublicIp": "DISABLED"
}
},
"loadBalancers": [],
"serviceRegistries": [],
"scale": {
"value": 0.0,
"unit": "PERCENT"
},
"stabilityStatus": "STABILIZING",
"stabilityStatusAt": 1557130290.707
}
}
```
+ Untuk detail API, lihat [DeleteTaskSet](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/delete-task-set.html)di *Referensi AWS CLI Perintah*.
### `deregister-container-instance`
Contoh kode berikut menunjukkan cara menggunakan`deregister-container-instance`.
**AWS CLI**
**Untuk membatalkan pendaftaran instance kontainer dari cluster**
`deregister-container-instance`Contoh berikut deregisters instance container dari cluster tertentu. Jika masih ada tugas yang berjalan di instance container, Anda harus menghentikan tugas tersebut sebelum membatalkan pendaftaran, atau menggunakan opsi tersebut. `--force`
```
aws ecs deregister-container-instance \
--cluster arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster \
--container-instance arn:aws:ecs:us-west-2:123456789012:container-instance/a1b2c3d4-5678-90ab-cdef-11111EXAMPLE \
--force
```
Output:
```
{
"containerInstance": {
"remainingResources": [
{
"integerValue": 1024,
"doubleValue": 0.0,
"type": "INTEGER",
"longValue": 0,
"name": "CPU"
},
{
"integerValue": 985,
"doubleValue": 0.0,
"type": "INTEGER",
"longValue": 0,
"name": "MEMORY"
},
{
"type": "STRINGSET",
"integerValue": 0,
"name": "PORTS",
"stringSetValue": [
"22",
"2376",
"2375",
"51678",
"51679"
],
"longValue": 0,
"doubleValue": 0.0
},
{
"type": "STRINGSET",
"integerValue": 0,
"name": "PORTS_UDP",
"stringSetValue": [],
"longValue": 0,
"doubleValue": 0.0
}
],
"agentConnected": true,
"attributes": [
{
"name": "ecs.capability.secrets.asm.environment-variables"
},
{
"name": "com.amazonaws.ecs.capability.logging-driver.syslog"
},
{
"value": "ami-01a82c3fce2c3ba58",
"name": "ecs.ami-id"
},
{
"name": "ecs.capability.secrets.asm.bootstrap.log-driver"
},
{
"name": "com.amazonaws.ecs.capability.logging-driver.none"
},
{
"name": "ecs.capability.ecr-endpoint"
},
{
"name": "com.amazonaws.ecs.capability.logging-driver.json-file"
},
{
"value": "vpc-1234567890123467",
"name": "ecs.vpc-id"
},
{
"name": "ecs.capability.execution-role-awslogs"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.17"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.18"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.19"
},
{
"name": "ecs.capability.docker-plugin.local"
},
{
"name": "ecs.capability.task-eni"
},
{
"name": "ecs.capability.task-cpu-mem-limit"
},
{
"name": "ecs.capability.secrets.ssm.bootstrap.log-driver"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.30"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.31"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.32"
},
{
"name": "ecs.capability.execution-role-ecr-pull"
},
{
"name": "ecs.capability.container-health-check"
},
{
"value": "subnet-1234567890123467",
"name": "ecs.subnet-id"
},
{
"value": "us-west-2a",
"name": "ecs.availability-zone"
},
{
"value": "t2.micro",
"name": "ecs.instance-type"
},
{
"name": "com.amazonaws.ecs.capability.task-iam-role-network-host"
},
{
"name": "ecs.capability.aws-appmesh"
},
{
"name": "com.amazonaws.ecs.capability.logging-driver.awslogs"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.24"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.25"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.26"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.27"
},
{
"name": "com.amazonaws.ecs.capability.privileged-container"
},
{
"name": "ecs.capability.container-ordering"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.28"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.29"
},
{
"value": "x86_64",
"name": "ecs.cpu-architecture"
},
{
"value": "93f43776-2018.10.0",
"name": "ecs.capability.cni-plugin-version"
},
{
"name": "ecs.capability.secrets.ssm.environment-variables"
},
{
"name": "ecs.capability.pid-ipc-namespace-sharing"
},
{
"name": "com.amazonaws.ecs.capability.ecr-auth"
},
{
"value": "linux",
"name": "ecs.os-type"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.20"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.21"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.22"
},
{
"name": "ecs.capability.task-eia"
},
{
"name": "ecs.capability.private-registry-authentication.secretsmanager"
},
{
"name": "com.amazonaws.ecs.capability.task-iam-role"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.23"
}
],
"pendingTasksCount": 0,
"tags": [],
"containerInstanceArn": "arn:aws:ecs:us-west-2:123456789012:container-instance/a1b2c3d4-5678-90ab-cdef-11111EXAMPLE",
"registeredResources": [
{
"integerValue": 1024,
"doubleValue": 0.0,
"type": "INTEGER",
"longValue": 0,
"name": "CPU"
},
{
"integerValue": 985,
"doubleValue": 0.0,
"type": "INTEGER",
"longValue": 0,
"name": "MEMORY"
},
{
"type": "STRINGSET",
"integerValue": 0,
"name": "PORTS",
"stringSetValue": [
"22",
"2376",
"2375",
"51678",
"51679"
],
"longValue": 0,
"doubleValue": 0.0
},
{
"type": "STRINGSET",
"integerValue": 0,
"name": "PORTS_UDP",
"stringSetValue": [],
"longValue": 0,
"doubleValue": 0.0
}
],
"status": "INACTIVE",
"registeredAt": 1557768075.681,
"version": 4,
"versionInfo": {
"agentVersion": "1.27.0",
"agentHash": "aabe65ee",
"dockerVersion": "DockerVersion: 18.06.1-ce"
},
"attachments": [],
"runningTasksCount": 0,
"ec2InstanceId": "i-12345678901234678"
}
}
```
Untuk informasi selengkapnya, lihat [Membatalkan pendaftaran Instans Kontainer di Panduan Pengembang](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deregister_container_instance.html) *ECS*.
+ Untuk detail API, lihat [DeregisterContainerInstance](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/deregister-container-instance.html)di *Referensi AWS CLI Perintah*.
### `deregister-task-definition`
Contoh kode berikut menunjukkan cara menggunakan`deregister-task-definition`.
**AWS CLI**
**Untuk membatalkan pendaftaran definisi tugas**
`deregister-task-definition`Contoh berikut membatalkan pendaftaran revisi pertama definisi `curler` tugas di wilayah default Anda.
```
aws ecs deregister-task-definition --task-definition curler:1
```
Perhatikan bahwa dalam output yang dihasilkan, status definisi tugas menunjukkan`INACTIVE`:
```
{
"taskDefinition": {
"status": "INACTIVE",
"family": "curler",
"volumes": [],
"taskDefinitionArn": "arn:aws:ecs:us-west-2:123456789012:task-definition/curler:1",
"containerDefinitions": [
{
"environment": [],
"name": "curler",
"mountPoints": [],
"image": "curl:latest",
"cpu": 100,
"portMappings": [],
"entryPoint": [],
"memory": 256,
"command": [
"curl -v http://example.com/"
],
"essential": true,
"volumesFrom": []
}
],
"revision": 1
}
}
```
Untuk informasi selengkapnya, lihat [Definisi Tugas Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [DeregisterTaskDefinition](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/deregister-task-definition.html)di *Referensi AWS CLI Perintah*.
### `describe-capacity-providers`
Contoh kode berikut menunjukkan cara menggunakan`describe-capacity-providers`.
**AWS CLI**
**Contoh 1: Untuk menggambarkan semua penyedia kapasitas**
`describe-capacity-providers`Contoh berikut mengambil rincian tentang semua penyedia kapasitas.
```
aws ecs describe-capacity-providers
```
Output:
```
{
"capacityProviders": [
{
"capacityProviderArn": "arn:aws:ecs:us-west-2:123456789012:capacity-provider/MyCapacityProvider",
"name": "MyCapacityProvider",
"status": "ACTIVE",
"autoScalingGroupProvider": {
"autoScalingGroupArn": "arn:aws:autoscaling:us-west-2:123456789012:autoScalingGroup:a1b2c3d4-5678-90ab-cdef-EXAMPLE11111:autoScalingGroupName/MyAutoScalingGroup",
"managedScaling": {
"status": "ENABLED",
"targetCapacity": 100,
"minimumScalingStepSize": 1,
"maximumScalingStepSize": 1000
},
"managedTerminationProtection": "ENABLED"
},
"tags": []
},
{
"capacityProviderArn": "arn:aws:ecs:us-west-2:123456789012:capacity-provider/FARGATE",
"name": "FARGATE",
"status": "ACTIVE",
"tags": []
},
{
"capacityProviderArn": "arn:aws:ecs:us-west-2:123456789012:capacity-provider/FARGATE_SPOT",
"name": "FARGATE_SPOT",
"status": "ACTIVE",
"tags": []
}
]
}
```
Untuk informasi selengkapnya, lihat [Penyedia kapasitas klaster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html) di *Panduan Pengembang Amazon ECS*.
**Contoh 2: Untuk menggambarkan penyedia kapasitas tertentu**
`describe-capacity-providers`Contoh berikut mengambil rincian tentang penyedia kapasitas tertentu. Menggunakan `--include TAGS` parameter akan menambahkan tag yang terkait dengan penyedia kapasitas ke output.
```
aws ecs describe-capacity-providers \
--capacity-providers MyCapacityProvider \
--include TAGS
```
Output:
```
{
"capacityProviders": [
{
"capacityProviderArn": "arn:aws:ecs:us-west-2:123456789012:capacity-provider/MyCapacityProvider",
"name": "MyCapacityProvider",
"status": "ACTIVE",
"autoScalingGroupProvider": {
"autoScalingGroupArn": "arn:aws:autoscaling:us-west-2:123456789012:autoScalingGroup:a1b2c3d4-5678-90ab-cdef-EXAMPLE11111:autoScalingGroupName/MyAutoScalingGroup",
"managedScaling": {
"status": "ENABLED",
"targetCapacity": 100,
"minimumScalingStepSize": 1,
"maximumScalingStepSize": 1000
},
"managedTerminationProtection": "ENABLED"
},
"tags": [
{
"key": "environment",
"value": "production"
}
]
}
]
}
```
Untuk informasi selengkapnya, lihat [Penyedia kapasitas klaster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [DescribeCapacityProviders](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/describe-capacity-providers.html)di *Referensi AWS CLI Perintah*.
### `describe-clusters`
Contoh kode berikut menunjukkan cara menggunakan`describe-clusters`.
**AWS CLI**
**Contoh 1: Untuk mendeskripsikan sebuah cluster**
`describe-clusters`Contoh berikut mengambil rincian tentang cluster tertentu.
```
aws ecs describe-clusters \
--cluster default
```
Output:
```
{
"clusters": [
{
"status": "ACTIVE",
"clusterName": "default",
"registeredContainerInstancesCount": 0,
"pendingTasksCount": 0,
"runningTasksCount": 0,
"activeServicesCount": 1,
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/default"
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [Cluster Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_clusters.html) di Panduan Pengembang *Amazon ECS.*
**Contoh 2: Untuk mendeskripsikan cluster dengan opsi lampiran**
`describe-clusters`Contoh berikut menentukan pilihan ATTACHMENTS. Ini mengambil rincian tentang cluster yang ditentukan dan daftar sumber daya yang melekat pada cluster dalam bentuk lampiran. Saat menggunakan penyedia kapasitas dengan klaster, sumber daya, baik AutoScaling rencana atau kebijakan penskalaan, akan direpresentasikan sebagai asp atau as\$1policy ATTACHMENTS.
```
aws ecs describe-clusters \
--include ATTACHMENTS \
--clusters sampleCluster
```
Output:
```
{
"clusters": [
{
"clusterArn": "arn:aws:ecs:af-south-1:123456789222:cluster/sampleCluster",
"clusterName": "sampleCluster",
"status": "ACTIVE",
"registeredContainerInstancesCount": 0,
"runningTasksCount": 0,
"pendingTasksCount": 0,
"activeServicesCount": 0,
"statistics": [],
"tags": [],
"settings": [],
"capacityProviders": [
"sampleCapacityProvider"
],
"defaultCapacityProviderStrategy": [],
"attachments": [
{
"id": "a1b2c3d4-5678-901b-cdef-EXAMPLE22222",
"type": "as_policy",
"status": "CREATED",
"details": [
{
"name": "capacityProviderName",
"value": "sampleCapacityProvider"
},
{
"name": "scalingPolicyName",
"value": "ECSManagedAutoScalingPolicy-3048e262-fe39-4eaf-826d-6f975d303188"
}
]
}
],
"attachmentsStatus": "UPDATE_COMPLETE"
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [Cluster Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_clusters.html) di Panduan Pengembang *Amazon ECS.*
+ Untuk detail API, lihat [DescribeClusters](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/describe-clusters.html)di *Referensi AWS CLI Perintah*.
### `describe-container-instances`
Contoh kode berikut menunjukkan cara menggunakan`describe-container-instances`.
**AWS CLI**
**Untuk menggambarkan contoh kontainer**
`describe-container-instances`Contoh berikut mengambil rincian untuk instance container di `update` cluster, menggunakan container instance UUID sebagai identifier.
```
aws ecs describe-container-instances \
--cluster update \
--container-instances a1b2c3d4-5678-90ab-cdef-11111EXAMPLE
```
Output:
```
{
"failures": [],
"containerInstances": [
{
"status": "ACTIVE",
"registeredResources": [
{
"integerValue": 2048,
"longValue": 0,
"type": "INTEGER",
"name": "CPU",
"doubleValue": 0.0
},
{
"integerValue": 3955,
"longValue": 0,
"type": "INTEGER",
"name": "MEMORY",
"doubleValue": 0.0
},
{
"name": "PORTS",
"longValue": 0,
"doubleValue": 0.0,
"stringSetValue": [
"22",
"2376",
"2375",
"51678"
],
"type": "STRINGSET",
"integerValue": 0
}
],
"ec2InstanceId": "i-A1B2C3D4",
"agentConnected": true,
"containerInstanceArn": "arn:aws:ecs:us-west-2:123456789012:container-instance/a1b2c3d4-5678-90ab-cdef-11111EXAMPLE",
"pendingTasksCount": 0,
"remainingResources": [
{
"integerValue": 2048,
"longValue": 0,
"type": "INTEGER",
"name": "CPU",
"doubleValue": 0.0
},
{
"integerValue": 3955,
"longValue": 0,
"type": "INTEGER",
"name": "MEMORY",
"doubleValue": 0.0
},
{
"name": "PORTS",
"longValue": 0,
"doubleValue": 0.0,
"stringSetValue": [
"22",
"2376",
"2375",
"51678"
],
"type": "STRINGSET",
"integerValue": 0
}
],
"runningTasksCount": 0,
"versionInfo": {
"agentVersion": "1.0.0",
"agentHash": "4023248",
"dockerVersion": "DockerVersion: 1.5.0"
}
}
]
}
```
Untuk informasi selengkapnya, lihat [Instans Kontainer Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_instances.html) di Panduan Pengembang *Amazon ECS.*
+ Untuk detail API, lihat [DescribeContainerInstances](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/describe-container-instances.html)di *Referensi AWS CLI Perintah*.
### `describe-service-deployments`
Contoh kode berikut menunjukkan cara menggunakan`describe-service-deployments`.
**AWS CLI**
**Untuk menjelaskan detail penyebaran layanan**
`describe-service-deployments`Contoh berikut mengembalikan rincian penyebaran layanan untuk penyebaran layanan dengan ARN. `arn:aws:ecs:us-east-1:123456789012:service-deployment/example-cluster/example-service/ejGvqq2ilnbKT9qj0vLJe`
```
aws ecs describe-service-deployments \
--service-deployment-arn arn:aws:ecs:us-east-1:123456789012:service-deployment/example-cluster/example-service/ejGvqq2ilnbKT9qj0vLJe
```
Output:
```
{
"serviceDeployments": [
{
"serviceDeploymentArn": "arn:aws:ecs:us-east-1:123456789012:service-deployment/example-cluster/example-service/ejGvqq2ilnbKT9qj0vLJe",
"serviceArn": "arn:aws:ecs:us-east-1:123456789012:service/example-cluster/example-service",
"clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/example-cluster",
"createdAt": "2024-10-31T08:03:30.917000-04:00",
"startedAt": "2024-10-31T08:03:32.510000-04:00",
"finishedAt": "2024-10-31T08:05:04.527000-04:00",
"updatedAt": "2024-10-31T08:05:04.527000-04:00",
"sourceServiceRevisions": [],
"targetServiceRevision": {
"arn": "arn:aws:ecs:us-east-1:123456789012:service-revision/example-cluster/example-service/1485800978477494678",
"requestedTaskCount": 1,
"runningTaskCount": 1,
"pendingTaskCount": 0
},
"status": "SUCCESSFUL",
"deploymentConfiguration": {
"deploymentCircuitBreaker": {
"enable": true,
"rollback": true
},
"maximumPercent": 200,
"minimumHealthyPercent": 100,
"alarms": {
"alarmNames": [],
"rollback": false,
"enable": false
}
},
"deploymentCircuitBreaker": {
"status": "MONITORING_COMPLETE",
"failureCount": 0,
"threshold": 3
},
"alarms": {
"status": "DISABLED"
}
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [Melihat riwayat layanan menggunakan penerapan layanan Amazon ECS di Panduan Pengembang](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-deployment.html) *Amazon ECS*.
+ Untuk detail API, lihat [DescribeServiceDeployments](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/describe-service-deployments.html)di *Referensi AWS CLI Perintah*.
### `describe-service-revisions`
Contoh kode berikut menunjukkan cara menggunakan`describe-service-revisions`.
**AWS CLI**
**Untuk menjelaskan rincian revisi layanan**
`describe-service-revisions`Contoh berikut mengembalikan rincian revisi layanan untuk revisi layanan dengan ARN. `arn:aws:ecs:us-east-1:123456789012:service-revision/example-cluster/example-service/1485800978477494678`
```
aws ecs describe-service-revisions \
--service-revision-arns arn:aws:ecs:us-east-1:123456789012:service-revision/example-cluster/example-service/1485800978477494678
```
Output:
```
{
"serviceRevisions": [
{
"serviceRevisionArn": "arn:aws:ecs:us-east-1:123456789012:service-revision/example-cluster/example-service/1485800978477494678",
"serviceArn": "arn:aws:ecs:us-east-1:123456789012:service/example-cluster/example-service",
"clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/example-cluster",
"taskDefinition": "arn:aws:ecs:us-east-1:123456789012:task-definition/webserver:5",
"capacityProviderStrategy": [
{
"capacityProvider": "FARGATE",
"weight": 1,
"base": 0
}
],
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-0d0eab1bb38d5ca64",
"subnet-0db5010045995c2d5"
],
"securityGroups": [
"sg-02556bf85a191f59a"
],
"assignPublicIp": "ENABLED"
}
},
"containerImages": [
{
"containerName": "aws-otel-collector",
"imageDigest": "sha256:7a1b3560655071bcacd66902c20ebe9a69470d5691fe3bd36baace7c2f3c4640",
"image": "public.ecr.aws/aws-observability/aws-otel-collector:v0.32.0"
},
{
"containerName": "web",
"imageDigest": "sha256:28402db69fec7c17e179ea87882667f1e054391138f77ffaf0c3eb388efc3ffb",
"image": "nginx"
}
],
"guardDutyEnabled": false,
"serviceConnectConfiguration": {
"enabled": false
},
"createdAt": "2024-10-31T08:03:29.302000-04:00"
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [revisi layanan Amazon ECS di Panduan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-revision.html) Pengembang *Amazon ECS.*
+ Untuk detail API, lihat [DescribeServiceRevisions](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/describe-service-revisions.html)di *Referensi AWS CLI Perintah*.
### `describe-services`
Contoh kode berikut menunjukkan cara menggunakan`describe-services`.
**AWS CLI**
**Untuk mendeskripsikan layanan**
`describe-services`Contoh berikut mengambil rincian untuk `my-http-service` layanan di cluster default.
```
aws ecs describe-services --services my-http-service
```
Output:
```
{
"services": [
{
"status": "ACTIVE",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/amazon-ecs-sample:1",
"pendingCount": 0,
"loadBalancers": [],
"desiredCount": 10,
"createdAt": 1466801808.595,
"serviceName": "my-http-service",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/default",
"serviceArn": "arn:aws:ecs:us-west-2:123456789012:service/my-http-service",
"deployments": [
{
"status": "PRIMARY",
"pendingCount": 0,
"createdAt": 1466801808.595,
"desiredCount": 10,
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/amazon-ecs-sample:1",
"updatedAt": 1428326312.703,
"id": "ecs-svc/1234567890123456789",
"runningCount": 10
}
],
"events": [
{
"message": "(service my-http-service) has reached a steady state.",
"id": "a1b2c3d4-5678-90ab-cdef-11111EXAMPLE",
"createdAt": 1466801812.435
}
],
"runningCount": 10
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [Layanan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [DescribeServices](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/describe-services.html)di *Referensi AWS CLI Perintah*.
### `describe-task-definition`
Contoh kode berikut menunjukkan cara menggunakan`describe-task-definition`.
**AWS CLI**
**Untuk menggambarkan definisi tugas**
`describe-task-definition`Contoh berikut mengambil rincian definisi tugas.
```
aws ecs describe-task-definition \
--task-definition hello_world:8
```
Output:
```
{
"taskDefinition": {
"taskDefinitionArn": "arn:aws:ecs:us-east-1:012345678910:task-definition/hello_world:8",
"containerDefinitions": [
{
"cpu": 10,
"environment": [],
"essential": true,
"image": "wordpress",
"links": [
"mysql"
] ,
"memory": 500,
"mountPoints": [],
"name": "wordpress",
"portMappings": [
{
"containerPort": 80,
"hostPort": 80
}
],
"volumesFrom": []
},
{
"cpu": 10,
"environment": [
{
"name": "MYSQL_ROOT_PASSWORD",
"value": "password"
}
],
"essential": true,
"image": "mysql",
"memory": 500,
"mountPoints": [],
"name": "mysql",
"portMappings": [],
"volumesFrom": []
}
],
"family": "hello_world",
"revision": 8,
"volumes": [],
"status": "ACTIVE",
"placementConstraints": [],
"compatibilities": [
"EXTERNAL",
"EC2"
],
"registeredAt": "2024-06-21T11:15:12.669000-05:00",
"registeredBy": "arn:aws:sts::012345678910:assumed-role/demo-role/jane-doe"
},
"tags": []
}
```
Untuk informasi selengkapnya, lihat [Definisi Tugas Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [DescribeTaskDefinition](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/describe-task-definition.html)di *Referensi AWS CLI Perintah*.
### `describe-task-sets`
Contoh kode berikut menunjukkan cara menggunakan`describe-task-sets`.
**AWS CLI**
**Untuk mendeskripsikan set tugas**
`describe-task-sets`Contoh berikut menjelaskan tugas yang ditetapkan dalam layanan yang menggunakan deployer eksternal.
```
aws ecs describe-task-sets \
--cluster MyCluster \
--service MyService \
--task-sets arn:aws:ecs:us-west-2:123456789012:task-set/MyCluster/MyService/ecs-svc/1234567890123456789
```
Output:
```
{
"taskSets": [
{
"id": "ecs-svc/1234567890123456789",
"taskSetArn": "arn:aws:ecs:us-west-2:123456789012:task-set/MyCluster/MyService/ecs-svc/1234567890123456789",
"status": "ACTIVE",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/sample-fargate:2",
"computedDesiredCount": 0,
"pendingCount": 0,
"runningCount": 0,
"createdAt": 1557207715.195,
"updatedAt": 1557207740.014,
"launchType": "EC2",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-1234431"
],
"assignPublicIp": "DISABLED"
}
},
"loadBalancers": [],
"serviceRegistries": [],
"scale": {
"value": 0.0,
"unit": "PERCENT"
},
"stabilityStatus": "STEADY_STATE",
"stabilityStatusAt": 1557207740.014
}
],
"failures": []
}
```
+ Untuk detail API, lihat [DescribeTaskSets](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/describe-task-sets.html)di *Referensi AWS CLI Perintah*.
### `describe-tasks`
Contoh kode berikut menunjukkan cara menggunakan`describe-tasks`.
**AWS CLI**
**Contoh 1: Untuk menggambarkan tugas tugas tunggal**
`describe-tasks`Contoh berikut mengambil rincian tugas dalam sebuah cluster. Anda dapat menentukan tugas dengan menggunakan ID atau ARN penuh tugas. Contoh ini menggunakan ARN penuh tugas.
```
aws ecs describe-tasks \
--cluster MyCluster \
--tasks arn:aws:ecs:us-east-1:123456789012:task/MyCluster/4d590253bb114126b7afa7b58EXAMPLE
```
Output:
```
{
"tasks": [
{
"attachments": [],
"attributes": [
{
"name": "ecs.cpu-architecture",
"value": "x86_64"
}
],
"availabilityZone": "us-east-1b",
"clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/MyCluster",
"connectivity": "CONNECTED",
"connectivityAt": "2021-08-11T12:21:26.681000-04:00",
"containerInstanceArn": "arn:aws:ecs:us-east-1:123456789012:container-instance/test/025c7e2c5e054a6790a29fc1fEXAMPLE",
"containers": [
{
"containerArn": "arn:aws:ecs:us-east-1:123456789012:container/MyCluster/4d590253bb114126b7afa7b58eea9221/a992d1cc-ea46-474a-b6e8-24688EXAMPLE",
"taskArn": "arn:aws:ecs:us-east-1:123456789012:task/MyCluster/4d590253bb114126b7afa7b58EXAMPLE",
"name": "simple-app",
"image": "httpd:2.4",
"runtimeId": "91251eed27db90006ad67b1a08187290869f216557717dd5c39b37c94EXAMPLE",
"lastStatus": "RUNNING",
"networkBindings": [
{
"bindIP": "0.0.0.0",
"containerPort": 80,
"hostPort": 80,
"protocol": "tcp"
}
],
"networkInterfaces": [],
"healthStatus": "UNKNOWN",
"cpu": "10",
"memory": "300"
}
],
"cpu": "10",
"createdAt": "2021-08-11T12:21:26.681000-04:00",
"desiredStatus": "RUNNING",
"enableExecuteCommand": false,
"group": "service:testupdate",
"healthStatus": "UNKNOWN",
"lastStatus": "RUNNING",
"launchType": "EC2",
"memory": "300",
"overrides": {
"containerOverrides": [
{
"name": "simple-app"
}
],
"inferenceAcceleratorOverrides": []
},
"pullStartedAt": "2021-08-11T12:21:28.234000-04:00",
"pullStoppedAt": "2021-08-11T12:21:33.793000-04:00",
"startedAt": "2021-08-11T12:21:34.945000-04:00",
"startedBy": "ecs-svc/968695068243EXAMPLE",
"tags": [],
"taskArn": "arn:aws:ecs:us-east-1:123456789012:task/MyCluster/4d590253bb114126b7afa7b58eea9221",
"taskDefinitionArn": "arn:aws:ecs:us-east-1:123456789012:task-definition/console-sample-app-static2:1",
"version": 2
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [Definisi Tugas Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html) di Panduan *Pengembang Amazon ECS*.
**Contoh 2: Untuk mendeskripsikan beberapa tugas**
`describe-tasks`Contoh berikut mengambil rincian beberapa tugas dalam sebuah cluster. Anda dapat menentukan tugas dengan menggunakan ID atau ARN penuh tugas. Contoh ini menggunakan IDs tugas penuh.
```
aws ecs describe-tasks \
--cluster MyCluster \
--tasks "74de0355a10a4f979ac495c14EXAMPLE" "d789e94343414c25b9f6bd59eEXAMPLE"
```
Output:
```
{
"tasks": [
{
"attachments": [
{
"id": "d9e7735a-16aa-4128-bc7a-b2d51EXAMPLE",
"type": "ElasticNetworkInterface",
"status": "ATTACHED",
"details": [
{
"name": "subnetId",
"value": "subnet-0d0eab1bb3EXAMPLE"
},
{
"name": "networkInterfaceId",
"value": "eni-0fa40520aeEXAMPLE"
},
{
"name": "macAddress",
"value": "0e:89:76:28:07:b3"
},
{
"name": "privateDnsName",
"value": "ip-10-0-1-184.ec2.internal"
},
{
"name": "privateIPv4Address",
"value": "10.0.1.184"
}
]
}
],
"attributes": [
{
"name": "ecs.cpu-architecture",
"value": "x86_64"
}
],
"availabilityZone": "us-east-1b",
"clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/MyCluster",
"connectivity": "CONNECTED",
"connectivityAt": "2021-12-20T12:13:37.875000-05:00",
"containers": [
{
"containerArn": "arn:aws:ecs:us-east-1:123456789012:container/MyCluster/74de0355a10a4f979ac495c14EXAMPLE/aad3ba00-83b3-4dac-84d4-11f8cEXAMPLE",
"taskArn": "arn:aws:ecs:us-east-1:123456789012:task/MyCluster/74de0355a10a4f979ac495c14EXAMPLE",
"name": "web",
"image": "nginx",
"runtimeId": "74de0355a10a4f979ac495c14EXAMPLE-265927825",
"lastStatus": "RUNNING",
"networkBindings": [],
"networkInterfaces": [
{
"attachmentId": "d9e7735a-16aa-4128-bc7a-b2d51EXAMPLE",
"privateIpv4Address": "10.0.1.184"
}
],
"healthStatus": "UNKNOWN",
"cpu": "99",
"memory": "100"
}
],
"cpu": "256",
"createdAt": "2021-12-20T12:13:20.226000-05:00",
"desiredStatus": "RUNNING",
"enableExecuteCommand": false,
"group": "service:tdsevicetag",
"healthStatus": "UNKNOWN",
"lastStatus": "RUNNING",
"launchType": "FARGATE",
"memory": "512",
"overrides": {
"containerOverrides": [
{
"name": "web"
}
],
"inferenceAcceleratorOverrides": []
},
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"pullStartedAt": "2021-12-20T12:13:42.665000-05:00",
"pullStoppedAt": "2021-12-20T12:13:46.543000-05:00",
"startedAt": "2021-12-20T12:13:48.086000-05:00",
"startedBy": "ecs-svc/988401040018EXAMPLE",
"tags": [],
"taskArn": "arn:aws:ecs:us-east-1:123456789012:task/MyCluster/74de0355a10a4f979ac495c14EXAMPLE",
"taskDefinitionArn": "arn:aws:ecs:us-east-1:123456789012:task-definition/webserver:2",
"version": 3,
"ephemeralStorage": {
"sizeInGiB": 20
}
},
{
"attachments": [
{
"id": "214eb5a9-45cd-4bf8-87bc-57fefEXAMPLE",
"type": "ElasticNetworkInterface",
"status": "ATTACHED",
"details": [
{
"name": "subnetId",
"value": "subnet-0d0eab1bb3EXAMPLE"
},
{
"name": "networkInterfaceId",
"value": "eni-064c7766daEXAMPLE"
},
{
"name": "macAddress",
"value": "0e:76:83:01:17:a9"
},
{
"name": "privateDnsName",
"value": "ip-10-0-1-41.ec2.internal"
},
{
"name": "privateIPv4Address",
"value": "10.0.1.41"
}
]
}
],
"attributes": [
{
"name": "ecs.cpu-architecture",
"value": "x86_64"
}
],
"availabilityZone": "us-east-1b",
"clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/MyCluster",
"connectivity": "CONNECTED",
"connectivityAt": "2021-12-20T12:13:35.243000-05:00",
"containers": [
{
"containerArn": "arn:aws:ecs:us-east-1:123456789012:container/MyCluster/d789e94343414c25b9f6bd59eEXAMPLE/9afef792-609b-43a5-bb6a-3efdbEXAMPLE",
"taskArn": "arn:aws:ecs:us-east-1:123456789012:task/MyCluster/d789e94343414c25b9f6bd59eEXAMPLE",
"name": "web",
"image": "nginx",
"runtimeId": "d789e94343414c25b9f6bd59eEXAMPLE-265927825",
"lastStatus": "RUNNING",
"networkBindings": [],
"networkInterfaces": [
{
"attachmentId": "214eb5a9-45cd-4bf8-87bc-57fefEXAMPLE",
"privateIpv4Address": "10.0.1.41"
}
],
"healthStatus": "UNKNOWN",
"cpu": "99",
"memory": "100"
}
],
"cpu": "256",
"createdAt": "2021-12-20T12:13:20.226000-05:00",
"desiredStatus": "RUNNING",
"enableExecuteCommand": false,
"group": "service:tdsevicetag",
"healthStatus": "UNKNOWN",
"lastStatus": "RUNNING",
"launchType": "FARGATE",
"memory": "512",
"overrides": {
"containerOverrides": [
{
"name": "web"
}
],
"inferenceAcceleratorOverrides": []
},
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"pullStartedAt": "2021-12-20T12:13:44.611000-05:00",
"pullStoppedAt": "2021-12-20T12:13:48.251000-05:00",
"startedAt": "2021-12-20T12:13:49.326000-05:00",
"startedBy": "ecs-svc/988401040018EXAMPLE",
"tags": [],
"taskArn": "arn:aws:ecs:us-east-1:123456789012:task/MyCluster/d789e94343414c25b9f6bd59eEXAMPLE",
"taskDefinitionArn": "arn:aws:ecs:us-east-1:123456789012:task-definition/webserver:2",
"version": 3,
"ephemeralStorage": {
"sizeInGiB": 20
}
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [Definisi Tugas Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [DescribeTasks](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/describe-tasks.html)di *Referensi AWS CLI Perintah*.
### `execute-command`
Contoh kode berikut menunjukkan cara menggunakan`execute-command`.
**AWS CLI**
**Untuk menjalankan perintah /bin/sh interaktif**
`execute-command`Contoh berikut menjalankan perintah /bin/sh interaktif terhadap wadah bernama MyContainer untuk tugas dengan id dari. `arn:aws:ecs:us-east-1:123456789012:task/MyCluster/d789e94343414c25b9f6bd59eEXAMPLE`
```
aws ecs execute-command \
--cluster MyCluster \
--task arn:aws:ecs:us-east-1:123456789012:task/MyCluster/d789e94343414c25b9f6bd59eEXAMPLE \
--container MyContainer \
--interactive \
--command "/bin/sh"
```
Perintah ini tidak menghasilkan output.
Untuk informasi selengkapnya, lihat [Menggunakan Amazon ECS Exec untuk men-debug di Panduan Pengembang](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-exec.html) *Amazon ECS*.
+ Untuk detail API, lihat [ExecuteCommand](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/execute-command.html)di *Referensi AWS CLI Perintah*.
### `get-task-protection`
Contoh kode berikut menunjukkan cara menggunakan`get-task-protection`.
**AWS CLI**
**Mengambil status perlindungan tugas dalam layanan ECS**
Berikut ini `get-task-protection` memberikan status perlindungan tugas ECS yang dimiliki oleh layanan Amazon ECS.
```
aws ecs get-task-protection \
--cluster ECS-project-update-cluster \
--tasks c43ed3b1331041f289316f958adb6a24
```
Output:
```
{
"protectedTasks": [
{
"taskArn": "arn:aws:ecs:us-west-2:123456789012:task/c43ed3b1331041f289316f958adb6a24",
"protectionEnabled": false
}
],
"failures": []
}
```
Untuk pembentukan selengkapnya tentang perlindungan tugas, lihat [Melindungi tugas Amazon ECS agar tidak dihentikan oleh peristiwa penskalaan dalam Panduan Pengembang](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-scale-in-protection.html) *Amazon* ECS.
+ Untuk detail API, lihat [GetTaskProtection](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/get-task-protection.html)di *Referensi AWS CLI Perintah*.
### `list-account-settings`
Contoh kode berikut menunjukkan cara menggunakan`list-account-settings`.
**AWS CLI**
**Contoh 1: Untuk melihat pengaturan akun untuk akun**
`list-account-settings`Contoh berikut menampilkan pengaturan akun yang efektif untuk akun.
```
aws ecs list-account-settings --effective-settings
```
Output:
```
{
"settings": [
{
"name": "containerInstanceLongArnFormat",
"value": "enabled",
"principalArn": "arn:aws:iam::123456789012:root"
},
{
"name": "serviceLongArnFormat",
"value": "enabled",
"principalArn": "arn:aws:iam::123456789012:root"
},
{
"name": "taskLongArnFormat",
"value": "enabled",
"principalArn": "arn:aws:iam::123456789012:root"
}
]
}
```
**Contoh 2: Untuk melihat pengaturan akun untuk pengguna IAM tertentu atau peran IAM**
`list-account-settings`Contoh berikut menampilkan pengaturan akun untuk pengguna IAM tertentu atau peran IAM.
```
aws ecs list-account-settings --principal-arn arn:aws:iam::123456789012:user/MyUser
```
Output:
```
{
"settings": [
{
"name": "serviceLongArnFormat",
"value": "enabled",
"principalArn": "arn:aws:iam::123456789012:user/MyUser"
}
]
}
```
Untuk informasi selengkapnya, lihat [Nama Sumber Daya Amazon (ARNs) dan IDs](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-resource-ids.html) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [ListAccountSettings](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-account-settings.html)di *Referensi AWS CLI Perintah*.
### `list-attributes`
Contoh kode berikut menunjukkan cara menggunakan`list-attributes`.
**AWS CLI**
**Untuk membuat daftar instance kontainer yang berisi atribut tertentu**
Contoh berikut mencantumkan atribut untuk instance kontainer yang memiliki `stack=production` atribut di cluster default.
```
aws ecs list-attributes \
--target-type container-instance \
--attribute-name stack \
--attribute-value production \
--cluster default
```
Output:
```
{
"attributes": [
{
"name": "stack",
"targetId": "arn:aws:ecs:us-west-2:130757420319:container-instance/1c3be8ed-df30-47b4-8f1e-6e68ebd01f34",
"value": "production"
}
]
}
```
Untuk informasi selengkapnya, lihat [Konfigurasi Agen Kontainer Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [ListAttributes](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-attributes.html)di *Referensi AWS CLI Perintah*.
### `list-clusters`
Contoh kode berikut menunjukkan cara menggunakan`list-clusters`.
**AWS CLI**
**Untuk membuat daftar cluster yang tersedia**
`list-clusters`Contoh berikut mencantumkan semua cluster yang tersedia.
```
aws ecs list-clusters
```
Output:
```
{
"clusterArns": [
"arn:aws:ecs:us-west-2:123456789012:cluster/MyECSCluster1",
"arn:aws:ecs:us-west-2:123456789012:cluster/AnotherECSCluster"
]
}
```
Untuk informasi selengkapnya, lihat [Cluster Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_clusters.html) di Panduan Pengembang *Amazon ECS.*
+ Untuk detail API, lihat [ListClusters](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-clusters.html)di *Referensi AWS CLI Perintah*.
### `list-container-instances`
Contoh kode berikut menunjukkan cara menggunakan`list-container-instances`.
**AWS CLI**
**Untuk membuat daftar instance kontainer dalam sebuah cluster**
`list-container-instances`Contoh berikut mencantumkan semua instance kontainer yang tersedia dalam sebuah cluster.
```
aws ecs list-container-instances --cluster MyCluster
```
Output:
```
{
"containerInstanceArns": [
"arn:aws:ecs:us-west-2:123456789012:container-instance/MyCluster/a1b2c3d4-5678-90ab-cdef-11111EXAMPLE",
"arn:aws:ecs:us-west-2:123456789012:container-instance/MyCluster/a1b2c3d4-5678-90ab-cdef-22222EXAMPLE"
]
}
```
Untuk informasi selengkapnya, lihat [Instans Kontainer Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_instances.html) di Panduan Pengembang *Amazon ECS.*
+ Untuk detail API, lihat [ListContainerInstances](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-container-instances.html)di *Referensi AWS CLI Perintah*.
### `list-service-deployments`
Contoh kode berikut menunjukkan cara menggunakan`list-service-deployments`.
**AWS CLI**
**Untuk membuat daftar penyebaran layanan**
`list-service-deployments`Contoh berikut mengambil penerapan layanan untuk layanan bernama. `example-service`
```
aws ecs list-service-deployments \
--service arn:aws:ecs:us-east-1:123456789012:service/example-cluster/example-service
```
Output:
```
{
"serviceDeployments": [
{
"serviceDeploymentArn": "arn:aws:ecs:us-east-1:123456789012:service-deployment/example-cluster/example-service/ejGvqq2ilnbKT9qj0vLJe",
"serviceArn": "arn:aws:ecs:us-east-1:123456789012:service/example-cluster/example-service",
"clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/example-cluster",
"startedAt": "2024-10-31T08:03:32.510000-04:00",
"createdAt": "2024-10-31T08:03:30.917000-04:00",
"finishedAt": "2024-10-31T08:05:04.527000-04:00",
"targetServiceRevisionArn": "arn:aws:ecs:us-east-1:123456789012:service-revision/example-cluster/example-service/1485800978477494678",
"status": "SUCCESSFUL"
}
]
}
```
Untuk informasi selengkapnya, lihat [Melihat riwayat layanan menggunakan penerapan layanan Amazon ECS di Panduan Pengembang](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-deployment.html) *Amazon ECS*.
+ Untuk detail API, lihat [ListServiceDeployments](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-service-deployments.html)di *Referensi AWS CLI Perintah*.
### `list-services-by-namespace`
Contoh kode berikut menunjukkan cara menggunakan`list-services-by-namespace`.
**AWS CLI**
**Untuk membuat daftar layanan di namespace**
`list-services-by-namespace`Contoh berikut mencantumkan semua layanan yang dikonfigurasi untuk namespace yang ditentukan di Wilayah default Anda.
```
aws ecs list-services-by-namespace \
--namespace service-connect
```
Output:
```
{
"serviceArns": [
"arn:aws:ecs:us-west-2:123456789012:service/MyCluster/MyService",
"arn:aws:ecs:us-west-2:123456789012:service/tutorial/service-connect-nginx-service"
]
}
```
Untuk informasi selengkapnya, lihat [Service Connect](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [ListServicesByNamespace](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-services-by-namespace.html)di *Referensi AWS CLI Perintah*.
### `list-services`
Contoh kode berikut menunjukkan cara menggunakan`list-services`.
**AWS CLI**
**Untuk membuat daftar layanan dalam klaster**
`list-services`Contoh berikut menunjukkan cara membuat daftar layanan yang berjalan di cluster.
```
aws ecs list-services --cluster MyCluster
```
Output:
```
{
"serviceArns": [
"arn:aws:ecs:us-west-2:123456789012:service/MyCluster/MyService"
]
}
```
Untuk informasi selengkapnya, lihat [Layanan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [ListServices](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-services.html)di *Referensi AWS CLI Perintah*.
### `list-tags-for-resource`
Contoh kode berikut menunjukkan cara menggunakan`list-tags-for-resource`.
**AWS CLI**
**Untuk membuat daftar tag untuk sumber daya**
`list-tags-for-resource`Contoh berikut mencantumkan tag untuk cluster tertentu.
```
aws ecs list-tags-for-resource \
--resource-arn arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster
```
Output:
```
{
"tags": [
{
"key": "key1",
"value": "value1"
},
{
"key": "key2",
"value": "value2"
},
{
"key": "key3",
"value": "value3"
}
]
}
```
+ Untuk detail API, lihat [ListTagsForResource](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-tags-for-resource.html)di *Referensi AWS CLI Perintah*.
### `list-task-definition-families`
Contoh kode berikut menunjukkan cara menggunakan`list-task-definition-families`.
**AWS CLI**
**Contoh 1: Untuk membuat daftar keluarga definisi tugas terdaftar**
`list-task-definition-families`Contoh berikut mencantumkan semua keluarga definisi tugas terdaftar.
```
aws ecs list-task-definition-families
```
Output:
```
{
"families": [
"node-js-app",
"web-timer",
"hpcc",
"hpcc-c4-8xlarge"
]
}
```
**Contoh 2: Untuk memfilter keluarga definisi tugas terdaftar**
`list-task-definition-families`Contoh berikut mencantumkan revisi definisi tugas yang dimulai dengan “hpcc”.
```
aws ecs list-task-definition-families --family-prefix hpcc
```
Output:
```
{
"families": [
"hpcc",
"hpcc-c4-8xlarge"
]
}
```
Untuk informasi selengkapnya, lihat [Parameter Definisi Tugas](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#family) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [ListTaskDefinitionFamilies](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-task-definition-families.html)di *Referensi AWS CLI Perintah*.
### `list-task-definitions`
Contoh kode berikut menunjukkan cara menggunakan`list-task-definitions`.
**AWS CLI**
**Contoh 1: Untuk mencantumkan definisi tugas yang terdaftar**
`list-task-definitions`Contoh berikut mencantumkan semua definisi tugas terdaftar.
```
aws ecs list-task-definitions
```
Output:
```
{
"taskDefinitionArns": [
"arn:aws:ecs:us-west-2:123456789012:task-definition/sleep300:2",
"arn:aws:ecs:us-west-2:123456789012:task-definition/sleep360:1",
"arn:aws:ecs:us-west-2:123456789012:task-definition/wordpress:3",
"arn:aws:ecs:us-west-2:123456789012:task-definition/wordpress:4",
"arn:aws:ecs:us-west-2:123456789012:task-definition/wordpress:5",
"arn:aws:ecs:us-west-2:123456789012:task-definition/wordpress:6"
]
}
```
**Contoh 2: Untuk mencantumkan definisi tugas terdaftar dalam keluarga**
list-task-definitionsContoh berikut mencantumkan revisi definisi tugas dari keluarga tertentu.
```
aws ecs list-task-definitions --family-prefix wordpress
```
Output:
```
{
"taskDefinitionArns": [
"arn:aws:ecs:us-west-2:123456789012:task-definition/wordpress:3",
"arn:aws:ecs:us-west-2:123456789012:task-definition/wordpress:4",
"arn:aws:ecs:us-west-2:123456789012:task-definition/wordpress:5",
"arn:aws:ecs:us-west-2:123456789012:task-definition/wordpress:6"
]
}
```
Untuk informasi selengkapnya, lihat [Definisi Tugas Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [ListTaskDefinitions](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-task-definitions.html)di *Referensi AWS CLI Perintah*.
### `list-tasks`
Contoh kode berikut menunjukkan cara menggunakan`list-tasks`.
**AWS CLI**
**Contoh 1: Untuk membuat daftar tugas dalam sebuah cluster**
`list-tasks`Contoh berikut mencantumkan semua tugas dalam sebuah cluster.
```
aws ecs list-tasks --cluster default
```
Output:
```
{
"taskArns": [
"arn:aws:ecs:us-west-2:123456789012:task/a1b2c3d4-5678-90ab-cdef-11111EXAMPLE",
"arn:aws:ecs:us-west-2:123456789012:task/a1b2c3d4-5678-90ab-cdef-22222EXAMPLE"
]
}
```
**Contoh 2: Untuk membuat daftar tugas pada instance kontainer tertentu**
`list-tasks`Contoh berikut mencantumkan tugas-tugas pada instance container, menggunakan container instance UUID sebagai filter.
```
aws ecs list-tasks --cluster default --container-instance a1b2c3d4-5678-90ab-cdef-33333EXAMPLE
```
Output:
```
{
"taskArns": [
"arn:aws:ecs:us-west-2:123456789012:task/a1b2c3d4-5678-90ab-cdef-44444EXAMPLE"
]
}
```
Untuk informasi selengkapnya, lihat [Definisi Tugas Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [ListTasks](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/list-tasks.html)di *Referensi AWS CLI Perintah*.
### `put-account-setting-default`
Contoh kode berikut menunjukkan cara menggunakan`put-account-setting-default`.
**AWS CLI**
**Untuk mengubah pengaturan akun default**
`put-account-setting-default`Contoh berikut memodifikasi pengaturan akun default untuk semua pengguna IAM atau peran di akun Anda. Perubahan ini berlaku untuk seluruh AWS akun kecuali pengguna atau peran IAM secara eksplisit mengesampingkan pengaturan ini untuk diri mereka sendiri.
```
aws ecs put-account-setting-default --name serviceLongArnFormat --value enabled
```
Output:
```
{
"setting": {
"name": "serviceLongArnFormat",
"value": "enabled",
"principalArn": "arn:aws:iam::123456789012:root"
}
}
```
Untuk informasi selengkapnya, lihat [Nama Sumber Daya Amazon (ARNs) dan IDs](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-resource-ids.html) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [PutAccountSettingDefault](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/put-account-setting-default.html)di *Referensi AWS CLI Perintah*.
### `put-account-setting`
Contoh kode berikut menunjukkan cara menggunakan`put-account-setting`.
**AWS CLI**
**Untuk mengubah pengaturan akun untuk akun pengguna IAM Anda**
`put-account-setting`Contoh berikut menetapkan pengaturan `containerInsights` akun untuk `enhanced` untuk akun pengguna IAM Anda. Ini mengaktifkan Wawasan Kontainer dengan observabilitas yang ditingkatkan.
```
aws ecs put-account-setting \
--name containerInsights \
--value enhanced
```
Output:
```
{
"setting": {
"name": "containerInsights",
"value": "enhanced",
"principalArn": "arn:aws:iam::123456789012:user/johndoe",
"type": "user"
}
}
```
Untuk informasi selengkapnya, lihat [Memodifikasi Pengaturan Akun](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-modifying-longer-id-settings.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [PutAccountSetting](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/put-account-setting.html)di *Referensi AWS CLI Perintah*.
### `put-account-settings`
Contoh kode berikut menunjukkan cara menggunakan`put-account-settings`.
**AWS CLI**
**Untuk mengubah pengaturan akun untuk pengguna IAM atau peran IAM**
`put-account-setting`Contoh berikut memodifikasi pengaturan akun untuk pengguna IAM tertentu atau peran IAM.
```
aws ecs put-account-setting \
--name serviceLongArnFormat \
--value enabled \
--principal-arn arn:aws:iam::123456789012:user/MyUser
```
Output:
```
{
"setting": {
"name": "serviceLongArnFormat",
"value": "enabled",
"principalArn": "arn:aws:iam::123456789012:user/MyUser"
}
}
```
+ Untuk detail API, lihat [PutAccountSettings](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/put-account-settings.html)di *Referensi AWS CLI Perintah*.
### `put-attributes`
Contoh kode berikut menunjukkan cara menggunakan`put-attributes`.
**AWS CLI**
**Untuk membuat atribut dan mengaitkannya dengan sumber daya Amazon ECS**
Berikut ini `put-attributes` menerapkan atribut dengan nama stack dan nilai produksi untuk instance container.
```
aws ecs put-attributes \
--attributes name=stack,value=production,targetId=arn:aws:ecs:us-west-2:130757420319:container-instance/1c3be8ed-df30-47b4-8f1e-6e68ebd01f34
```
Output:
```
{
"attributes": [
{
"name": "stack",
"targetId": "arn:aws:ecs:us-west-2:130757420319:container-instance/1c3be8ed-df30-47b4-8f1e-6e68ebd01f34",
"value": "production"
}
]
}
```
+ Untuk detail API, lihat [PutAttributes](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/put-attributes.html)di *Referensi AWS CLI Perintah*.
### `put-cluster-capacity-providers`
Contoh kode berikut menunjukkan cara menggunakan`put-cluster-capacity-providers`.
**AWS CLI**
**Contoh 1: Untuk menambahkan penyedia kapasitas yang ada ke cluster**
`put-cluster-capacity-providers`Contoh berikut menambahkan penyedia kapasitas yang ada ke cluster. `create-capacity-provider`Perintah ini digunakan untuk membuat penyedia kapasitas. `describe-clusters`Perintah ini digunakan untuk menggambarkan penyedia kapasitas saat ini dan strategi penyedia kapasitas default yang terkait dengan cluster. Saat menambahkan penyedia kapasitas baru ke klaster, Anda harus menentukan semua penyedia kapasitas yang ada selain penyedia kapasitas baru yang ingin Anda kaitkan dengan cluster. Anda juga harus menentukan strategi penyedia kapasitas default untuk dikaitkan dengan cluster. Dalam contoh ini, `MyCluster` cluster memiliki penyedia `MyCapacityProvider1` kapasitas yang terkait dengannya dan Anda ingin menambahkan penyedia `MyCapacityProvider2` kapasitas dan memasukkannya ke dalam strategi penyedia kapasitas default sehingga tugas tersebar merata di kedua penyedia kapasitas.
```
aws ecs put-cluster-capacity-providers \
--cluster MyCluster \
--capacity-providers MyCapacityProvider1 MyCapacityProvider2 \
--default-capacity-provider-strategy capacityProvider=MyCapacityProvider1,weight=1 capacityProvider=MyCapacityProvider2,weight=1
```
Output:
```
{
"cluster": {
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster",
"clusterName": "MyCluster",
"status": "ACTIVE",
"registeredContainerInstancesCount": 0,
"runningTasksCount": 0,
"pendingTasksCount": 0,
"activeServicesCount": 0,
"statistics": [],
"tags": [],
"settings": [
{
"name": "containerInsights",
"value": "enabled"
}
],
"capacityProviders": [
"MyCapacityProvider1",
"MyCapacityProvider2"
],
"defaultCapacityProviderStrategy": [
{
"capacityProvider": "MyCapacityProvider1",
"weight": 1,
"base": 0
},
{
"capacityProvider": "MyCapacityProvider2",
"weight": 1,
"base": 0
}
],
"attachments": [
{
"id": "0fb0c8f4-6edd-4de1-9b09-17e470ee1918",
"type": "as_policy",
"status": "ACTIVE",
"details": [
{
"name": "capacityProviderName",
"value": "MyCapacityProvider1"
},
{
"name": "scalingPolicyName",
"value": "ECSManagedAutoScalingPolicy-a1b2c3d4-5678-90ab-cdef-EXAMPLE11111"
}
]
},
{
"id": "ae592060-2382-4663-9476-b015c685593c",
"type": "as_policy",
"status": "ACTIVE",
"details": [
{
"name": "capacityProviderName",
"value": "MyCapacityProvider2"
},
{
"name": "scalingPolicyName",
"value": "ECSManagedAutoScalingPolicy-a1b2c3d4-5678-90ab-cdef-EXAMPLE22222"
}
]
}
],
"attachmentsStatus": "UPDATE_IN_PROGRESS"
}
}
```
Untuk informasi selengkapnya, lihat [Penyedia kapasitas klaster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html) di *Panduan Pengembang Amazon ECS*.
**Contoh 2: Untuk menghapus penyedia kapasitas dari cluster**
`put-cluster-capacity-providers`Contoh berikut menghapus penyedia kapasitas dari cluster. `describe-clusters`Perintah ini digunakan untuk menggambarkan penyedia kapasitas saat ini yang terkait dengan cluster. Saat menghapus penyedia kapasitas dari klaster, Anda harus menentukan penyedia kapasitas yang ingin tetap terkait dengan klaster serta strategi penyedia kapasitas default untuk dikaitkan dengan cluster. Dalam contoh ini, cluster memiliki `MyCapacityProvider1` dan penyedia `MyCapacityProvider2` kapasitas yang terkait dengannya dan Anda ingin menghapus penyedia `MyCapacityProvider2` kapasitas, sehingga Anda hanya menentukan `MyCapacityProvider1` dalam perintah bersama dengan strategi penyedia kapasitas default yang diperbarui.
```
aws ecs put-cluster-capacity-providers \
--cluster MyCluster \
--capacity-providers MyCapacityProvider1 \
--default-capacity-provider-strategy capacityProvider=MyCapacityProvider1,weight=1,base=0
```
Output:
```
{
"cluster": {
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster",
"clusterName": "MyCluster",
"status": "ACTIVE",
"registeredContainerInstancesCount": 0,
"runningTasksCount": 0,
"pendingTasksCount": 0,
"activeServicesCount": 0,
"statistics": [],
"tags": [],
"settings": [
{
"name": "containerInsights",
"value": "enabled"
}
],
"capacityProviders": [
"MyCapacityProvider1"
],
"defaultCapacityProviderStrategy": [
"capacityProvider": "MyCapacityProvider1",
"weight": 1,
"base": 0
],
"attachments": [
{
"id": "0fb0c8f4-6edd-4de1-9b09-17e470ee1918",
"type": "as_policy",
"status": "ACTIVE",
"details": [
{
"name": "capacityProviderName",
"value": "MyCapacityProvider1"
},
{
"name": "scalingPolicyName",
"value": "ECSManagedAutoScalingPolicy-a1b2c3d4-5678-90ab-cdef-EXAMPLE11111"
}
]
},
{
"id": "ae592060-2382-4663-9476-b015c685593c",
"type": "as_policy",
"status": "DELETING",
"details": [
{
"name": "capacityProviderName",
"value": "MyCapacityProvider2"
},
{
"name": "scalingPolicyName",
"value": "ECSManagedAutoScalingPolicy-a1b2c3d4-5678-90ab-cdef-EXAMPLE22222"
}
]
}
],
"attachmentsStatus": "UPDATE_IN_PROGRESS"
}
}
```
Untuk informasi selengkapnya, lihat [Penyedia kapasitas klaster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html) di *Panduan Pengembang Amazon ECS*.
**Contoh 3: Untuk menghapus semua penyedia kapasitas dari cluster**
`put-cluster-capacity-providers`Contoh berikut menghapus semua penyedia kapasitas yang ada dari cluster.
```
aws ecs put-cluster-capacity-providers \
--cluster MyCluster \
--capacity-providers [] \
--default-capacity-provider-strategy []
```
Output:
```
{
"cluster": {
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster",
"clusterName": "MyCluster",
"status": "ACTIVE",
"registeredContainerInstancesCount": 0,
"runningTasksCount": 0,
"pendingTasksCount": 0,
"activeServicesCount": 0,
"statistics": [],
"tags": [],
"settings": [
{
"name": "containerInsights",
"value": "enabled"
}
],
"capacityProviders": [],
"defaultCapacityProviderStrategy": [],
"attachments": [
{
"id": "0fb0c8f4-6edd-4de1-9b09-17e470ee1918",
"type": "as_policy",
"status": "DELETING",
"details": [
{
"name": "capacityProviderName",
"value": "MyCapacityProvider1"
},
{
"name": "scalingPolicyName",
"value": "ECSManagedAutoScalingPolicy-a1b2c3d4-5678-90ab-cdef-EXAMPLE11111"
}
]
},
{
"id": "ae592060-2382-4663-9476-b015c685593c",
"type": "as_policy",
"status": "DELETING",
"details": [
{
"name": "capacityProviderName",
"value": "MyCapacityProvider2"
},
{
"name": "scalingPolicyName",
"value": "ECSManagedAutoScalingPolicy-a1b2c3d4-5678-90ab-cdef-EXAMPLE22222"
}
]
}
],
"attachmentsStatus": "UPDATE_IN_PROGRESS"
}
}
```
Untuk informasi selengkapnya, lihat [Penyedia kapasitas klaster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [PutClusterCapacityProviders](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/put-cluster-capacity-providers.html)di *Referensi AWS CLI Perintah*.
### `register-task-definition`
Contoh kode berikut menunjukkan cara menggunakan`register-task-definition`.
**AWS CLI**
**Contoh 1: Untuk mendaftarkan definisi tugas dengan file JSON**
`register-task-definition`Contoh berikut mendaftarkan definisi tugas ke keluarga yang ditentukan. Definisi wadah disimpan dalam format JSON di lokasi file yang ditentukan.
```
aws ecs register-task-definition \
--cli-input-json file:///sleep360.json
```
Isi dari `sleep360.json`:
```
{
"containerDefinitions": [
{
"name": "sleep",
"image": "busybox",
"cpu": 10,
"command": [
"sleep",
"360"
],
"memory": 10,
"essential": true
}
],
"family": "sleep360"
}
```
Output:
```
{
"taskDefinition": {
"status": "ACTIVE",
"family": "sleep360",
"placementConstraints": [],
"compatibilities": [
"EXTERNAL",
"EC2"
],
"volumes": [],
"taskDefinitionArn": "arn:aws:ecs:us-east-1:123456789012:task-definition/sleep360:1",
"containerDefinitions": [
{
"environment": [],
"name": "sleep",
"mountPoints": [],
"image": "busybox",
"cpu": 10,
"portMappings": [],
"command": [
"sleep",
"360"
],
"memory": 10,
"essential": true,
"volumesFrom": []
}
],
"revision": 1
}
}
```
Untuk informasi selengkapnya, lihat [Contoh definisi tugas](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/example_task_definitions.html) di *Panduan Pengembang Amazon ECS*.
**Contoh 2: Untuk mendaftarkan definisi tugas dengan parameter string JSON**
`register-task-definition`Contoh berikut mendaftarkan definisi tugas menggunakan definisi kontainer yang disediakan sebagai parameter string JSON dengan tanda kutip ganda yang lolos.
```
aws ecs register-task-definition \
--family sleep360 \
--container-definitions "[{\"name\":\"sleep\",\"image\":\"busybox\",\"cpu\":10,\"command\":[\"sleep\",\"360\"],\"memory\":10,\"essential\":true}]"
```
Outputnya identik dengan contoh sebelumnya.
Untuk informasi selengkapnya, lihat [Membuat Definisi Tugas](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-task-definition.html) di *Panduan Pengembang Amazon ECS*.
+ Untuk detail API, lihat [RegisterTaskDefinition](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/register-task-definition.html)di *Referensi AWS CLI Perintah*.
### `run-task`
Contoh kode berikut menunjukkan cara menggunakan`run-task`.
**AWS CLI**
**Contoh 1: Untuk menjalankan tugas di klaster default Anda**
`run-task`Contoh berikut menjalankan tugas pada cluster default dan menggunakan token klien.
```
aws ecs run-task \
--cluster default \
--task-definition sleep360:1 \
--client-token 550e8400-e29b-41d4-a716-446655440000
```
Output:
```
{
"tasks": [
{
"attachments": [],
"attributes": [
{
"name": "ecs.cpu-architecture",
"value": "x86_64"
}
],
"availabilityZone": "us-east-1b",
"capacityProviderName": "example-capacity-provider",
"clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/default",
"containerInstanceArn": "arn:aws:ecs:us-east-1:123456789012:container-instance/default/bc4d2ec611d04bb7bb97e83ceEXAMPLE",
"containers": [
{
"containerArn": "arn:aws:ecs:us-east-1:123456789012:container/default/d6f51cc5bbc94a47969c92035e9f66f8/75853d2d-711e-458a-8362-0f0aEXAMPLE",
"taskArn": "arn:aws:ecs:us-east-1:123456789012:task/default/d6f51cc5bbc94a47969c9203EXAMPLE",
"name": "sleep",
"image": "busybox",
"lastStatus": "PENDING",
"networkInterfaces": [],
"cpu": "10",
"memory": "10"
}
],
"cpu": "10",
"createdAt": "2023-11-21T16:59:34.403000-05:00",
"desiredStatus": "RUNNING",
"enableExecuteCommand": false,
"group": "family:sleep360",
"lastStatus": "PENDING",
"launchType": "EC2",
"memory": "10",
"overrides": {
"containerOverrides": [
{
"name": "sleep"
}
],
"inferenceAcceleratorOverrides": []
},
"tags": [],
"taskArn": "arn:aws:ecs:us-east-1:123456789012:task/default/d6f51cc5bbc94a47969c9203EXAMPLE",
"taskDefinitionArn": "arn:aws:ecs:us-east-1:123456789012:task-definition/sleep360:1",
"version": 1
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [Menjalankan aplikasi sebagai tugas mandiri](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/standalone-task-create.html) di Panduan *Pengembang Amazon ECS*.
**Contoh 2: Untuk mengonfigurasi volume Amazon EBS untuk tugas mandiri**
`run-task`Contoh berikut mengonfigurasi volume Amazon EBS terenkripsi untuk tugas Fargate pada klaster default. Anda harus memiliki peran infrastruktur Amazon ECS yang dikonfigurasi dengan kebijakan `AmazonECSInfrastructureRolePolicyForVolumes` terkelola yang dilampirkan. Anda harus menentukan definisi tugas dengan nama volume yang sama seperti pada `run-task` permintaan. Contoh ini menggunakan `--cli-input-json` opsi dan file input JSON yang disebut`ebs.json`.
```
aws ecs run-task \
--cli-input-json file://ebs.json
```
Isi dari `ebs.json`:
```
{
"cluster": "default",
"taskDefinition": "mytaskdef",
"launchType": "FARGATE",
"networkConfiguration":{
"awsvpcConfiguration":{
"assignPublicIp": "ENABLED",
"securityGroups": ["sg-12344321"],
"subnets":["subnet-12344321"]
}
},
"volumeConfigurations": [
{
"name": "myEBSVolume",
"managedEBSVolume": {
"volumeType": "gp3",
"sizeInGiB": 100,
"roleArn":"arn:aws:iam::1111222333:role/ecsInfrastructureRole",
"encrypted": true,
"kmsKeyId": "arn:aws:kms:region:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab"
}
}
]
}
```
Output:
```
{
"tasks": [
{
"attachments": [
{
"id": "ce868693-15ca-4083-91ac-f782f64000c9",
"type": "ElasticNetworkInterface",
"status": "PRECREATED",
"details": [
{
"name": "subnetId",
"value": "subnet-070982705451dad82"
}
]
},
{
"id": "a17ed863-786c-4372-b5b3-b23e53f37877",
"type": "AmazonElasticBlockStorage",
"status": "CREATED",
"details": [
{
"name": "roleArn",
"value": "arn:aws:iam::123456789012:role/ecsInfrastructureRole"
},
{
"name": "volumeName",
"value": "myEBSVolume"
},
{
"name": "deleteOnTermination",
"value": "true"
}
]
}
],
"attributes": [
{
"name": "ecs.cpu-architecture",
"value": "x86_64"
}
],
"availabilityZone": "us-west-2b",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/default",
"containers": [
{
"containerArn": "arn:aws:ecs:us-west-2:123456789012:container/default/7f1fbd3629434cc4b82d72d2f09b67c9/e21962a2-f328-4699-98a3-5161ac2c186a",
"taskArn": "arn:aws:ecs:us-west-2:123456789012:task/default/7f1fbd3629434cc4b82d72d2f09b67c9",
"name": "container-using-ebs",
"image": "amazonlinux:2",
"lastStatus": "PENDING",
"networkInterfaces": [],
"cpu": "0"
}
],
"cpu": "1024",
"createdAt": "2025-01-23T10:29:46.650000-06:00",
"desiredStatus": "RUNNING",
"enableExecuteCommand": false,
"group": "family:mytaskdef",
"lastStatus": "PROVISIONING",
"launchType": "FARGATE",
"memory": "3072",
"overrides": {
"containerOverrides": [
{
"name": "container-using-ebs"
}
],
"inferenceAcceleratorOverrides": []
},
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"tags": [],
"taskArn": "arn:aws:ecs:us-west-2:123456789012:task/default/7f1fbd3629434cc4b82d72d2f09b67c9",
"taskDefinitionArn": "arn:aws:ecs:us-west-2:123456789012:task-definition/mytaskdef:4",
"version": 1,
"ephemeralStorage": {
"sizeInGiB": 20
},
"fargateEphemeralStorage": {
"sizeInGiB": 20
}
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [Menggunakan volume Amazon EBS dengan Amazon ECS di Panduan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html) Pengembang *Amazon ECS.*
+ Untuk detail API, lihat [RunTask](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/run-task.html)di *Referensi AWS CLI Perintah*.
### `start-task`
Contoh kode berikut menunjukkan cara menggunakan`start-task`.
**AWS CLI**
**Contoh 1: Untuk memulai tugas baru**
`start-task`Contoh berikut memulai tugas menggunakan revisi terbaru dari definisi `sleep360` tugas pada instance container yang ditentukan di cluster default.
```
aws ecs start-task \
--task-definition sleep360 \
--container-instances 765936fadbdd46b5991a4bd70c2a43d4
```
Output:
```
{
"tasks": [
{
"taskArn": "arn:aws:ecs:us-west-2:123456789012:task/default/666fdccc2e2d4b6894dd422f4eeee8f8",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/default",
"taskDefinitionArn": "arn:aws:ecs:us-west-2:123456789012:task-definition/sleep360:3",
"containerInstanceArn": "arn:aws:ecs:us-west-2:123456789012:container-instance/default/765936fadbdd46b5991a4bd70c2a43d4",
"overrides": {
"containerOverrides": [
{
"name": "sleep"
}
]
},
"lastStatus": "PENDING",
"desiredStatus": "RUNNING",
"cpu": "128",
"memory": "128",
"containers": [
{
"containerArn": "arn:aws:ecs:us-west-2:123456789012:container/75f11ed4-8a3d-4f26-a33b-ad1db9e02d41",
"taskArn": "arn:aws:ecs:us-west-2:123456789012:task/default/666fdccc2e2d4b6894dd422f4eeee8f8",
"name": "sleep",
"lastStatus": "PENDING",
"networkInterfaces": [],
"cpu": "10",
"memory": "10"
}
],
"version": 1,
"createdAt": 1563421494.186,
"group": "family:sleep360",
"launchType": "EC2",
"attachments": [],
"tags": []
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [Menjadwalkan kontainer Anda di Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html) di Panduan *Pengembang Amazon ECS*.
**Contoh 2: Untuk mengonfigurasi volume Amazon EBS saat tugas dimulai**
`start-task`Contoh berikut mengonfigurasi volume Amazon EBS terenkripsi untuk tugas pada instance container yang ditentukan. Anda harus memiliki peran infrastruktur Amazon ECS yang dikonfigurasi dengan kebijakan `AmazonECSInfrastructureRolePolicyForVolumes` terkelola yang dilampirkan. Anda harus menentukan definisi tugas dengan nama volume yang sama seperti pada `start-task` permintaan. Contoh ini menggunakan `--cli-input-json` opsi dan file input JSON yang disebut `ebs.json` dengan konten berikut.
```
aws ecs start-task \
--cli-input-json file://ebs.json \
--container-instances 765936fadbdd46b5991a4bd70c2a43d4
```
Isi dari `ebs.json`:
```
{
"cluster": "default",
"taskDefinition": "mytaskdef",
"networkConfiguration":{
"awsvpcConfiguration":{
"assignPublicIp": "ENABLED",
"securityGroups": ["sg-12344321"],
"subnets":["subnet-12344321"]
}
},
"volumeConfigurations": [
{
"name": "myEBSVolume",
"managedEBSVolume": {
"volumeType": "gp3",
"sizeInGiB": 100,
"roleArn":"arn:aws:iam::123456789012:role/ecsInfrastructureRole",
"encrypted": true,
"kmsKeyId": "arn:aws:kms:region:123456789012:key/1234abcd-12ab-34cd-56ef-1234567890ab"
}
}
]
}
```
Output:
```
{
"tasks": [
{
"attachments": [
{
"id": "aea29489-9dcd-49f1-8164-4d91566e1113",
"type": "ElasticNetworkInterface",
"status": "PRECREATED",
"details": [
{
"name": "subnetId",
"value": "subnet-12344321"
}
]
},
{
"id": "f29e1222-9a1e-410f-b499-a12a7cd6d42e",
"type": "AmazonElasticBlockStorage",
"status": "CREATED",
"details": [
{
"name": "roleArn",
"value": "arn:aws:iam::123456789012:role/ecsInfrastructureRole"
},
{
"name": "volumeName",
"value": "myEBSVolume"
},
{
"name": "deleteOnTermination",
"value": "true"
}
]
}
],
"attributes": [
{
"name": "ecs.cpu-architecture",
"value": "arm64"
}
],
"availabilityZone": "us-west-2c",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/default",
"containerInstanceArn": "arn:aws:ecs:us-west-2:123456789012:container-instance/default/765936fadbdd46b5991a4bd70c2a43d4",
"containers": [
{
"containerArn": "arn:aws:ecs:us-west-2:123456789012:container/default/bb122ace3ed84add92c00a351a03c69e/a4a9ed10-51c7-4567-9653-50e71b94f867",
"taskArn": "arn:aws:ecs:us-west-2:123456789012:task/default/bb122ace3ed84add92c00a351a03c69e",
"name": "container-using-ebs",
"image": "amazonlinux:2",
"lastStatus": "PENDING",
"networkInterfaces": [],
"cpu": "0"
}
],
"cpu": "1024",
"createdAt": "2025-01-23T14:51:05.191000-06:00",
"desiredStatus": "RUNNING",
"enableExecuteCommand": false,
"group": "family:mytaskdef",
"lastStatus": "PROVISIONING",
"launchType": "EC2",
"memory": "3072",
"overrides": {
"containerOverrides": [
{
"name": "container-using-ebs"
}
],
"inferenceAcceleratorOverrides": []
},
"tags": [],
"taskArn": "arn:aws:ecs:us-west-2:123456789012:task/default/bb122ace3ed84add92c00a351a03c69e",
"taskDefinitionArn": "arn:aws:ecs:us-west-2:123456789012:task-definition/mytaskdef:4",
"version": 1
}
],
"failures": []
}
```
Untuk informasi selengkapnya, lihat [Menggunakan volume Amazon EBS dengan Amazon ECS di Panduan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html) Pengembang *Amazon ECS.*
+ Untuk detail API, lihat [StartTask](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/start-task.html)di *Referensi AWS CLI Perintah*.
### `stop-task`
Contoh kode berikut menunjukkan cara menggunakan`stop-task`.
**AWS CLI**
**Untuk menghentikan tugas**
Berikut ini `stop-task` menghentikan tugas yang ditentukan agar tidak berjalan di cluster default.
```
aws ecs stop-task \
--task 666fdccc2e2d4b6894dd422f4eeee8f8
```
Output:
```
{
"task": {
"taskArn": "arn:aws:ecs:us-west-2:130757420319:task/default/666fdccc2e2d4b6894dd422f4eeee8f8",
"clusterArn": "arn:aws:ecs:us-west-2:130757420319:cluster/default",
"taskDefinitionArn": "arn:aws:ecs:us-west-2:130757420319:task-definition/sleep360:3",
"containerInstanceArn": "arn:aws:ecs:us-west-2:130757420319:container-instance/default/765936fadbdd46b5991a4bd70c2a43d4",
"overrides": {
"containerOverrides": []
},
"lastStatus": "STOPPED",
"desiredStatus": "STOPPED",
"cpu": "128",
"memory": "128",
"containers": [],
"version": 2,
"stoppedReason": "Taskfailedtostart",
"stopCode": "TaskFailedToStart",
"connectivity": "CONNECTED",
"connectivityAt": 1563421494.186,
"pullStartedAt": 1563421494.252,
"pullStoppedAt": 1563421496.252,
"executionStoppedAt": 1563421497,
"createdAt": 1563421494.186,
"stoppingAt": 1563421497.252,
"stoppedAt": 1563421497.252,
"group": "family:sleep360",
"launchType": "EC2",
"attachments": [],
"tags": []
}
}
```
+ Untuk detail API, lihat [StopTask](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/stop-task.html)di *Referensi AWS CLI Perintah*.
### `tag-resource`
Contoh kode berikut menunjukkan cara menggunakan`tag-resource`.
**AWS CLI**
**Untuk menandai sumber daya**
`tag-resource`Contoh berikut menambahkan tag tunggal ke sumber daya yang ditentukan.
```
aws ecs tag-resource \
--resource-arn arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster
--tags key=key1,value=value1
```
Perintah ini tidak menghasilkan output.
**Untuk menambahkan beberapa tag ke sumber daya**
`tag-resource`Contoh berikut menambahkan beberapa tag ke sumber daya yang ditentukan.
```
aws ecs tag-resource \
--resource-arn arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster \
--tags key=key1,value=value1 key=key2,value=value2 key=key3,value=value3
```
Perintah ini tidak menghasilkan output.
+ Untuk detail API, lihat [TagResource](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/tag-resource.html)di *Referensi AWS CLI Perintah*.
### `untag-resource`
Contoh kode berikut menunjukkan cara menggunakan`untag-resource`.
**AWS CLI**
**Untuk menghapus tag dari sumber daya**
`untag-resource`Contoh berikut menghapus tag yang terdaftar dari sumber daya yang ditentukan.
```
aws ecs untag-resource \
--resource-arn arn:aws:ecs:us-west-2:123456789012:cluster/MyCluster \
--tag-keys key1,key2
```
Perintah ini tidak menghasilkan output.
+ Untuk detail API, lihat [UntagResource](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/untag-resource.html)di *Referensi AWS CLI Perintah*.
### `update-cluster-settings`
Contoh kode berikut menunjukkan cara menggunakan`update-cluster-settings`.
**AWS CLI**
**Untuk memodifikasi pengaturan untuk klaster Anda**
`update-cluster-settings`Contoh berikut memungkinkan CloudWatch Container Insights dengan peningkatan observabilitas untuk cluster. `MyCluster`
```
aws ecs update-cluster-settings \
--cluster MyCluster \
--settings name=containerInsights,value=enhanced
```
Output:
```
{
"cluster": {
"clusterArn": "arn:aws:ecs:us-esat-1:123456789012:cluster/MyCluster",
"clusterName": "default",
"status": "ACTIVE",
"registeredContainerInstancesCount": 0,
"runningTasksCount": 0,
"pendingTasksCount": 0,
"activeServicesCount": 0,
"statistics": [],
"tags": [],
"settings": [
{
"name": "containerInsights",
"value": "enhanced"
}
]
}
}
```
Untuk informasi selengkapnya, lihat [Memodifikasi Pengaturan Akun](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-modifying-longer-id-settings.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [UpdateClusterSettings](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/update-cluster-settings.html)di *Referensi AWS CLI Perintah*.
### `update-cluster`
Contoh kode berikut menunjukkan cara menggunakan`update-cluster`.
**AWS CLI**
**Contoh 1: Perbarui cluster ECS yang mengaktifkan ContainerInsights**
Berikut ini `update-cluster` memperbarui nilai containerInsights ke `enabled` dalam klaster yang sudah dibuat. Secara default, ini dinonaktifkan.
```
aws ecs update-cluster \
--cluster ECS-project-update-cluster \
--settings name=containerInsights,value=enabled
```
Output:
```
"cluster": {
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/ECS-project-update-cluster",
"clusterName": "ECS-project-update-cluster",
"status": "ACTIVE",
"registeredContainerInstancesCount": 0,
"runningTasksCount": 0,
"pendingTasksCount": 0,
"activeServicesCount": 0,
"statistics": [],
"tags": [],
"settings": [
{
"name": "containerInsights",
"value": "enabled"
}
],
"capacityProviders": [
"Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-EC2CapacityProvider-3fIpdkLywwFt"
],
"defaultCapacityProviderStrategy": [
{
"capacityProvider": "Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-EC2CapacityProvider-3fIpdkLywwFt",
"weight": 1,
"base": 0
}
],
"attachments": [
{
"id": "069d002b-7634-42e4-b1d4-544f4c8f6380",
"type": "as_policy",
"status": "CREATED",
"details": [
{
"name": "capacityProviderName",
"value": "Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-EC2CapacityProvider-3fIpdkLywwFt"
},
{
"name": "scalingPolicyName",
"value": "ECSManagedAutoScalingPolicy-152363a6-8c65-484c-b721-42c3e070ae93"
}
]
},
{
"id": "08b5b6ca-45e9-4209-a65d-e962a27c490a",
"type": "managed_draining",
"status": "CREATED",
"details": [
{
"name": "capacityProviderName",
"value": "Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-EC2CapacityProvider-3fIpdkLywwFt"
},
{
"name": "autoScalingLifecycleHookName",
"value": "ecs-managed-draining-termination-hook"
}
]
},
{
"id": "45d0b36f-8cff-46b6-9380-1288744802ab",
"type": "sc",
"status": "ATTACHED",
"details": []
}
],
"attachmentsStatus": "UPDATE_COMPLETE",
"serviceConnectDefaults": {
"namespace": "arn:aws:servicediscovery:us-west-2:123456789012:namespace/ns-igwrsylmy3kwvcdx"
}
}
```
**Contoh 2: Perbarui cluster ECS untuk mengatur namespace Service Connect default**
Berikut ini `update-cluster` memperbarui cluster ECS dengan menyetel namespace Service Connect default.
```
aws ecs update-cluster \
--cluster ECS-project-update-cluster \
--service-connect-defaults namespace=test
```
Output:
```
{
"cluster": {
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/ECS-project-update-cluster",
"clusterName": "ECS-project-update-cluster",
"status": "ACTIVE",
"registeredContainerInstancesCount": 0,
"runningTasksCount": 0,
"pendingTasksCount": 0,
"activeServicesCount": 0,
"statistics": [],
"tags": [],
"settings": [
{
"name": "containerInsights",
"value": "enabled"
}
],
"capacityProviders": [
"Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-EC2CapacityProvider-3fIpdkLywwFt"
],
"defaultCapacityProviderStrategy": [
{
"capacityProvider": "Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-EC2CapacityProvider-3fIpdkLywwFt",
"weight": 1,
"base": 0
}
],
"attachments": [
{
"id": "069d002b-7634-42e4-b1d4-544f4c8f6380",
"type": "as_policy",
"status": "CREATED",
"details": [
{
"name": "capacityProviderName",
"value": "Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-EC2CapacityProvider-3fIpdkLywwFt"
},
{
"name": "scalingPolicyName",
"value": "ECSManagedAutoScalingPolicy-152363a6-8c65-484c-b721-42c3e070ae93"
}
]
},
{
"id": "08b5b6ca-45e9-4209-a65d-e962a27c490a",
"type": "managed_draining",
"status": "CREATED",
"details": [
{
"name": "capacityProviderName",
"value": "Infra-ECS-Cluster-ECS-project-update-cluster-d6bb6d5b-EC2CapacityProvider-3fIpdkLywwFt"
},
{
"name": "autoScalingLifecycleHookName",
"value": "ecs-managed-draining-termination-hook"
}
]
},
{
"id": "45d0b36f-8cff-46b6-9380-1288744802ab",
"type": "sc",
"status": "DELETED",
"details": []
},
{
"id": "3e6890c3-609c-4832-91de-d6ca891b3ef1",
"type": "sc",
"status": "ATTACHED",
"details": []
},
{
"id": "961b8ec1-c2f1-4070-8495-e669b7668e90",
"type": "sc",
"status": "DELETED",
"details": []
}
],
"attachmentsStatus": "UPDATE_COMPLETE",
"serviceConnectDefaults": {
"namespace": "arn:aws:servicediscovery:us-west-2:123456789012:namespace/ns-dtjmxqpfi46ht7dr"
}
}
}
```
Untuk informasi selengkapnya tentang Service Connect, lihat [Menggunakan Service Connect untuk menghubungkan layanan Amazon ECS dengan nama pendek](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [UpdateCluster](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/update-cluster.html)di *Referensi AWS CLI Perintah*.
### `update-container-agent`
Contoh kode berikut menunjukkan cara menggunakan`update-container-agent`.
**AWS CLI**
**Untuk memperbarui agen penampung pada instans penampung Amazon ECS**
`update-container-agent`Contoh berikut memperbarui agen kontainer pada instance kontainer tertentu di cluster default.
```
aws ecs update-container-agent --cluster default --container-instance a1b2c3d4-5678-90ab-cdef-11111EXAMPLE
```
Output:
```
{
"containerInstance": {
"status": "ACTIVE",
...
"agentUpdateStatus": "PENDING",
"versionInfo": {
"agentVersion": "1.0.0",
"agentHash": "4023248",
"dockerVersion": "DockerVersion: 1.5.0"
}
}
}
```
Untuk informasi selengkapnya, lihat [Memperbarui Agen Kontainer Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html) di Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [UpdateContainerAgent](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/update-container-agent.html)di *Referensi AWS CLI Perintah*.
### `update-container-instances-state`
Contoh kode berikut menunjukkan cara menggunakan`update-container-instances-state`.
**AWS CLI**
**Untuk memperbarui status instance kontainer**
Berikut ini `update-container-instances-state` memperbarui status instance kontainer tertentu `DRAINING` yang akan menghapusnya dari cluster apakah itu terdaftar.
```
aws ecs update-container-instances-state \
--container-instances 765936fadbdd46b5991a4bd70c2a43d4 \
--status DRAINING
```
Output:
```
{
"containerInstances": [
{
"containerInstanceArn": "arn:aws:ecs:us-west-2:130757420319:container-instance/default/765936fadbdd46b5991a4bd70c2a43d4",
"ec2InstanceId": "i-013d87ffbb4d513bf",
"version": 4390,
"versionInfo": {
"agentVersion": "1.29.0",
"agentHash": "a190a73f",
"dockerVersion": "DockerVersion:18.06.1-ce"
},
"remainingResources": [
{
"name": "CPU",
"type": "INTEGER",
"doubleValue": 0,
"longValue": 0,
"integerValue": 1536
},
{
"name": "MEMORY",
"type": "INTEGER",
"doubleValue": 0,
"longValue": 0,
"integerValue": 2681
},
{
"name": "PORTS",
"type": "STRINGSET",
"doubleValue": 0,
"longValue": 0,
"integerValue": 0,
"stringSetValue": [
"22",
"2376",
"2375",
"51678",
"51679"
]
},
{
"name": "PORTS_UDP",
"type": "STRINGSET",
"doubleValue": 0,
"longValue": 0,
"integerValue": 0,
"stringSetValue": []
}
],
"registeredResources": [
{
"name": "CPU",
"type": "INTEGER",
"doubleValue": 0,
"longValue": 0,
"integerValue": 2048
},
{
"name": "MEMORY",
"type": "INTEGER",
"doubleValue": 0,
"longValue": 0,
"integerValue": 3705
},
{
"name": "PORTS",
"type": "STRINGSET",
"doubleValue": 0,
"longValue": 0,
"integerValue": 0,
"stringSetValue": [
"22",
"2376",
"2375",
"51678",
"51679"
]
},
{
"name": "PORTS_UDP",
"type": "STRINGSET",
"doubleValue": 0,
"longValue": 0,
"integerValue": 0,
"stringSetValue": []
}
],
"status": "DRAINING",
"agentConnected": true,
"runningTasksCount": 2,
"pendingTasksCount": 0,
"attributes": [
{
"name": "ecs.capability.secrets.asm.environment-variables"
},
{
"name": "ecs.capability.branch-cni-plugin-version",
"value": "e0703516-"
},
{
"name": "ecs.ami-id",
"value": "ami-00e0090ac21971297"
},
{
"name": "ecs.capability.secrets.asm.bootstrap.log-driver"
},
{
"name": "com.amazonaws.ecs.capability.logging-driver.none"
},
{
"name": "ecs.capability.ecr-endpoint"
},
{
"name": "ecs.capability.docker-plugin.local"
},
{
"name": "ecs.capability.task-cpu-mem-limit"
},
{
"name": "ecs.capability.secrets.ssm.bootstrap.log-driver"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.30"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.31"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.32"
},
{
"name": "ecs.availability-zone",
"value": "us-west-2c"
},
{
"name": "ecs.capability.aws-appmesh"
},
{
"name": "com.amazonaws.ecs.capability.logging-driver.awslogs"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.24"
},
{
"name": "ecs.capability.task-eni-trunking"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.25"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.26"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.27"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.28"
},
{
"name": "com.amazonaws.ecs.capability.privileged-container"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.29"
},
{
"name": "ecs.cpu-architecture",
"value": "x86_64"
},
{
"name": "com.amazonaws.ecs.capability.ecr-auth"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.20"
},
{
"name": "ecs.os-type",
"value": "linux"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.21"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.22"
},
{
"name": "ecs.capability.task-eia"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.23"
},
{
"name": "ecs.capability.private-registry-authentication.secretsmanager"
},
{
"name": "com.amazonaws.ecs.capability.logging-driver.syslog"
},
{
"name": "com.amazonaws.ecs.capability.logging-driver.json-file"
},
{
"name": "ecs.capability.execution-role-awslogs"
},
{
"name": "ecs.vpc-id",
"value": "vpc-1234"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.17"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.18"
},
{
"name": "com.amazonaws.ecs.capability.docker-remote-api.1.19"
},
{
"name": "ecs.capability.task-eni"
},
{
"name": "ecs.capability.execution-role-ecr-pull"
},
{
"name": "ecs.capability.container-health-check"
},
{
"name": "ecs.subnet-id",
"value": "subnet-1234"
},
{
"name": "ecs.instance-type",
"value": "c5.large"
},
{
"name": "com.amazonaws.ecs.capability.task-iam-role-network-host"
},
{
"name": "ecs.capability.container-ordering"
},
{
"name": "ecs.capability.cni-plugin-version",
"value": "91ccefc8-2019.06.0"
},
{
"name": "ecs.capability.pid-ipc-namespace-sharing"
},
{
"name": "ecs.capability.secrets.ssm.environment-variables"
},
{
"name": "com.amazonaws.ecs.capability.task-iam-role"
}
],
"registeredAt": 1560788724.507,
"attachments": [],
"tags": []
}
],
"failures": []
}
```
+ Untuk detail API, lihat [UpdateContainerInstancesState](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/update-container-instances-state.html)di *Referensi AWS CLI Perintah*.
### `update-service-primary-task-set`
Contoh kode berikut menunjukkan cara menggunakan`update-service-primary-task-set`.
**AWS CLI**
**Untuk memperbarui set tugas utama untuk layanan**
`update-service-primary-task-set`Contoh berikut memperbarui tugas utama yang ditetapkan untuk layanan tertentu.
```
aws ecs update-service-primary-task-set \
--cluster MyCluster \
--service MyService \
--primary-task-set arn:aws:ecs:us-west-2:123456789012:task-set/MyCluster/MyService/ecs-svc/1234567890123456789
```
Output:
```
{
"taskSet": {
"id": "ecs-svc/1234567890123456789",
"taskSetArn": "arn:aws:ecs:us-west-2:123456789012:task-set/MyCluster/MyService/ecs-svc/1234567890123456789",
"status": "PRIMARY",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/sample-fargate:2",
"computedDesiredCount": 1,
"pendingCount": 0,
"runningCount": 0,
"createdAt": 1557128360.711,
"updatedAt": 1557129412.653,
"launchType": "EC2",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344312"
],
"assignPublicIp": "DISABLED"
}
},
"loadBalancers": [],
"serviceRegistries": [],
"scale": {
"value": 50.0,
"unit": "PERCENT"
},
"stabilityStatus": "STABILIZING",
"stabilityStatusAt": 1557129279.914
}
}
```
+ Untuk detail API, lihat [UpdateServicePrimaryTaskSet](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/update-service-primary-task-set.html)di *Referensi AWS CLI Perintah*.
### `update-service`
Contoh kode berikut menunjukkan cara menggunakan`update-service`.
**AWS CLI**
**Contoh 1: Untuk mengubah definisi tugas yang digunakan dalam layanan**
`update-service`Contoh berikut memperbarui `my-http-service` layanan untuk menggunakan definisi `amazon-ecs-sample` tugas.
```
aws ecs update-service \
--cluster test \
--service my-http-service \
--task-definition amazon-ecs-sample
```
Output:
```
{
"service": {
"serviceArn": "arn:aws:ecs:us-west-2:123456789012:service/test/my-http-service",
"serviceName": "my-http-service",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/test",
"loadBalancers": [],
"serviceRegistries": [],
"status": "ACTIVE",
"desiredCount": 2,
"runningCount": 2,
"pendingCount": 0,
"launchType": "FARGATE",
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/amazon-ecs-sample:2",
"deploymentConfiguration": {
"deploymentCircuitBreaker": {
"enable": true,
"rollback": true
},
"maximumPercent": 200,
"minimumHealthyPercent": 100,
"alarms": {
"alarmNames": [],
"rollback": false,
"enable": false
}
},
"deployments": [
{
"id": "ecs-svc/7419115625193919142",
"status": "PRIMARY",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/amazon-ecs-sample:2",
"desiredCount": 0,
"pendingCount": 0,
"runningCount": 0,
"failedTasks": 0,
"createdAt": "2025-02-21T13:26:02.734000-06:00",
"updatedAt": "2025-02-21T13:26:02.734000-06:00",
"launchType": "FARGATE",
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "ENABLED"
}
},
"rolloutState": "IN_PROGRESS",
"rolloutStateReason": "ECS deployment ecs-svc/7419115625193919142 in progress."
},
{
"id": "ecs-svc/1709597507655421668",
"status": "ACTIVE",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/old-amazon-ecs-sample:4",
"desiredCount": 2,
"pendingCount": 0,
"runningCount": 2,
"failedTasks": 0,
"createdAt": "2025-01-24T11:13:07.621000-06:00",
"updatedAt": "2025-02-02T16:11:30.838000-06:00",
"launchType": "FARGATE",
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "ENABLED"
}
},
"rolloutState": "COMPLETED",
"rolloutStateReason": "ECS deployment ecs-svc/1709597507655421668 completed."
}
],
"roleArn": "arn:aws:iam::123456789012:role/aws-service-role/ecs.amazonaws.com/AWSServiceRoleForECS",
"events": [
{
"id": "e40b4d1c-80d9-4834-aaf3-6a268e530e17",
"createdAt": "2025-02-21T10:31:26.037000-06:00",
"message": "(my-http-service) has reached a steady state."
},
{
"id": "6ac069ad-fc8b-4e49-a35d-b5574a964c8e",
"createdAt": "2025-02-21T04:31:22.703000-06:00",
"message": "(my-http-service) has reached a steady state."
},
{
"id": "265f7d37-dfd1-4880-a846-ec486f341919",
"createdAt": "2025-02-20T22:31:22.514000-06:00",
"message": "(my-http-service) has reached a steady state."
}
],
"createdAt": "2024-10-30T17:12:43.218000-05:00",
"placementConstraints": [],
"placementStrategy": [],
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321",
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "ENABLED"
}
},
"healthCheckGracePeriodSeconds": 0,
"schedulingStrategy": "REPLICA",
"deploymentController": {
"type": "ECS"
},
"createdBy": "arn:aws:iam::123456789012:role/AIDACKCEVSQ6C2EXAMPLE",
"enableECSManagedTags": true,
"propagateTags": "NONE",
"enableExecuteCommand": false,
"availabilityZoneRebalancing": "DISABLED"
}
}
```
Untuk informasi selengkapnya, lihat [Memperbarui layanan Amazon ECS menggunakan konsol di](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/update-service-console-v2.html) Panduan *Pengembang Amazon ECS*.
**Contoh 2: Untuk mengubah jumlah tugas dalam suatu layanan**
`update-service`Contoh berikut memperbarui jumlah tugas yang diinginkan dari layanan `my-http-service` dari ke 2.
```
aws ecs update-service \
--cluster MyCluster \
--service my-http-service \
--desired-count 2
```
Output:
```
{
"service": {
"serviceArn": "arn:aws:ecs:us-east-1:123456789012:service/MyCluster/my-http-service",
"serviceName": "my-http-service",
"clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/MyCluster",
"loadBalancers": [],
"serviceRegistries": [],
"status": "ACTIVE",
"desiredCount": 2,
"runningCount": 1,
"pendingCount": 0,
"capacityProviderStrategy": [
{
"capacityProvider": "FARGATE",
"weight": 1,
"base": 0
}
],
"platformVersion": "LATEST",
"platformFamily": "Linux",
"taskDefinition": "arn:aws:ecs:us-east-1:123456789012:task-definition/MyTaskDefinition",
"deploymentConfiguration": {
"deploymentCircuitBreaker": {
"enable": true,
"rollback": true
},
"maximumPercent": 200,
"minimumHealthyPercent": 100,
"alarms": {
"alarmNames": [],
"rollback": false,
"enable": false
}
},
"deployments": [
{
"id": "ecs-svc/1976744184940610707",
"status": "PRIMARY",
"taskkDefinition": "arn:aws:ecs:us-east-1:123456789012:task-definition/MyTaskDefinition",
"desiredCount": 1,
"pendingCount": 0,
"runningCount": 1,
"failedTasks": 0,
"createdAt": "2024-12-03T16:24:25.225000-05:00",
"updatedAt": "2024-12-03T16:25:15.837000-05:00",
"capacityProviderStrategy": [
{
"capacityProvider": "FARGATE",
"weight": 1,
"base": 0
}
],
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-0d0eab1bb38d5ca64",
"subnet-0db5010045995c2d5"
],
"securityGroups": [
"sg-02556bf85a191f59a"
],
"assignPublicIp": "ENABLED"
}
},
"rolloutState": "COMPLETED",
"rolloutStateReason": "ECS deployment ecs-svc/1976744184940610707 completed."
}
],
"roleArn": "arn:aws:iam::123456789012:role/aws-service-role/ecs.amazonaws.com/AWSServiceRoleForECS",
"events": [
{
"id": "f27350b9-4b2a-4e2e-b72e-a4b68380de45",
"createdAt": "2024-12-30T13:24:07.345000-05:00",
"message": "(service my-http-service) has reached a steady state."
},
{
"id": "e764ec63-f53f-45e3-9af2-d99f922d2957",
"createdAt": "2024-12-30T12:32:21.600000-05:00",
"message": "(service my-http-service) has reached a steady state."
},
{
"id": "28444756-c2fa-47f8-bd60-93a8e05f3991",
"createdAt": "2024-12-08T19:26:10.367000-05:00",
"message": "(service my-http-service) has reached a steady state."
}
],
"createdAt": "2024-12-03T16:24:25.225000-05:00",
"placementConstraints": [],
"placementStrategy": [],
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-0d0eab1bb38d5ca64",
"subnet-0db5010045995c2d5"
],
"securityGroups": [
"sg-02556bf85a191f59a"
],
"assignPublicIp": "ENABLED"
}
},
"healthCheckGracePeriodSeconds": 0,
"schedulingStrategy": "REPLICA",
"deploymentController": {
"type": "ECS"
},
"createdBy": "arn:aws:iam::123456789012:role/Admin",
"enableECSManagedTags": true,
"propagateTags": "NONE",
"enableExecuteCommand": false,
"availabilityZoneRebalancing": "ENABLED"
}
}
```
Untuk informasi selengkapnya, lihat [Memperbarui layanan Amazon ECS menggunakan konsol di](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/update-service-console-v2.html) Panduan *Pengembang Amazon ECS*.
**Contoh 3: Untuk mengonfigurasi volume Amazon EBS untuk lampiran pada pembaruan layanan**
`update-service`Contoh berikut memperbarui layanan `my-http-service` untuk menggunakan volume Amazon EBS. Anda harus memiliki peran infrastruktur Amazon ECS yang dikonfigurasi dengan kebijakan `AmazonECSInfrastructureRolePolicyForVolumes` terkelola yang dilampirkan. Anda juga harus menentukan definisi tugas dengan nama volume yang sama seperti pada `update-service` permintaan dan dengan `configuredAtLaunch` set ke`true`. Contoh ini menggunakan `--cli-input-json` opsi dan file input JSON yang disebut`ebs.json`.
```
aws ecs update-service \
--cli-input-json file://ebs.json
```
Isi dari `ebs.json`:
```
{
"cluster": "mycluster",
"taskDefinition": "mytaskdef",
"service": "my-http-service",
"desiredCount": 2,
"volumeConfigurations": [
{
"name": "myEbsVolume",
"managedEBSVolume": {
"roleArn":"arn:aws:iam::123456789012:role/ecsInfrastructureRole",
"volumeType": "gp3",
"sizeInGiB": 100,
"iops": 3000,
"throughput": 125,
"filesystemType": "ext4"
}
}
]
}
```
Output:
```
{
"service": {
"serviceArn": "arn:aws:ecs:us-west-2:123456789012:service/mycluster/my-http-service",
"serviceName": "my-http-service",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/mycluster",
"loadBalancers": [],
"serviceRegistries": [],
"status": "ACTIVE",
"desiredCount": 2,
"runningCount": 2,
"pendingCount": 0,
"launchType": "FARGATE",
"platformVersion": "LATEST",
"platformFamily": "Linux",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/mytaskdef:1",
"deploymentConfiguration": {
"deploymentCircuitBreaker": {
"enable": true,
"rollback": true
},
"maximumPercent": 200,
"minimumHealthyPercent": 100,
"alarms": {
"alarmNames": [],
"rollback": false,
"enable": false
}
},
"deployments": [
{
"id": "ecs-svc/2420458347226626275",
"status": "PRIMARY",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/mytaskdef:1",
"desiredCount": 0,
"pendingCount": 0,
"runningCount": 0,
"failedTasks": 0,
"createdAt": "2025-02-21T15:07:20.519000-06:00",
"updatedAt": "2025-02-21T15:07:20.519000-06:00",
"launchType": "FARGATE",
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321",
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "ENABLED"
}
},
"rolloutState": "IN_PROGRESS",
"rolloutStateReason": "ECS deployment ecs-svc/2420458347226626275 in progress.",
"volumeConfigurations": [
{
"name": "ebs-volume",
"managedEBSVolume": {
"volumeType": "gp3",
"sizeInGiB": 100,
"iops": 3000,
"throughput": 125,
"roleArn": "arn:aws:iam::123456789012:role/ecsInfrastructureRole",
"filesystemType": "ext4"
}
}
]
},
{
"id": "ecs-svc/5191625155316533644",
"status": "ACTIVE",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/mytaskdef:2",
"desiredCount": 2,
"pendingCount": 0,
"runningCount": 2,
"failedTasks": 0,
"createdAt": "2025-02-21T14:54:48.862000-06:00",
"updatedAt": "2025-02-21T14:57:22.502000-06:00",
"launchType": "FARGATE",
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "ENABLED"
}
},
"rolloutState": "COMPLETED",
"rolloutStateReason": "ECS deployment ecs-svc/5191625155316533644 completed."
}
],
"roleArn": "arn:aws:iam::123456789012:role/aws-service-role/ecs.amazonaws.com/AWSServiceRoleForECS",
"events": [
{
"id": "b5823113-c2c5-458e-9649-8c2ed38f23a5",
"createdAt": "2025-02-21T14:57:22.508000-06:00",
"message": "(service my-http-service) has reached a steady state."
},
{
"id": "b05a48e8-da35-4074-80aa-37ceb3167357",
"createdAt": "2025-02-21T14:57:22.507000-06:00",
"message": "(service my-http-service) (deployment ecs-svc/5191625155316533644) deployment completed."
},
{
"id": "a10cd55d-4ba6-4cea-a655-5a5d32ada8a0",
"createdAt": "2025-02-21T14:55:32.833000-06:00",
"message": "(service my-http-service) has started 1 tasks: (task fb9c8df512684aec92f3c57dc3f22361)."
},
],
"createdAt": "2025-02-21T14:54:48.862000-06:00",
"placementConstraints": [],
"placementStrategy": [],
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "ENABLED"
}
},
"healthCheckGracePeriodSeconds": 0,
"schedulingStrategy": "REPLICA",
"deploymentController": {
"type": "ECS"
},
"createdBy": "arn:aws:iam::123456789012:role/AIDACKCEVSQ6C2EXAMPLE",
"enableECSManagedTags": true,
"propagateTags": "NONE",
"enableExecuteCommand": false,
"availabilityZoneRebalancing": "ENABLED"
}
}
```
Untuk informasi selengkapnya, lihat [Menggunakan volume Amazon EBS dengan Amazon ECS di Panduan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html) Pengembang *Amazon ECS.*
**Contoh 4: Untuk memperbarui layanan agar tidak lagi menggunakan volume Amazon EBS**
`update-service`Contoh berikut memperbarui layanan `my-http-service` agar tidak lagi menggunakan volume Amazon EBS. Anda harus menentukan revisi definisi tugas dengan `configuredAtLaunch` set to`false`.
```
aws ecs update-service \
--cluster mycluster \
--task-definition mytaskdef \
--service my-http-service \
--desired-count 2 \
--volume-configurations "[]"
```
Output:
```
{
"service": {
"serviceArn": "arn:aws:ecs:us-west-2:123456789012:service/mycluster/my-http-service",
"serviceName": "my-http-service",
"clusterArn": "arn:aws:ecs:us-west-2:123456789012:cluster/mycluster",
"loadBalancers": [],
"serviceRegistries": [],
"status": "ACTIVE",
"desiredCount": 2,
"runningCount": 2,
"pendingCount": 0,
"launchType": "FARGATE",
"platformVersion": "LATEST",
"platformFamily": "Linux",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/mytaskdef:3",
"deploymentConfiguration": {
"deploymentCircuitBreaker": {
"enable": true,
"rollback": true
},
"maximumPercent": 200,
"minimumHealthyPercent": 100,
"alarms": {
"alarmNames": [],
"rollback": false,
"enable": false
}
},
"deployments": [
{
"id": "ecs-svc/7522791612543716777",
"status": "PRIMARY",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/mytaskdef:3",
"desiredCount": 0,
"pendingCount": 0,
"runningCount": 0,
"failedTasks": 0,
"createdAt": "2025-02-21T15:25:38.598000-06:00",
"updatedAt": "2025-02-21T15:25:38.598000-06:00",
"launchType": "FARGATE",
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "ENABLED"
}
},
"rolloutState": "IN_PROGRESS",
"rolloutStateReason": "ECS deployment ecs-svc/7522791612543716777 in progress."
},
{
"id": "ecs-svc/2420458347226626275",
"status": "ACTIVE",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/myoldtaskdef:1",
"desiredCount": 2,
"pendingCount": 0,
"runningCount": 2,
"failedTasks": 0,
"createdAt": "2025-02-21T15:07:20.519000-06:00",
"updatedAt": "2025-02-21T15:10:59.955000-06:00",
"launchType": "FARGATE",
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "ENABLED"
}
},
"rolloutState": "COMPLETED",
"rolloutStateReason": "ECS deployment ecs-svc/2420458347226626275 completed.",
"volumeConfigurations": [
{
"name": "ebs-volume",
"managedEBSVolume": {
"volumeType": "gp3",
"sizeInGiB": 100,
"iops": 3000,
"throughput": 125,
"roleArn": "arn:aws:iam::123456789012:role/ecsInfrastructureRole",
"filesystemType": "ext4"
}
}
]
}
],
"roleArn": "arn:aws:iam::123456789012:role/aws-service-role/ecs.amazonaws.com/AWSServiceRoleForECS",
"events": [
{
"id": "4f2c3ca1-7800-4048-ba57-bba210ada2ad",
"createdAt": "2025-02-21T15:10:59.959000-06:00",
"message": "(service my-http-service) has reached a steady state."
},
{
"id": "4b36a593-2d40-4ed6-8be8-b9b699eb6198",
"createdAt": "2025-02-21T15:10:59.958000-06:00",
"message": "(service my-http-service) (deployment ecs-svc/2420458347226626275) deployment completed."
},
{
"id": "88380089-14e2-4ef0-8dbb-a33991683371",
"createdAt": "2025-02-21T15:09:39.055000-06:00",
"message": "(service my-http-service) has stopped 1 running tasks: (task fb9c8df512684aec92f3c57dc3f22361)."
},
{
"id": "97d84243-d52f-4255-89bb-9311391c61f6",
"createdAt": "2025-02-21T15:08:57.653000-06:00",
"message": "(service my-http-service) has stopped 1 running tasks: (task 33eff090ad2c40539daa837e6503a9bc)."
},
{
"id": "672ece6c-e2d0-4021-b5da-eefb14001687",
"createdAt": "2025-02-21T15:08:15.631000-06:00",
"message": "(service my-http-service) has started 1 tasks: (task 996c02a66ff24f3190a4a8e0c841740f)."
},
{
"id": "a3cf9bea-9be6-4175-ac28-4c68360986eb",
"createdAt": "2025-02-21T15:07:36.931000-06:00",
"message": "(service my-http-service) has started 1 tasks: (task d5d23c39f89e46cf9a647b9cc6572feb)."
},
{
"id": "b5823113-c2c5-458e-9649-8c2ed38f23a5",
"createdAt": "2025-02-21T14:57:22.508000-06:00",
"message": "(service my-http-service) has reached a steady state."
},
{
"id": "b05a48e8-da35-4074-80aa-37ceb3167357",
"createdAt": "2025-02-21T14:57:22.507000-06:00",
"message": "(service my-http-service) (deployment ecs-svc/5191625155316533644) deployment completed."
},
{
"id": "a10cd55d-4ba6-4cea-a655-5a5d32ada8a0",
"createdAt": "2025-02-21T14:55:32.833000-06:00",
"message": "(service my-http-service) has started 1 tasks: (task fb9c8df512684aec92f3c57dc3f22361)."
},
{
"id": "42da91fa-e26d-42ef-88c3-bb5965c56b2f",
"createdAt": "2025-02-21T14:55:02.703000-06:00",
"message": "(service my-http-service) has started 1 tasks: (task 33eff090ad2c40539daa837e6503a9bc)."
}
],
"createdAt": "2025-02-21T14:54:48.862000-06:00",
"placementConstraints": [],
"placementStrategy": [],
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "ENABLED"
}
},
"healthCheckGracePeriodSeconds": 0,
"schedulingStrategy": "REPLICA",
"deploymentController": {
"type": "ECS"
},
"createdBy": "arn:aws:iam::123456789012:role/AIDACKCEVSQ6C2EXAMPLE",
"enableECSManagedTags": true,
"propagateTags": "NONE",
"enableExecuteCommand": false,
"availabilityZoneRebalancing": "ENABLED"
}
}
```
Untuk informasi selengkapnya, lihat [Menggunakan volume Amazon EBS dengan Amazon ECS di Panduan](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html) Pengembang *Amazon ECS.*
**Contoh 5: Untuk mengaktifkan penyeimbangan kembali Availability Zone untuk suatu layanan**
`update-service`Contoh berikut mengaktifkan penyeimbangan kembali Availability Zone untuk layanan. `my-http-service`
```
aws ecs update-service \
--cluster MyCluster \
--service my-http-service \
--availability-zone-rebalancing ENABLED
```
Output:
```
{
"service": {
"serviceArn": "arn:aws:ecs:us-east-1:123456789012:service/MyCluster/my-http-service",
"serviceName": "my-http-service",
"clusterArn": "arn:aws:ecs:us-east-1:123456789012:cluster/MyCluster",
"loadBalancers": [],
"serviceRegistries": [],
"status": "ACTIVE",
"desiredCount": 2,
"runningCount": 1,
"pendingCount": 0,
"capacityProviderStrategy": [
{
"capacityProvider": "FARGATE",
"weight": 1,
"base": 0
}
],
"platformVersion": "LATEST",
"platformFamily": "Linux",
"taskDefinition": "arn:aws:ecs:us-east-1:123456789012:task-definition/MyTaskDefinition",
"deploymentConfiguration": {
"deploymentCircuitBreaker": {
"enable": true,
"rollback": true
},
"maximumPercent": 200,
"minimumHealthyPercent": 100,
"alarms": {
"alarmNames": [],
"rollback": false,
"enable": false
}
},
"deployments": [
{
"id": "ecs-svc/1976744184940610707",
"status": "PRIMARY",
"taskkDefinition": "arn:aws:ecs:us-east-1:123456789012:task-definition/MyTaskDefinition",
"desiredCount": 1,
"pendingCount": 0,
"runningCount": 1,
"failedTasks": 0,
"createdAt": "2024-12-03T16:24:25.225000-05:00",
"updatedAt": "2024-12-03T16:25:15.837000-05:00",
"capacityProviderStrategy": [
{
"capacityProvider": "FARGATE",
"weight": 1,
"base": 0
}
],
"platformVersion": "1.4.0",
"platformFamily": "Linux",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-0d0eab1bb38d5ca64",
"subnet-0db5010045995c2d5"
],
"securityGroups": [
"sg-02556bf85a191f59a"
],
"assignPublicIp": "ENABLED"
}
},
"rolloutState": "COMPLETED",
"rolloutStateReason": "ECS deployment ecs-svc/1976744184940610707 completed."
}
],
"roleArn": "arn:aws:iam::123456789012:role/aws-service-role/ecs.amazonaws.com/AWSServiceRoleForECS",
"events": [],
"createdAt": "2024-12-03T16:24:25.225000-05:00",
"placementConstraints": [],
"placementStrategy": [],
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-0d0eab1bb38d5ca64",
"subnet-0db5010045995c2d5"
],
"securityGroups": [
"sg-02556bf85a191f59a"
],
"assignPublicIp": "ENABLED"
}
},
"healthCheckGracePeriodSeconds": 0,
"schedulingStrategy": "REPLICA",
"deploymentController": {
"type": "ECS"
},
"createdBy": "arn:aws:iam::123456789012:role/Admin",
"enableECSManagedTags": true,
"propagateTags": "NONE",
"enableExecuteCommand": false,
"availabilityZoneRebalancing": "ENABLED"
}
}
```
Untuk informasi selengkapnya, lihat [Memperbarui layanan Amazon ECS menggunakan konsol di](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/update-service-console-v2.html) Panduan *Pengembang Amazon ECS*.
+ Untuk detail API, lihat [UpdateService](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/update-service.html)di *Referensi AWS CLI Perintah*.
### `update-task-protection`
Contoh kode berikut menunjukkan cara menggunakan`update-task-protection`.
**AWS CLI**
**Contoh 1: Aktifkan perlindungan tugas untuk tugas ECS**
Berikut ini `update-task-protection` melindungi tugas ECS Anda dari penghentian selama scale-in dari Deployment atau Service. AutoScaling Anda dapat menentukan periode kedaluwarsa khusus untuk perlindungan tugas dari 1 hingga 2.880 menit (48 jam). Jika Anda tidak menentukan periode kedaluwarsa, mengaktifkan waktu default perlindungan tugas adalah 2 jam.
```
aws ecs update-task-protection \
--cluster ECS-project-update-cluster \
--tasks c43ed3b1331041f289316f958adb6a24 \
--protection-enabled \
--expires-in-minutes 300
```
Output:
```
{
"protectedTasks": [
{
"taskArn": "arn:aws:ecs:us-west-2:123456789012:task/c43ed3b1331041f289316f958adb6a24",
"protectionEnabled": true,
"expirationDate": "2024-09-14T19:53:36.687000-05:00"
}
],
"failures": []
}
```
**Contoh 2: Nonaktifkan perlindungan tugas untuk tugas ECS**
Berikut ini `update-task-protection` menonaktifkan tugas yang dilindungi dari skala dari Deployment atau Service. AutoScaling
```
aws ecs update-task-protection \
--cluster ECS-project-update-cluster \
--tasks c43ed3b1331041f289316f958adb6a24 \
--no-protection-enabled
```
Output:
```
{
"protectedTasks": [
{
"taskArn": "arn:aws:ecs:us-west-2:123456789012:task/c43ed3b1331041f289316f958adb6a24",
"protectionEnabled": false
}
],
"failures": []
}
```
Untuk pembentukan selengkapnya tentang perlindungan tugas, lihat [Melindungi tugas Amazon ECS agar tidak dihentikan oleh peristiwa penskalaan dalam Panduan Pengembang](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-scale-in-protection.html) *Amazon* ECS.
+ Untuk detail API, lihat [UpdateTaskProtection](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/update-task-protection.html)di *Referensi AWS CLI Perintah*.
### `update-task-set`
Contoh kode berikut menunjukkan cara menggunakan`update-task-set`.
**AWS CLI**
**Untuk memperbarui set tugas**
`update-task-set`Contoh berikut memperbarui set tugas untuk menyesuaikan skala.
```
aws ecs update-task-set \
--cluster MyCluster \
--service MyService \
--task-set arn:aws:ecs:us-west-2:123456789012:task-set/MyCluster/MyService/ecs-svc/1234567890123456789 \
--scale value=50,unit=PERCENT
```
Output:
```
{
"taskSet": {
"id": "ecs-svc/1234567890123456789",
"taskSetArn": "arn:aws:ecs:us-west-2:123456789012:task-set/MyCluster/MyService/ecs-svc/1234567890123456789",
"status": "ACTIVE",
"taskDefinition": "arn:aws:ecs:us-west-2:123456789012:task-definition/sample-fargate:2",
"computedDesiredCount": 0,
"pendingCount": 0,
"runningCount": 0,
"createdAt": 1557128360.711,
"updatedAt": 1557129279.914,
"launchType": "EC2",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
"subnet-12344321"
],
"securityGroups": [
"sg-12344321"
],
"assignPublicIp": "DISABLED"
}
},
"loadBalancers": [],
"serviceRegistries": [],
"scale": {
"value": 50.0,
"unit": "PERCENT"
},
"stabilityStatus": "STABILIZING",
"stabilityStatusAt": 1557129279.914
}
}
```
+ Untuk detail API, lihat [UpdateTaskSet](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/update-task-set.html)di *Referensi AWS CLI Perintah*.