Updating deployment instructions

evertonfraga · evertonfraga · commit 4339e2ed4a0a · 2024-07-12T10:31:09.000-04:00
diff --git a/lib/sui/README.md b/lib/sui/README.md
@@ -10,7 +10,7 @@ This blueprint has step by step guides to set up a single Sui Full Node.
 
 
 ### Sui Full Node setup
-![SingleNodeSetup](./doc/assets/Architecture-SingleNode.png)
+![SingleNodeSetup](./doc/assets/Architecture-Single.png)
 
 This setup is for PoC or development environments and it supports Devnet, Testnet and Mainnet. It deploys a single EC2 instance with Sui client. The RPC port is exposed only to internal IP range of the VPC, while P2P ports allow external access to keep the client synced.
 
@@ -54,6 +54,8 @@ Create your own copy of `.env` file and edit it:
    cp ./sample-configs/.env-sample-full .env
    nano .env
 ```
+   **NOTE:** You can find more examples inside the `sample-configs` directory.
+
 
 4. Deploy common components such as IAM role, and Amazon S3 bucket to store data snapshots
 
@@ -65,15 +67,16 @@ Create your own copy of `.env` file and edit it:
 
 ### Deploy Sui Full-Node
 
-1. Deploy JSON_RPC Full Node
+1. Deploy Full Node
 
 ```bash
    pwd
    # Make sure you are in aws-blockchain-node-runners/lib/sui
    npx cdk deploy sui-single-node --json --outputs-file single-node-deploy.json
 ```
+   **NOTE:** The default VPC must have at least two public subnets in different Availability Zones, and public subnet must set `Auto-assign public IPv4 address` to `YES`.
 
-   The EC2 instance will deploy, initialize the node and start the first sync. In Cloudformation the instance will show as successful once the node is running. From that point it still takes a while until the node is synced to the blockchain. You can check the sync status with the REST call below in step 4. If the `curl cannot connect to the node on port 8732, then the node is still importing. Once that's done, the curl command works. 
+   The EC2 instance will deploy, initialize the node and start the first sync. In Cloudformation the instance will show as successful once the node is running. From that point it still takes a while until the node is synced to the blockchain. You can check the sync status with the REST call below in step 4. If the `curl cannot connect to the node on port 9000, then the node is still importing. Once that's done, the curl command works. 
 
 2. After starting the node you need to wait for the inital syncronization process to finish. It may take from an hour to half a day depending on the the state of the network. You can use Amazon CloudWatch to track the progress. To see them:
 
@@ -82,11 +85,7 @@ Create your own copy of `.env` file and edit it:
 
 4. Once the initial synchronization is done, you should be able to access the RPC API of that node from within the same VPC. The RPC port is not exposed to the Internet. Check if the JSON-RPC port is open and working — run the following command from a terminal:
 
-```bash
-   INSTANCE_ID=$(cat single-node-deploy.json | jq -r '..|.singleinstanceid? | select(. != null)')
-   NODE_INTERNAL_IP=$(aws ec2 describe-instances --instance-ids $INSTANCE_ID --query 'Reservations[*].Instances[*].PrivateIpAddress' --output text)
-
-    # We query if the node is synced to main
+``` We query if the node is synced to main
     ## replace <your IP address> with your server IP address
 curl --location --request POST <your IP address>:9000 \
 --header 'Content-Type: application/json' \
@@ -95,8 +94,15 @@ curl --location --request POST <your IP address>:9000 \
 
 The result should start like like this (the actual balance might change):
 
-```{"jsonrpc":"2.0","result":{"openrpc":"1.2.6","info":{"title":"Sui JSON-RPC","description":"Sui JSON-RPC API for interaction with Sui Full node. Make RPC calls using https://fullnode.NETWORK.sui.io:443, where NETWORK is the network you want to use (testnet, devnet, mainnet). By default, local networks use port 9000.","contact":{"name":"Mysten Labs","url":"https://mystenlabs.com","email":"build@mystenlabs.com"},"license":{"name":"Apache-2.0","url":"https://raw.githubusercontent.com/MystenLabs/sui/main/LICENSE"},"version":"1.28.2"},"methods
 ```
+{"jsonrpc":"2.0","result":{"openrpc":"1.2.6","info":{"title":"Sui JSON-RPC","description":"Sui JSON-RPC API for interaction with Sui Full node. Make RPC calls using https://fullnode.NETWORK.sui.io:443, where NETWORK is the network you want to use (testnet, devnet, mainnet). By default, local networks use port 9000.","contact":{"name":"Mysten Labs","url":"https://mystenlabs.com","email":"build@mystenlabs.com"},"license":{"name":"Apache-2.0","url":"https://raw.githubusercontent.com/MystenLabs/sui/main/LICENSE"},"version":"1.28.2"},"methods
+```
+
+
+
+
+
+
 
 
 ### Clearing up and undeploying everything
@@ -117,7 +123,7 @@ The result should start like like this (the actual balance might change):
 
     # You need to manually delete an s3 bucket with a name similar to 'sui-snapshots-$accountid-tz-nodes-common' on the console,firstly empty the bucket,secondly delete the bucket,and then execute
     # Delete all common components like IAM role and Security Group
-    cdk destroy dui-common
+    cdk destroy sui-common
 ```
 
 2. Follow steps to delete the Cloud9 instance in [Cloud9 Setup](../../doc/setup-cloud9.md)
@@ -132,8 +138,98 @@ The result should start like like this (the actual balance might change):
    pwd
    # Make sure you are in aws-blockchain-node-runners/lib/Sui
 
-   export INSTANCE_ID=$(cat single-node-deploy.json | jq -r '..|.single-node-instance-id? | select(. != null)')
+   export INSTANCE_ID=$(jq -r '.["sui-single-node-testnet"].nodeinstanceid' single-node-deploy.json)
    echo "INSTANCE_ID=" $INSTANCE_ID
-   aws ssm start-session --target $INSTANCE_ID --region $AWS_REGION
+   aws ssm start-session --target $INSTANCE_ID
    sudo cat /var/log/cloud-init-output.log
 ```
+
+2. If SSH is disabled, how to login to fullnode instance?
+
+```bash
+   NODE_INTERNAL_IP=$(aws ec2 describe-instances --instance-ids $INSTANCE_ID --query 'Reservations[*].Instances[*].PrivateIpAddress' --output text)
+   echo "NODE_INTERNAL_IP="$NODE_INTERNAL_IP
+    pwd
+   # Make sure you are in aws-blockchain-node-runners/lib/Sui
+   aws ssm start-session --target $INSTANCE_ID
+  
+```
+
+3. Service Tools
+
+```
+#Check Sui version
+sui -V
+# Check node logs
+sudo journalctl -fu suid -o cat
+# Check node status
+sudo service suid status
+# Restart node
+sudo systemctl restart suid
+# Stop Node
+sudo systemctl stop suid
+# Start Node
+sudo systemctl start suid
+```
+
+4. Journalctl and Node Status throws errors:
+
+Set up archival fallback to enable your node to fallback to an archive in case of lag, add this block to your fullnode.yaml file as described here https://docs.sui.io/guides/operator/archives#set-up-archival-fallback. Restart Node
+
+```
+Example:
+
+state-archive-read-config:
+  - object-store-config:
+      object-store: "S3"
+      # Use mysten-testnet-archives for testnet 
+      # Use mysten-mainnet-archives for mainnet
+      bucket: "mysten-testnet-archives"
+      # Use your AWS account access key id
+      aws-access-key-id: ""
+      # Use your AWS account secret access key
+      aws-secret-access-key: ""
+      aws-region: "us-west-2"
+      object-store-connection-limit: 20
+    # How many objects to read ahead when catching up  
+    concurrency: 5
+    # Whether to prune local state based on latest checkpoint in archive.
+    # This should stay false for most use cases
+    use-for-pruning-watermark: false
+
+```
+
+5. Restoring a Full node using snapshots: Restoring using RocksDB snapshots to restore from a RocksDB snapshot, follow these steps (https://docs.sui.io/guides/operator/snapshots):
+```
+Syntax:
+sui-tool download-db-snapshot --latest \
+    --network <NETWORK> --snapshot-bucket <BUCKET-NAME> \
+    --snapshot-bucket-type <TYPE> --path <PATH-TO-NODE-DB> \
+    --num-parallel-downloads 25 \
+    --skip-indexes \
+    --no-sign-request
+
+ 
+Example:   
+sudo sui-tool download-db-snapshot --latest --network testnet --path /data/sui/db/live --num-parallel-downloads 50 --skip-indexes --no-sign-request
+
+```
+
+6. Compare the number of checkpoints on your node and on chain
+
+```bash
+ ## replace <your IP address> with your server IP address
+curl -q <your IP address>:9184/metrics 2>/dev/null |grep '^highest_synced_checkpoint'; echo
+```
+```bash
+## replace <Network_ID> with devnet| testnet | mainnet
+curl --location --request POST 'https://fullnode.<Network_ID>.sui.io:443/' --header 'Content-Type: application/json' --data-raw '{"jsonrpc":"2.0", "id":1,"method":"sui_getLatestCheckpointSequenceNumber"}'; echo
+```
+
+7. Monitoring Sui node metrics over port TCP/9184
+
+```
+Enter your node's external IP at https://node.sui.zvalid.com/
+```
+
+
