Infrastructure

This guide covers how to create and manage infrastructure in GoInfra. An Infra is an instance of your cloud provider that allows you to create and manage virtual machines (or Kubernetes clusters) for your blockchain organization.

Accessing GoInfra

Access GoInfra by clicking on the App Menu in the navigation bar and selecting GoInfra.

On the overview page you will see all the infrastructures you have already created. To create a new one, click the + New Infra button in the top right corner.

GoInfra Overview

Choosing a Provider

After clicking + New Infra (or navigating to Create Infra in the sidebar), you will be prompted to select a cloud provider for your infrastructure.

Choose a Provider

The available providers are:

Provider Infrastructure type Availability
External Provider User-managed VMs connected via SSH Starter and above
Amazon Web Services EC2 virtual machines managed by GoInfra Higher-tier plans
Google Cloud Platform GCP virtual machines managed by GoInfra Higher-tier plans
Microsoft Azure Azure virtual machines managed by GoInfra Higher-tier plans
AWS EKS Kubernetes cluster on Amazon Elastic Kubernetes Service Higher-tier plans
Kubernetes On-Prem Self-managed Kubernetes cluster via kubeconfig Coming soon
GoLedger Fully managed by GoLedger — no infrastructure to configure Coming soon

Select the provider that matches your setup and fill in the details below.


Creating an External Provider

The External provider lets you connect your own pre-existing machines to GoInfra using SSH. GoInfra will not provision or manage the underlying VMs — you are responsible for the machines.

Select External Provider and fill in the following:

Infra Details

  1. Name (required): A name to identify your infrastructure within GoChain.

Then click Create Infra.

Creating External Infrastructure

After the infra is created, you will be taken to the VM setup step where you can register your existing machines. See the VM Setup Guide for details.


Creating an Amazon Web Services Provider

The AWS provider lets GoInfra create and manage EC2 instances directly in your AWS account.

Select Amazon Web Services and fill in the following:

Infra Details

  1. Name (required): A name to identify your infrastructure.
  2. Region (required): The AWS region where your VMs will be created (e.g. us-east-1).
  3. Access Key (required): Your AWS IAM Access Key ID.
  4. Secret Key (required): Your AWS IAM Secret Access Key.

Security Group

  1. Security Group Name (required): The name of the AWS security group GoInfra will create. This name must not already exist in your AWS account — GoInfra will create it with the required firewall rules for the blockchain components.
  2. Security Group Description (required): A short description for the security group.

Create Private Key

  1. Key Name (required): The name of the SSH key pair GoInfra will create in your AWS account. This name must not already exist in your account.
  2. Key Description (required): A short description for the key pair.

Advanced Configuration (optional)

Expand this section to define custom ports for your instances. Make sure you have added the ports needed to deploy the network resources. Check the documentation for more information on standard ports.

Then click Create Infra.

Creating AWS Infrastructure

After the infra is created, you will be taken to the VM setup step. See the VM Setup Guide for details.


Creating a Google Cloud Platform Provider

The GCP provider lets GoInfra create and manage virtual machines in your Google Cloud project using a service account.

Select Google Cloud Platform and fill in the following:

Infra Details

  1. Name (required): A name to identify your infrastructure.
  2. Zone (required): The GCP zone where your VMs will be created (e.g. us-east1). Select from the dropdown.
  3. Json File GCP (required): Upload your GCP service account JSON key file. This file provides GoInfra with the credentials it needs to provision resources in your Google Cloud project.

VPC Network

  1. VPC Network Name (required): The name of the VPC network GoInfra will create for your infrastructure.
  2. VPC Network Description (required): A short description for the VPC network.

Create Private Key

  1. Key Name (required): The name of the SSH key GoInfra will create to access your instances.
  2. Key Description (required): A short description for the key.

Then click Create Infra.

Creating GCP Infrastructure

After the infra is created, you will be taken to the VM setup step. See the VM Setup Guide for details.


Creating a Microsoft Azure Provider

The Azure provider lets GoInfra create and manage virtual machines within your Azure subscription using an Azure Active Directory app registration.

Select Microsoft Azure and fill in the following:

Infra Details

  1. Name (required): A name to identify your infrastructure.
  2. Resource Group (required): The name of an existing Azure Resource Group where the infrastructure will be created. Make sure this Resource Group already exists in the selected location.
  3. Location (required): The Azure region for deployment. Must match the region of the Resource Group above.
  4. Client Secret (required): The client secret of your Azure Active Directory app registration.
  5. Client ID (required): The application (client) ID of your Azure AD app registration.
  6. Tenant ID (required): The directory (tenant) ID of your Azure Active Directory.
  7. Subscription ID (required): The ID of the Azure subscription where resources will be provisioned.

Virtual Network

  1. Virtual Network Name (required): The name of the Virtual Network (VNet) GoInfra will create.
  2. Virtual Network Description (required): A short description for the Virtual Network.

Create Private Key

  1. Key Name (required): The name of the SSH key GoInfra will create to access your instances.
  2. Key Description (required): A short description for the key.

Then click Create Infra.

Creating Azure Infrastructure

After the infra is created, you will be taken to the VM setup step. See the VM Setup Guide for details.


Creating an AWS EKS Provider

The AWS EKS provider lets GoInfra deploy blockchain components as pods on an existing Amazon Elastic Kubernetes Service cluster, instead of provisioning individual VMs.

âš ī¸ Warning: You must have an EKS cluster already created in your AWS account before using this provider. GoInfra will deploy resources onto the cluster but will not create the cluster itself. For more information on setting up an EKS cluster, please refer to the Cluster Setup Guide.

Select AWS EKS and fill in the following:

Infra Details

  1. Name (required): A name to identify your infrastructure.
  2. Region (required): The AWS region where your EKS cluster is located.
  3. Access Key (required): Your AWS IAM Access Key ID.
  4. Secret Key (required): Your AWS IAM Secret Access Key.

EKS Cluster Configuration

  1. Cluster Name (required): The name of your existing EKS cluster.
  2. Role ARN (required): The IAM Role ARN for EKS cluster access (e.g. arn:aws:iam::123456789012:role/EKSClusterRole). Provide this if your cluster uses an IAM role for API authentication.
  3. Cluster Endpoint (required): The HTTPS endpoint for your EKS cluster API server (e.g. https://XXXXX.eks.region.amazonaws.com).
  4. Target DNS Name (required): A wildcard DNS name used for external access to the cluster services (e.g. *.k8s.xyz.com.br). This DNS record must be previously created and pointing to your cluster's load balancer.
  5. CA Certificate (Base64) (required): The Base64-encoded CA certificate for your EKS cluster. Paste the full Base64 string.

Then click Create Infra.

Creating AWS EKS Infrastructure

â„šī¸ Note: There is no VM setup step for EKS — blockchain components are deployed directly as Kubernetes pods on your existing cluster.


GoLedger Provider

💡 Coming soon: The GoLedger-managed infrastructure provider is not yet available. With this option, GoLedger will handle all infrastructure provisioning on your behalf — no cloud credentials required. Check back later for updates.


Kubernetes On-Prem Provider

💡 Coming soon: Support for self-managed Kubernetes clusters via kubeconfig is not yet available. This provider will allow you to deploy blockchain components on your own on-premises or private cloud Kubernetes cluster.


Next Steps

With your infrastructure created, the next step depends on your provider type:

  • External, AWS, GCP, or Azure: Proceed to VM Setup to register or provision the virtual machines for your organization.
  • AWS EKS: Your infrastructure is ready. Proceed to set up your organization:
  • GoFabric Setup Guide
  • GoBesu Setup Guide