> For the complete documentation index, see [llms.txt](https://orbs-doc.gitbook.io/orbs-guardian-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://orbs-doc.gitbook.io/orbs-guardian-help/en/orbs-node-recovery/node-using-aws-cli.md).

# Node using AWS CLI

## Solution 1. Restart your AWS EC2

This solution tries simple server restarting.

* Please get logged in AWS console

### Instructions

1. open <https://aws.amazon.com/> and log in with your guardian's account.
2. Please make sure right region is selected where your node is installed. (Region info is on the right top)
3. Go to EC2 service menu.

   <figure><img src="https://274447141-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnntATZcqsyWj32j5CQbd%2Fuploads%2FVDsLmfriYgrtrIUPMv41%2Fimage.png?alt=media&amp;token=e2c3f46b-a131-4852-b9f4-789f4da62531" alt=""><figcaption></figcaption></figure>
4. Select Instances(running)

   <figure><img src="https://274447141-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnntATZcqsyWj32j5CQbd%2Fuploads%2FrWTl80WaPVUdqG6wC6Rz%2Fimage.png?alt=media&amp;token=277fb03a-487e-4c00-826a-0049768686ea" alt=""><figcaption></figcaption></figure>
5. Select checkbox of current instance and try reboot instance.

   <figure><img src="https://274447141-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnntATZcqsyWj32j5CQbd%2Fuploads%2FmkmQ5jQ4cWi41xOAkyJb%2Fimage.png?alt=media&amp;token=3aede63a-476c-4c7c-9084-ad7299b04f53" alt=""><figcaption></figcaption></figure>
6. Please wait rebooting and check [status page](https://status.orbs.network/) after 30-60 mins. If your node is still offline, try the next solution.

***

## Solution 2. Re-install Node

This solution tries simple server restarting.

* Please get logged in your local machine which you used when install node previously (Mac or linux terminal)

### Instructions

1. Open "Terminal"
2. change directory to folder where "`orbs-node.json`" file located.(ie. `cd orbs-node`)
3. `ls` command will show you files in current directory. Please make sure there is `orbs-node.json` file.

   <div align="left"><figure><img src="https://274447141-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnntATZcqsyWj32j5CQbd%2Fuploads%2FAxKLUeYVdkAYDm0pXrTo%2Fimage.png?alt=media&amp;token=467a52ab-29cd-4900-b8a4-d3bc50e9b250" alt=""><figcaption></figcaption></figure></div>
4. update polygon CLI to the latest one

   ```
   npm update -g @orbs-network/polygon
   ```
5. Destory node using command below.

   ```
   polygon destroy -f orbs-node.json
   ```
6. Please wait until success massage displayed.
7. When destroy command success, try create node again with command below.\
   (`pkey.txt` is and example. If you have another name or different way to refer private key of node address, use proper command)

   ```
   polygon create -f orbs-node.json --orbs-private-key $(cat pkey.txt)
   ```
8. Please wait until success massage displayed.
9. Please wait and hour and check [status page](https://status.orbs.network/). It can take 24 hours having all green.<br>

   <div align="left"><figure><img src="https://274447141-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnntATZcqsyWj32j5CQbd%2Fuploads%2FRuJ1z910yUWV5g9VZRY2%2F%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202025-03-14%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%201.02.10.png?alt=media&amp;token=046c4fdc-0c7e-4fec-9efa-cff419638771" alt=""><figcaption></figcaption></figure></div>
10. If it keeps offline, please contact <eddy@orbs.com>.