Register an EKS Cluster

Running GoFabric on AWS EKS: 1. Prepare an EKS cluster → 2. Register an EKS cluster → 3. Deploy on Kubernetes

This guide registers your EKS cluster as an Infra in GoInfra. Once registered, the Infra replaces virtual machines: you select it when creating organizations and components, and GoChain deploys them as pods in your cluster. There is no VM provisioning step.

GoChain connects to the cluster's API server with the ServiceAccount token you created in step 1. Access is granted with Kubernetes RBAC inside your cluster; nothing is created in AWS IAM.

â„šī¸ Note: AWS EKS is available for GoFabric organizations. GoBesu networks run on virtual machines from AWS, GCP, Azure or an external provider.

Before You Start

Complete 1. Prepare an EKS cluster. Its last step lists the values this form asks for: region, ServiceAccount token, cluster name, cluster endpoint, target DNS name and CA certificate.

Creating the Infra

Step 1: Navigate to GoInfra

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

Accessing GoInfra Figure 1: Accessing GoInfra from the App Menu

Step 2: Select the AWS EKS Provider

In the infrastructure creation screen, select AWS EKS.

Step 3: Provide the Cluster Details

Infra Details

  • Name (required): A name for your infrastructure (e.g., "K8s Production Cluster").
  • Region (required): The AWS region of your EKS cluster.

Cluster Access

  • Service Account Token (required): The bearer token GoChain presents to your cluster's API server.

Infra Details and Cluster Access Figure 2: Infra Details and Cluster Access

âš ī¸ Use a long-lived token. Since Kubernetes 1.24, kubectl create token issues a token that expires, and GoChain does not renew it. Read the token from an explicit kubernetes.io/service-account-token Secret instead, as shown in step 1. The same Secret also holds the cluster's CA certificate.

EKS Cluster Configuration

  • Cluster Name (required): The name of your EKS cluster as defined in AWS.
  • Cluster Endpoint (required): The Kubernetes API server endpoint URL (e.g., https://XXXXX.eks.region.amazonaws.com).
  • Target DNS Name (required): The wildcard DNS name used to expose Fabric components deployed in the cluster (e.g., *.k8s.example.com). GoFabric generates subdomains under this domain for each component. The wildcard record must already point to your cluster's load balancer or ingress. It cannot be changed after creation.
  • CA Certificate (Base64) (required): The cluster's CA certificate, Base64-encoded.

EKS Cluster Configuration Figure 3: EKS Cluster Configuration

Advanced Configuration (optional)

These cluster settings can also be changed later on the Infra's page, but a change only reaches containers created or redeployed afterwards, so set them before creating organizations:

  • Ingress class: The class of the components' ingresses. Empty uses nginx.
  • CPU limit and Memory limit: Limits for containers whose resource and organization set none (e.g., 1 and 1Gi). Empty means no limit.
  • Restricted security profile: Runs containers as non-root with a read-only filesystem, for clusters that enforce the restricted Pod Security Standard.
  • Omit the TLS block on passthrough ingresses: For ingress controllers that fail a passthrough route whose TLS secret does not exist, such as Traefik's ingress-nginx compatibility provider. ingress-nginx does not need it.
  • Skip Prometheus and Grafana: Leaves Prometheus and Grafana out of this Infra's organizations.

Advanced Configuration Figure 4: Advanced Configuration (cluster settings)

Step 4: Create the Infrastructure

Click on the Create Infra button to create your infrastructure.

â„šī¸ Note: Unlike VM-based deployments, there is no "Set Up Virtual Machines" step after creating a Kubernetes infrastructure. The cluster handles all compute resources automatically.

Managing the Infra

Open the Infra from the GoInfra overview:

  • The Infra tab shows the connection (provider, region, cluster name, API endpoint and target DNS) and the current cluster settings.
  • The Settings tab has the Cluster settings card: edit the advanced configuration above and click Save cluster settings. Changes apply to containers created or redeployed afterwards; running containers keep what they were built with.

Rotating or revoking the token

The token does not renew itself. To replace it:

  1. Create a new token Secret in your cluster (step 1, Step 7.3).
  2. Open the Infra, go to Settings, paste the new token in Rotate ServiceAccount token (New Service Account Token) and click Replace token.

The Infra keeps its identity, so nothing needs re-registering.

To revoke GoChain's access immediately, delete the token Secret or the ServiceAccount in your cluster:

kubectl delete secret gochain-token -n <NAMESPACE>

Next Step

Your cluster is registered. Continue with 3. Deploy on Kubernetes to create organizations, peers, orderers and chaincodes in it. For general GoFabric concepts, see the GoFabric Setup Guide.