> For the complete documentation index, see [llms.txt](https://help.cloudstoragesec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cloudstoragesec.com/trouble-shooting/rebooting-the-management-console.md).

# Rebooting the Management Console

Rebooting the console is a simple process.

{% hint style="info" %}
Ensure you are in the region you installed the Antivirus for Amazon S3 Management Console.
{% endhint %}

<figure><img src="https://905555942-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlGcQw8I2CHyi1loKBlfi%2Fuploads%2Fnd0515maRw6bLbSfSamr%2Frestartconsoleservice.gif?alt=media&amp;token=ed762916-f56a-4c2a-bee8-197e069f3c42" alt=""><figcaption></figcaption></figure>

1. First, login to the [AWS Console](https://console.aws.amazon.com/)
2. Then, navigate to the Elastic Container Service
3. Click into the Cluster that matches your deployment to see the details and services, then go to the Console Service
4. Check the box for `Force New Deployment` and click the `Skip to Review` button
5. Finally, click the `Update Service` button
6. That is it. Your console should reboot shortly in the next few minutes. A new task will spin up, once that new task is healthy the old task will spin down.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.cloudstoragesec.com/trouble-shooting/rebooting-the-management-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.