Skip to content

Commit 718f50a

Browse files
authored
Merge pull request #38 from aws-samples/eth-single-node
Single node Ethereum setup - add diagram to the Readme file
2 parents 558b34e + 75103b4 commit 718f50a

File tree

2 files changed

+9
-1
lines changed

2 files changed

+9
-1
lines changed

lib/ethereum/README.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,14 @@
22

33
## Architecture Overview
44

5+
This blueprint has two options for running nodes. You can set up a single JSON RPC node or multiple nodes in highly-available setup. The details are below.
6+
7+
### Single RPC node setup
8+
![SingleNodeSetup](./doc/assets/Architecture-PoC.png)
9+
10+
This setup is for small scale PoC or development environments. It deploys a single EC2 instance with both consensus and execution clients. The RPC port is exposed only to internal IP range of the VPC, while P2P ports allow external access to keep the clients synced.
11+
12+
### Highly available setup
513
![Architecture](./doc/assets/Architecture.png)
614

715
1. An ongoing data synchronization process is configured with nodes in the Ethereum network with a sync node and RPC nodes.
@@ -131,7 +139,7 @@ The result should be like this (the actual balance might change):
131139
{"jsonrpc":"2.0","id":1,"result":"0xe791d050f91d9949d344d"}
132140
```
133141

134-
### Option 2: Deploy the Highly Available RPC Nodes
142+
### Option 2: Highly Available RPC Nodes
135143

136144
1. Deploy Sync Node
137145

106 KB
Loading

0 commit comments

Comments
 (0)