> For the complete documentation index, see [llms.txt](https://docs.kira.thiennguyen.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kira.thiennguyen.dev/user-guide/ecs.md).

# ECS

The ECS section lets you inspect and operate your Elastic Container Service workloads without leaving Kira.

## Browse clusters, services, and tasks

Drill from **clusters → services → tasks**. For each service you can see its running tasks, the task definition it's using, and its current state. If you've pre-listed clusters for an account in your [configuration](/getting-started/configuration.md#accounts), they show up ready to go; otherwise Kira lists what the account exposes.

## Task definitions & revisions

Open a service's **task definition** to see its containers, images, and settings. You can browse **revisions** of a task-definition family and **compare** two revisions to see exactly what changed between deploys — useful when diagnosing a regression. Deep links such as `kira://ecs/task-def?...` and `kira://ecs/compare?...` open these views directly (see [Navigating Kira](/user-guide/navigation.md#deep-links-kira)).

## Operate services

| Action        | What it does                                                                   |
| ------------- | ------------------------------------------------------------------------------ |
| **Redeploy**  | Force a new deployment of the service (pull the latest image / restart tasks). |
| **Scale**     | Change the desired task count.                                                 |
| **Roll back** | Move the service back to a previous task-definition revision.                  |

{% hint style="info" %}
Services managed by **Application Auto Scaling** are detected as such, so scaling and capacity reflect the autoscaling configuration rather than a fixed desired count.
{% endhint %}

## Health & metrics

Kira surfaces **service health** and **CloudWatch metrics** (such as CPU and memory utilisation) for a service, so you can see how a deployment is behaving at a glance.

## ECS Exec — a shell inside a task

When ECS Exec is enabled for a task, Kira can open an **interactive terminal session inside a running container**. This drops you into a full terminal (backed by a real PTY) so you can run commands, inspect the environment, and debug live — no bastion host or manual `aws ecs execute-command` required.

Kira checks the prerequisites for ECS Exec before connecting and tells you if something (IAM permissions, the SSM agent, or task configuration) is missing.

## Logs

Jump from a service or task to its **CloudWatch Logs** to follow output in real time. See [CloudWatch Logs](/user-guide/logs.md) for the dedicated log viewer.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kira.thiennguyen.dev/user-guide/ecs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.