> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/aeternity-user-tools-and-services/run-an-aeternity-node.md).

# Run an æternity node

### Getting Started with Nodes

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Node Documentation and Installation Guide</td><td><a href="broken://spaces/yxhRUAwn7tH8JUboTur7/pages/E0OkdK3UgNsNIyzyhK54">Broken link</a></td><td><a href="https://839505583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FggVl0Jqy6Dd8f38hGk63%2Fuploads%2FO7MHc7XJYKrtCX2zPCz5%2Fflip-30deg-gradient2.svg?alt=media&amp;token=9a5fcdda-f853-495e-a65b-ac9c4272af37">flip-30deg-gradient2.svg</a></td></tr><tr><td>Node API reference</td><td><a href="broken://pages/AaUPF6iS9cpYczkzcYHq">Broken link</a></td><td><a href="https://839505583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FggVl0Jqy6Dd8f38hGk63%2Fuploads%2FuCuUz6N9JVi7JNEARpet%2F30deg-gradient.svg?alt=media&amp;token=14b19a78-76dd-40be-b953-2b92048cd356">30deg-gradient.svg</a></td></tr></tbody></table>

#### Running a Node

Running an æternity node involves several key steps. First, you'll need to install the required dependencies and download the node software. After configuring your node settings according to your intended role in the network, you can start the node and connect to the network. Detailed installation and configuration guides are available in the technical documentation.

#### Best Practices

Successful node operation requires attention to several key areas. Ensuring sufficient hardware resources and maintaining good network connectivity are essential for optimal performance. Keeping your node software updated and following security best practices will help maintain the network's integrity. Regular monitoring and maintenance will ensure your node continues to operate effectively.

### Node Monitoring and Maintenance

#### Performance Monitoring

Effective node operation requires continuous monitoring of several key metrics. Your node's synchronization status indicates how well it's keeping up with the network. Memory usage and network connectivity affect your node's ability to process transactions and communicate with peers. Processing performance and block validation speed are crucial indicators of your node's health and contribution to the network.

#### Maintenance Tasks

Regular maintenance is essential for keeping your node running smoothly. This includes updating node software as new versions become available and backing up node data to prevent loss. Regular monitoring of disk space and network connections, along with reviewing log files, helps prevent potential issues before they impact performance.


---

# 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://docs.aeternity.com/aeternity-user-tools-and-services/run-an-aeternity-node.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.
