Practical overview
When it fits
Use it when you are prepared to manage AWS resources and want a template-based way to deploy public-facing Ethereum nodes with a selectable client and ethstats monitoring.
Who it is for
- Operators who want to deploy public-facing Ethereum nodes in their own AWS account.
- Teams choosing between Geth and Parity and wanting an ethstats view of deployed-node status.
Documented uses
- Create a CloudFormation stack for one or more Ethereum nodes.
- Choose Geth or Parity as the node client and configure AWS instance types and node count.
- View real-time information about deployed nodes through ethstats.
- Delete the CloudFormation stack when the deployment is no longer needed.
Requirements & limits
Deployment requires an active AWS account and uses billable AWS infrastructure. The repository identifies an MIT license.
- The deployment is created in your AWS account, so EC2 costs and ongoing billing oversight matter.
- You need an AWS key pair registered to the account.
- The template exposes an SSH access-range setting whose documented default is 0.0.0.0/0; review it before creating the stack.
- The choice of Geth or Parity is made by selecting the corresponding CloudFormation template.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Deploy an Ethereum node stack with CloudFormation
Create a public-facing Ethereum node stack using the Geth or Parity template and view its endpoint and ethstats status address.
Before you start
- An active AWS account.
- A key pair registered to the AWS account.
- Review of EC2 pricing and a plan to monitor AWS charges; deployment uses real, billable infrastructure.
Steps
Save the CloudFormation JSON template for either Geth or Parity.
In the AWS console, open CloudFormation, create a stack, and upload the chosen template.
Configure the stack name, ethstats password and server instance type, node instance type and count, key pair name, and SSH access range; review the configuration and create the stack.
Wait for CREATE_COMPLETE, then open the stack’s Outputs to find the ethstats IP and node URL.
Expected outcome
A deployed Ethereum node stack, with an output URL for connecting to the nodes and an ethstats address for viewing node status.
Guide limitations
- AWS infrastructure incurs real costs; the README advises understanding EC2 pricing and setting billing alerts.
- The documented default SSH access range is 0.0.0.0/0; the operator should review the setting.
Remove a deployed stack
Delete the CloudFormation stack created for the node deployment.
Before you start
- Access to the AWS account containing the deployed stack.
Steps
Open CloudFormation in the AWS console.
Select the deployed stack, choose Delete Stack, and confirm.
Expected outcome
The CloudFormation stack is deleted.
Guide limitations
- The README documents deleting the stack but does not describe separate cleanup procedures for resources outside that stack.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- MyEtherWallet/docker-geth-lb · Official homepage title · retained in its source language