Generating Infrastructure

Last updated 2 months ago

Windows is not supported. You can only generate the infrastructure using a Unix based OS. Eg. macOS or Linux.

Make sure you have installed all the requirements on your computer and have exported the proper AWS profile:

$ export AWS_PROFILE=my-cxcloud-dev

Infra generation

The first step of setting up a CX Cloud project, is generating the infrastructure required for running services. Create a Github repository named infra in your organization. Then clone it to your project folder and start infra generation by running the following commands:

$ git clone
$ cd infra
$ cxcloud generate infra

If you have enabled Multi-Factor Authentication on your AWS account or you are assuming another role which does, you might be asked to enter your MFA token (using your Authenticator app) in this step.

CX Cloud CLI will by default set temporary AWS API keys as environment variables. However, it is also possible to run CLI with preset API keys as environment variables. This is useful for example when running AWS Vault for storing the secrets in your operating system's secure keystore. The AWS_PROFILE environment variable doesn't need to be exported in case AWS Vault is used.

The CLI tool will ask you what domain you want to set as your cluster's domain. For most cases, you can use a "gossip-based" cluster configuration in which case you don't need an actual domain for your cluster. So enter the domain using the following format:


For example, you might want to name your cluster mygreatcluster then enter the domain name mygreatcluster.k8s.local

(If you actually want to set a real domain for your cluster, you have to follow this guide to delegate your domain to AWS's Route53 service and then use it.)

After answering the questions the tool asks you, it will start bootstrapping your environment on AWS. It does the following steps automatically for you:

  1. Creates an S3 bucket for storing settings and state

  2. Generates Terraform files for creating container repositories and other required resources

  3. Generates Kubernetes config files and creates the Kubernetes cluster

  4. Waits for the Kubernetes cluster to become available

  5. Configures access controls on the Kubernetes cluster

  6. Installs Tiller, nginx-ingress and cert-manager on the cluster

  7. Setups of staging and production LetsEncrypt issuers

  8. Displays the load balancer URL

If the setup is successful, the command displays the load balancer URL which you need to use to point your domains to.

Configuring a domain for your online service

After you have generated the Kubernetes infrastructure, you would want to assign a domain to your future online service (or services)

The assumed starting state is that you have access to manage "" DNS. CX Cloud is to be configured to utilize this domain to explore its possibilities. As there might already be a site running in, the target state with CX Cloud would look like this:

  • (customer front-end)

  • (commerce service API)

  • (content service API)

  • (search service API)

  • (auth service API)

  • ("admin panel")

  • (developer portal)

We have used this assumption in our documentation and configuration examples. Most of these configurations are done with a routing manifest later and at this stage we only need to point the domain to Kubernetes load balancer like this:

  • First figure out what your Load Balancer URL is. The URL is displayed after generating the infrastructure. But you can also find it using:

kubectl get service nginx-ingress-controller -o=jsonpath='{.status.loadBalancer.ingress[0].hostname}'
  • Then you have to point your own domain name to this load balancer URL. To do this:

    • If you manage your domain using a provider that's not AWS, navigate to your domain's management panel and create an CNAME record for pointing to the load balancer URL.

    • If you manage your domain using AWS's route53 service, create an ALIAS record for in Route53 pointing to that hostname.

      • More information on how to create an ALIAS record in Route53 on AWS here

If you want all the subdomains under a certain domain or subdomain to be available to you later during service creation, you can also create a CNAME or ALIAS record for *


As a final step, commit changes to your Github repository by running the following commands:

$ git add .
$ git commit -m "initial "
$ git push