> For the complete documentation index, see [llms.txt](https://launchnodes.gitbook.io/prysmatic-validator-node-for-eigenlayer-restaking/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://launchnodes.gitbook.io/prysmatic-validator-node-for-eigenlayer-restaking/aws-validator-node-set-up.md).

# AWS Validator Node Set Up

{% hint style="info" %}
[Register](https://7lftpmcph2j.typeform.com/to/UJYhysZt) to get free enhanced support!
{% endhint %}

To stake Ethereum, validator nodes are required to connect to Beacon nodes. The Validator and the beacon node are referred to as consensus layer clients. Launchnodes provide the Prysmatic Validator client and it connects to a Launchnodes Beacon Node (with Flashbots MEV Enabled) by default or clients can connect their Validator nodes to their own Beacon Nodes. The Beacon node Consensus layer client needs to connect to an execution layer client in order to synchronise, the consensus layer client that is used is Geth. The diagram provides a high level architecture of how the nodes work.

<figure><img src="/files/8yx0ly1sbRBbv1hsIW6U" alt=""><figcaption><p>High-level architecture </p></figcaption></figure>

### Maximum Extractable Value (MEV):

Maximal extractable value (MEV) refers to the maximum value that can be extracted from block production in excess of the standard block reward and gas fees by including, excluding, and changing the order of transactions in a block.

This node setup uses flashbots MEV. Flashbots is an independent project which extends execution clients with a service that allows searchers to submit MEV transactions to validators without revealing them to the public mempool.


---

# 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://launchnodes.gitbook.io/prysmatic-validator-node-for-eigenlayer-restaking/aws-validator-node-set-up.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.