Using Amazon ECS Exec for debugging

• Note This configuration only handles the logging of the execute-command session. It doesn't affect logging of your application.

• Note Because the execute-command API action contains only task and cluster resources in a request, only cluster and task tags are evaluated.

Troubleshooting ECS Anywhere issues

• Important Amazon ECS provides the Amazon ECS logs collection tool. You can use it to collect logs from your external instances for troubleshooting purposes. For more information, see .

Checking stopped tasks for errors

• Important Stopped tasks only appear in the Amazon ECS console, AWS CLI, and AWS SDKs for at least 1 hour after the task stops. After that, the details of the stopped task expire and aren't available in Amazon ECS. Amazon ECS also sends task state change events to Amazon EventBridge. You can't view events in EventBridge. Instead, you create rules to send the events to other persistent storage such as Amazon CloudWatch Logs. You can use the storage to view your stopped task details after it has expired from view in the Amazon ECS console. For more information, see . For a sample EventBridge configuration to archive Amazon ECS events to Amazon CloudWatch Logs, see on the GitHub website.

Invalid CPU or memory value specified

• Note When using Terraform, the following error may be returned.

• Note Task-level CPU and memory parameters are ignored for Windows containers.

Using Docker debug output

Amazon ECS Log File Locations

Amazon ECS logs collector

Agent introspection diagnostics

• Note The command below is piped through the python -mjson.tool for greater readability.

Docker diagnostics

API failure reasons