Cleaned up the index page and build error

casper-network · Sep 6, 2023 · 2ecbe4e · 2ecbe4e
1 parent 847569a
commit 2ecbe4e
Showing 1 changed file with 21 additions and 30 deletions.
diff --git a/source/docs/casper/operators/aws-nodes/index.md b/source/docs/casper/operators/aws-nodes/index.md
@@ -4,45 +4,36 @@ title: AWS Nodes
 
 # Read-Only Casper Nodes in AWS
 
-This project comprises the implementation of the Infrastructure as Code (IaC) to deploy a *read-only* [Casper node](https://github.com/casper-network/casper-node) on AWS. The procedure for the creation of this node is strongly based on the document *"[Setup Main Net validator node from scratch on Ubuntu 20.04 on AWS](https://docs.cspr.community/docs/aws/setup-mainnet-validator-from-scratch.html)"* until before *bonding*. Bonding makes the node a validator node, which is outside of the scope of the infrastructure as code developed in this project at the moment. The project is developed using **Terraform**, **Terragrunt** and **Bash** mainly.
+The Casper ecosystem includes the [casper-node-on-cloud](https://github.com/casper-ecosystem/casper-node-on-cloud/) repository for creating Casper nodes using Amazon Web Services (AWS). The project uses an Infrastructure as code (IaC) approach with **Terraform**, **Terragrunt**, and **Bash**.
 
-## Advantages to use IaC to deploy a Read-only Node in a Cloud Service
+The procedure for creating Casper nodes in AWS is based on the steps for [Installing a Node](../setup/install-node.md) and does not include the steps for bonding to the network and becoming a validator. Bonding makes the node a validator node, which is outside the scope of the IaC infrastructure. Therefore, the Casper nodes created with this approach are read-only nodes.
 
-There are numerous advantages when it comes to running a Casper node on cloud using IaC, for this solution you will find:
+## Advantages of using IaC in AWS
 
-* Through this project, the operator can create a node between in less time than by doing it manually with just the execution of a command that will take care of creating the entire infrastructure.
-* You will have the option to add a security layer, including a VPN server for secure access to the node.
-* This architecture will include an Auto-Scaling mechanism, which is a cloud service that takes care of the lifecycle of the instance, in this case, the node. This allows for the addition of mechanisms to automatically recover the node from any problem that leaves it unresponsive, creating a new node and replacing the broken one.
-  * Maintain the same public IP
-  * Keep the keys in a secure service
-  * Backup of the node's data every week *(by default is every Friday at 00:00:00)*, when it is synchronized
+Running a Casper node using IaC in AWS has the following advantages:
+
+* An operator can create a node quickly with a single command that takes care of creating the entire infrastructure.
+* Operators can add a security layer, including a VPN server, for secure access to the node.
+* This architecture includes an auto-scaling mechanism, which takes care of the node lifecycle, allowing automatic recovery if the node is unresponsive, creating a new node, and replacing the unresponsive one.
+* The node maintains the same public IP.
+* A secure service can manage credentials.
+* This infrastructure allows for weekly backups of the node's data when the node is synchronized. The default schedule is every Friday at 00:00:00.
 
 ## Architecture
 
-The purpose of this architecture is to maintain the integrity and security of the node. In case of an unexpected shutdown, the autoscaling group will recreate a new node with the same keys and data so the node maintains the same information as the latter one.
+The purpose of this architecture is to maintain the integrity and security of the Casper node. In case of an unexpected shutdown, the autoscaling group will create a new node with the same keys and data.
 
 <p align="center">
-<img src={"/image/operators/aws-casper.png"} alt="Casper AWS Node Architecture" width="500"/>
+<img src={"/image/operators/aws-casper.png"} alt="Casper AWS Node Architecture"/>
 </p>
 
 ## Table of Contents
 
-| Topic    | Description                                                     |
-| ----------- | ------------------------------------------------------------ |
-| [How to deploy the infrastructure](./1-deploying.md) |  |
-| [Monitoring Node](./2-connecting.md)     |  |
-| [About the modules implementations](./3-modules.md) |   |
-| [Restore & Backup Blockchain data process](./4-backup.md) |  |
-| [Setup OpenVPN](./5-open-vpn.md)      |          |
-| [Troubleshooting](./6-troubleshooting.md)  |  |
-
-
-<!--
-Content from:
-
-Directory with the code: https://github.com/casper-ecosystem/casper-node-on-cloud/
-
-https://github.com/casper-ecosystem/casper-node-on-cloud/wiki
-
-https://docs.cspr.community/docs/aws/setup-testnet-validator-from-scratch.html
--->
+| Topic                                                     | Description                                         |
+| --------------------------------------------------------- | --------------------------------------------------- |
+| [Deploy the Infrastructure](./1-deploying.md)             | How to deploy the infrastructure in AWS.            |
+| [Validate and Monitor the Node](./2-connecting.md)        | Validate the AWS setup and monitor the Casper node. |
+| [Implemented Modules](./3-modules.md)                     | Details about the modules implemented in this IaC.  |
+| [Restore and Backup](./4-backup.md)                       | Restoring and Backing up Blockchain Data.           |
+| [Setup OpenVPN](./5-open-vpn.md)                          | Configure the Open VPN Server.                      |
+| [Troubleshooting](./6-troubleshooting.md)                 | Troubleshooting Tips for Operators.                 |