Amazon ECS
Last updated 16 October 2026
ARNscope opens an ECS service where an incident starts: is the rollout healthy? One page shows the service’s deployments and events, its CPU and memory, every task with its containers and stop reason, and each container’s logs, with a server-side search and a live tail. Changes are rare and deliberate: a deploy always asks first.
Clusters and services
Open ECS in ARNscope and choose the profile and region. The list shows every cluster with its service count and running and pending tasks; expand a cluster to see its services, each with running over desired tasks. Type in the filter to narrow clusters and services by name.
Select a service to open it. The header shows its status (for example Deploying or Degraded), the task definition revision and the cluster, then a strip with running, desired, pending and failed tasks, the capacity provider or launch type, the rollout state and the number of deployments.
| Tab | What it shows |
|---|---|
| Overview | Recent warnings, deployments, utilization, load balancing, network and configuration |
| Tasks | Running or recently stopped tasks, and a task pane with details, containers and logs |
| Events | The service’s latest events, newest first |
| Network | Who the service talks to, from VPC flow logs |
| Task definition | The revision the service runs |
Deployments
Deployments lists each deployment with its role (Primary or Active), its rollout state, the revision, when it started and was last updated, a bar of running and pending tasks against desired, and the failed count. During a rollout you see the new revision coming up beside the old one draining, with ECS’s own message under each.
Warnings and events
Warnings from the last 24 hours sit at the top of the Overview, such as failing load balancer health checks or unhealthy targets. All events opens the Events tab, which lists the latest events newest first. Filter them by text, or tick Warnings only; the tab’s badge counts the warnings.
Utilization
Utilization charts CPU and memory (average and maximum across the service’s tasks) and, when Container Insights is on for the cluster, the running task count. The data is CloudWatch’s AWS/ECS metrics; choose the last 3 or 24 hours. A service whose memory climbs until tasks restart shows it as a sawtooth.
Tasks
Tasks lists the service’s running tasks, or with Stopped the ones that stopped recently (ECS keeps stopped tasks for about an hour). Filter by task id, IP address, availability zone or stop reason. Select a task to open its pane:
- Details: status and health, the stop code and reason for a stopped task, its lifecycle (created, started, stopped, how long it ran), placement and attachments.
- Containers: each container’s image and digest, health, exit code and reason, CPU and memory, private IP and ports.
- Logs: the container’s log stream; see below.
Container logs
The Logs tab reads the container’s stream when its task definition uses the awslogs log driver with a stream prefix; ARNscope works out the stream name from the task id. Lines open newest first, 200 at a time, and Load older walks back through the stream. With several containers, pick one from the menu.
To search, type a CloudWatch Logs filter pattern and press Enter, or click Search warnings and errors, which searches for common error and warning words. The search runs in CloudWatch Logs over that one stream, so it finds matches the loaded page does not hold.
For a running task, Live tail follows new lines as the container writes them. It uses CloudWatch Logs Live Tail, which AWS bills per minute, so it starts only when you click it and stops when you click again or leave the tab.
Open in Logs opens the container’s log group on the CloudWatch Logs page, on the same stream, for searches across streams, Logs Insights and favourites.
Split view
Drag a cluster or service from the list onto the right side of the window to open it beside the one you have. Each side keeps its own tab and selection, so you can watch a rollout on one service and the errors on another.
Deploying
Deploy offers Force new deployment (the same revision, new tasks) and Deploy a revision… (pick a registered revision). Either one opens a confirmation bar naming the service, cluster and profile; nothing changes until you click Deploy now. ARNscope then follows the rollout, refreshing the service every five seconds, until ECS reports it completed or failed (for up to 15 minutes).
Edit task definition edits the current revision as a form or as JSON, shows what changed, and registers it as a new revision with Save revision, or registers and deploys it with Save & deploy. Both ask first.
Permissions
| What | Actions |
|---|---|
| Clusters, services and tasks | ecs:ListClusters, ecs:DescribeClusters, ecs:ListServices, ecs:DescribeServices, ecs:ListTasks, ecs:DescribeTasks |
| Task definitions | ecs:DescribeTaskDefinition, ecs:ListTaskDefinitions |
| Utilization | cloudwatch:GetMetricData |
| Container logs | logs:GetLogEvents, logs:FilterLogEvents; live tail logs:DescribeLogGroups, logs:StartLiveTail, logs:StopLiveTail |
| Deploy | ecs:UpdateService; editing also ecs:RegisterTaskDefinition and iam:PassRole for the task’s roles |
| Network | ec2:DescribeNetworkInterfaces, ec2:DescribeFlowLogs, and Logs Insights on the flow log group |
Use the permission check to see which your profile is missing. When your role is denied ecs:UpdateService, Deploy is disabled and says why.
Limitations
- No stop, scale or exec. ARNscope does not stop tasks, change a service’s desired count or open ECS Exec sessions.
awslogsonly. Container logs are shown for theawslogsdriver with a stream prefix. FireLens, Splunk and other drivers ship logs elsewhere.- Recently stopped tasks only. ECS returns stopped tasks for about an hour after they stop.
- Task counts need Container Insights. CPU and memory come from
AWS/ECS; the running task chart needs Container Insights on the cluster. - Live tail costs money. CloudWatch Logs Live Tail is billed per minute while it runs.