AWS EC2 archive node setup with OpenEthereum (formerly Parity)
The following provides an example node setup. Performance related parameters will vary per chain.
Last updated
Was this helpful?
The following provides an example node setup. Performance related parameters will vary per chain.
Last updated
Was this helpful?
See the for complete instructions for any chain setup
Setup an EC2 instance and choose the best available storage (ie NVMe SSD).
During setup you will . For security purposes, you should limit the inbound traffic to RPC and WebSocket interfaces (default ports are 8545
and 8546
). Limit connection to these ports to the BlockScout application server's IP address if setting up BlockScout (find in the details section of your created instance) or to your local network. You can also set limit port connections later through the EC2 -> Security Groups panel.
Specify the private key ( .pem
) file, the user name for your AMI, and the public DNS name for your instance. For example, if you used Amazon Linux 2 or the Amazon Linux AMI, the user name is ec2-user
. If ubuntu, the user name is ubuntu
.
Example: ssh -i /path/my-key-pair.pem ec2-user@ec2-198-51-100-1.compute-1.amazonaws.com
Install OpenEthereum from for the corresponding platform
Create a config file called node.toml (see below for config file specs including ) and edit accordingly vim node.toml
Connect and Sync an archive node using the config file. parity --config node.toml
Find your EC2 url to connect with BlockScout: Go to EC2 Dashboard -> Instances -> corresponding archive node instance and record the ip address. When configuring BlockScout you will use this address along with port 8545 to connect via the EthereumJsonRPCHttpURL parameter.
For example: 192.0.2.1:8545
Additional Resources
.
Below we provide a general example file as well as the settings we use for our xDai node config. In general:
Parity should run in "fatdb+archive+traces" mode with pruning="archive"
, fatdb="on"
, tracing="on"
.
Both RPC and WebSockets interfaces should be opened and allow calls to "web3","eth","net","parity","pubsub","traces"
APIs.
These are the settings we use to run the xDai archive node.
A full list of configuration options is available at:
The following example file outlines general parameters - Performance-related parameters like processing_threads
, server_threads
or cache_size_db
will vary based on the chain size, available hardware, parity version, general traffic load etc. Often these are adjusted through a trial-and-error process.
This instruction was moved from: