To prepare your environment for deployment, you must manually configure your AWS environment settings.
Validate that the VMware Blockchain shared AMIs are visible under private images.
- Log in with the AWS console with your AWS account.
- Select the AWS region where the VMware Blockchain nodes should be created.
- Plan the topology for the VMware Blockchain network.
Skip steps 4 and 5 if you plan to use the default Amazon Virtual Private Cloud (VPC) configuration.
- (Optional) Create a VPC and corresponding subnets under that VPC.
See the AWS documentation for details, https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html.
Adhere to the following steps to avoid deployment errors:
Run all the VMware Blockchain nodes within the same VPC to avoid connectivity problems.
Subnets can belong to the same or different availability zones.
Subnets can be public or private.
Outbound connectivity to the internet is required for the installation.
- (Optional) Create Security Groups to limit connectivity to the VMware Blockchain network.
See the AWS documentation for details, https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security-groups.html.
As a best practice, adhere to the following suggestions:
All the VMware Blockchain nodes should be able to communicate with each other.
All the VMware Blockchain nodes should be able to connect to the VMware Blockchain Orchestrator. The VMware Blockchain Orchestrator appliance deploys VMware Blockchain nodes in your AWS environment.
- Create an AWS key pair in the region.
See the AWS documentation for details, https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html.
This AWS key pair is used to access the VMware Blockchain node. A generic key can be used for all VMware Blockchain nodes, or you can create unique keys per node or node type.
- Create one or more IAM users.
See the AWS documentation for details, https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html.