Mainnet/Testnet: Running Nodes using AWS 1-click Deployment

This tutorial will use our AWS 1-click Deployment image to start and create the latest Cronos POS Chain 1-Click Node for both Mainnet and Testnet

CAUTION We do not recommend directly running validator on Mainnet by 1-Click deployment. Please use it with caution! Because the 1-click deployment is not running with TMKMS and your tendermint validator key is in plain text /chain/.chain-maind/config/priv_validator_key.json. You may consider running validator with tmkms on AWS nitro-enclave.

Step 1. AWS Account Creation

You will first need to create an AWS account. This will require providing your credit card information to AWS and you may be subject to getting charged when you create a virtual machine. More details on account creation, check this link.

Please read AWS free trial page to see if you are eligible for the free-tier.

Step 2. Common Setup

Step 2-0. Go to EC2 page and change the region

Sign in to your AWS account and go to EC2 Dashboard and change to your favourite region. Click "Launch Instance"

Step 2-1. Search for Cronos POS Chain 1-Click Node on AWS Marketplace

Search for "Cronos POS Chain 1-Click Node" in Choose an Amazon Machine Image (AMI) section. Select "Cronos POS Chain 1-Click Node" from the search results.

Step 2-2. Choose an instance type

By default, it will choose the recommended instance type (m5a.large) for you. But you can choose another instance type based on Mainnet/Testnet requirements.

Step 2-3. Configure instance details

Configuration
Value

Network

Select an existing one or default vpc if you don't have any

Subnet

Choose a subnet or default subnet if you don't have any

Auto-assign Public IP

Enable

Other fields

Follow default setting

Step 2-4. Add Storage

  • Follow the default setting with 125 Throughput (MB/s)

Step 2-5. Add Tags

  • Create Tag if needed

Step 2-6. Configure Security Group

By default, the image creates a new security group for you allowing ssh, p2p, rpc, and rest ports. You can remove the default opened rules or add more rules for example: grpc(9090), node_exporter(9100), prometheus (26660), etc.

Default Port
Description

22

ssh

26656

p2p

26657

rpc

1317

rest

You should consider updating your security group rules to allow access from known IP addresses only.

Step 2-7. Review Instance Launch

Click "Launch" once you finish the review

You can either create a new key pair or import a key pair. Follow this instruction.

Step 2-8. Connect to your instance

Once the deployment is completed, you can connect to your instance via SSH.

AfterwardAfterwards, go to the chain directory, and you will find all the essential binaries for setting up your node:

Step 3. Running a full node

Step 3-1. Use the reconfiguration script

Now we use the reconfiguration script reconfig.sh to choose the existing networks to join.

(Optional) You may also enable STATE-SYNC. Your node will download data related to the head or near the head of the chain and verify the data. This leads to drastically shorter times for joining a network for validator. For validator, It will be amazingly fast to sync the near head of the chain and join the network.

CAUTION Blocks before state-sync trust height will NOT be queryable. If you want to run a full node or a validator with complete blockchain data; It is not suggested to use state-sync.

Clean up the old blockchain data (if any)

The consensus public key information could be found in /chain/.chain-maind/config/priv_validator_key.json

Backup your old /chain/.chain-maind/config/priv_validator_key.json if you ever created.

The script will also ask you to fill in the moniker value which is a human-readable display name for tendermint p2p. p2p gossip will allow you to connect with more nodes (data sources).

node_id and node_key are the unique identity of your node. Save them for later use.

chain-maind is now running in the background as a systemd service.

You can check its log by the command journalctl, for example:

The consensus public key can be found by and please take note of it for the next steps:

The latest block height can be found by:

Mainnet

Testnet

Once the tendermint syncs to the latest block, the setup is done! You may move on to the next step if you want to join the network as a validator.

Step 4. Join as a validator

We suggest that you should do this process locally with chain-maind to avoid exposing your keys on a cloud server. If you haven't installed chain-maind yet, please follow Step 1. Get the Cronos POS Chain binary for testnet or Step 1. Get the Cronos POS Chain Mainnet binary for mainnet.

NOTE

  • Check whether your chain-maind is mainnet or testnet binary

Mainnet

  • Mainnet binary for Mac and Windows are also available.

Or

Testnet

Mainnet

Create a new key and address

Please follow Step 3-1. Create a new key and address

Creating a validator node

You should obtain a consensus public key from Step 3-1. Use the reconfiguration script

Please follow Step 3-5. Joining the network as a validator to create a validator.

Check if the validator has been set

Back your server, and follow Step 3-6. Check your validator status

🎊 Congratulations! You've successfully joined the network as a validator! 🎊

Testnet

Create a new key and address

Please follow Step 3-1. Create a new key and address

Creating a validator node

You should obtain a consensus public key from Step 3-1. Use the reconfiguration script

Please follow Step 3-2 Joining the network as a validator to create a validator.

Check if the validator has been set

Back your server, and follow Step 3-6. Check your validator status

🎊 Congratulations! You've successfully joined the network as a validator! 🎊

PreviousCroeseid Testnet: Running NodesNextMainnet/Testnet: Running Nodes using Azure 1-click Deployment

Last updated