Skip to content

Commit ff61c18

Browse files
committed
Final changes based on test results and changes to the docs
1 parent e94323f commit ff61c18

File tree

2 files changed

+7
-6
lines changed

2 files changed

+7
-6
lines changed

lib/scroll/README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Sample AWS Blockchain Node Runner app for Scroll Nodes
22

3-
This is RPC Scroll nodes (L2Geth) setup on AWS guide.
3+
[Scroll](https://docs.scroll.io/en/getting-started/overview/) is a "Layer 2" scaling solution for Ethereum leveraging zero knowledge proofs. This blueprint helps to deploy Scroll nodes (L2Geth) on AWS as RPC nodes and use [Amazon Managed Blockchain Access Ethereum](https://docs.aws.amazon.com/managed-blockchain/latest/ethereum-dev/ethereum-concepts.html) node for "Layer 1". It is meant to be used for development, testing or Proof of Concept purposes.
44

55
## Overview of Deployment Architectures for Single Node setups
66

@@ -59,7 +59,7 @@ This is the Well-Architected checklist for Ethereum nodes implementation of the
5959
**Recommended for Scroll node**
6060

6161
- Instance type [m6a.2xlarge](https://aws.amazon.com/ec2/instance-types/m6a/).
62-
- 1TB EBS gp3 storage with at least 3000 IOPS.`
62+
- 500GB EBS gp3 storage with at least 3000 IOPS.`
6363

6464
**Amazon Managed Blockchain Ethereum L1**
6565

@@ -174,10 +174,10 @@ We will use AWS Cloud9 to execute the subsequent commands. Follow the instructio
174174
```
175175
176176
### Monitoring
177-
It may take about 30 minutes and you can use Amazon CloudWatch to track the progress. There is a script that publishes CloudWatch metrics every 5 minutes, where you can watch current block and slots behind metrics. When the node is fully synced the slots behind metric should go to 0. To see them:
177+
A script on the Scroll node publishes current block and blocks behind metrics to CloudWatch metrics every 5 minutes. When the node is fully synced the blocks behind metric should get to 0, which might take about 1.5 days. To see the metrics:
178178
179-
Navigate to CloudWatch service (make sure you are in the region you have specified for AWS_REGION)
180-
Open Dashboards and select scroll-single-node from the list of dashboards.
179+
- Navigate to CloudWatch service (make sure you are in the region you have specified for AWS_REGION)
180+
- Open Dashboards and select `scroll-single-node` from the list of dashboards.
181181
182182
## Clear up and undeploy everything
183183
@@ -217,7 +217,7 @@ Open Dashboards and select scroll-single-node from the list of dashboards.
217217
echo "INSTANCE_ID=" $INSTANCE_ID
218218
export AWS_REGION=us-east-1
219219
aws ssm start-session --target $INSTANCE_ID --region $AWS_REGION
220-
sudo journalctl -o cat -fu sol
220+
sudo journalctl -o cat -fu scroll
221221
```
222222
2. How to check the logs from the EC2 user-data script?
223223

website/docs/Blueprints/intro.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,3 +43,4 @@ First of all, THANK YOU! The easier it is to run a blockchain node on AWS the si
4343
- `lib/constructs/ha-rpc-nodes-with-alb.ts` - Provisions up to 4 identical EC2 instances to run nodes managed by an Auto Scaling Group and behind an Application Load Balancer.
4444
- `lib/constructs/single-node.ts` - Creates a single EC2 instance to run a blockchain node.
4545
- `lib/constructs/snapshots-bucket.ts` - Creates an S3 bucket to store a copy of blockchain node state to speed up syncing process.
46+
- `lib/constructs/amb-ethereum-single-node.ts` - Creates a single Ethereum node with [Amazon Managed Blockchain Access](https://docs.aws.amazon.com/managed-blockchain/latest/ethereum-dev/ethereum-concepts.html).

0 commit comments

Comments
 (0)