> For the complete documentation index, see [llms.txt](https://launchnodes.gitbook.io/lacnet-mainnet/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/lacnet-mainnet/query-eks-cluster.md).

# Query EKS Cluster

{% embed url="<https://drive.google.com/file/d/1AAS5VRDTbDSz1BSDZftqSc4xahukhMB8/view?usp=sharing>" %}

To perform operational commands and retrieve specific information about your EKS cluster, you can utilize the `ops.sh` script. This script provides various commands that can be executed in the AWS Cloud Shell or a terminal environment. Here are the available commands:

* `getPodRestart`: Use this command to restart the writer pods in the cluster.
* `getEnodeId`: Use this command to obtain the Enode ID of the Writer Node.
* `getNodeAddress`: Use this command to fetch the address of the Writer node.
* `getConnectionStatus`: Use this command to check the status of the nodes' connection.
* `getbesuLogs`: Use this command to view the besu container logs To execute any of these commands, follow these steps:

Step 1: Make sure you have the `ops.sh` script available. If not follow stage 3 again. Step 2: Open the AWS Cloud Shell or a terminal environment. Step 3: Navigate to the location where the `ops.sh` script is located. Step 4: Run the following command to source the script:

```
    source ops.sh
```

Once the script is sourced, you can run any of the commands mentioned above by simply typing the command in the AWS Cloud Shell and pressing Enter. The output will be displayed accordingly.

Note: Ensure that you have appropriate permissions and access to the EKS cluster before running these commands.


---

# 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/lacnet-mainnet/query-eks-cluster.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.