AWS Blockchain Templates
Developer Guide

Create the Ethereum Network

The Ethereum network that you specify using the template in this topic launches an AWS CloudFormation stack that creates an Amazon ECS cluster of EC2 instances for the Ethereum network. The template relies on the resources that you created earlier in Set Up Prerequisites.

When you launch the AWS CloudFormation stack using the template, it creates nested stacks for some tasks. After they are complete, you can connect to resources served by the network's Application Load Balancer through the bastion host to verify that your Ethereum network is running and accessible.

To create the Ethereum network using the AWS Blockchain Template for Ethereum

  1. Open the latest AWS Blockchain Template for Ethereum in the AWS CloudFormation console using the following quick-links for the AWS Region in which you are working:

  2. Enter values according to the following guidelines:

    • For Stack name, enter a name that is easy for you to identify. This name is used within the names of resources that the stack creates.

    • Under Ethereum Network Parameters and Private Ethereum Network Parameters, leave the default settings.

      Warning

      Use the default accounts and associated mnemonic phrase for testing purposes only. Do not send real Ether using the default set of accounts because anyone with access to the mnemonic phrase can access or steal Ether from the accounts. Instead, specify custom accounts for production purposes. The mnemonic phrase associated with the default account is outdoor father modify clever trophy abandon vital feel portion grit evolve twist.

    • Under Platform configuration, leave the default settings, which creates an Amazon ECS cluster of EC2 instances. The alternative, docker-local creates an Ethereum network using a single EC2 instance.

    • Under EC2 configuration, select options according to the following guidelines:

    • Under VPC network configuration, select options according to the following guidelines:

      • For VPC ID, select the VPC that you created earlier in Create a VPC and Subnets.

      • For Ethereum Network Subnet IDs, select the single private subnet that you created earlier in the procedure To create the VPC.

    • Under ECS cluster configuration, leave the defaults. This creates an ECS cluster of three EC2 instances.

    • Under Application Load Balancer configuration (ECS only), select options according to the following guidelines:

    • Under EthStats, select options according to the following guidelines:

      • For Deploy EthStats, leave the default setting, which is true.

      • For EthStats Connection Secret, type an arbitrary value that is at least six characters.

    • Under EthExplorer, leave the default setting for Deploy EthExplorer, which is true.

    • Under Other parameters, leave the default value for Nested Template S3 URL Prefix and make a note of it. This is where you can find nested templates.

  3. Leave all other settings to their defaults, select the acknowledgement check box, and choose Create.

    The Stack Detail page for the root stack that AWS CloudFormation launches appears.

  4. To monitor the progress of the root stack and nested stacks, choose Stacks.

  5. When all stacks show CREATE_COMPLETE for Status, you can connect to Ethereum user interfaces to verify that the network is running and accessible. When you use the ECS container platform, URLs for connecting to EthStats, EthExplorer, and EthJsonRPC through the Application Load Balancer are available on the Outputs tab of the root stack.

    Important

    You won't be able to connect directly to these URLs or SSH directly until you set up a proxy connection through the bastion host on your client computer. For more information, see Connect to EthStats and EthExplorer Using the Bastion Host.