Hands-On with VMware Tanzu Community Edition - AWS Option

Hands-On with
VMware Tanzu Community Edition
AWS Option

(Image Credit: This Page)


In my last post, I covered in gory detail how to use the Tanzu Community Edition CLI on your Mac to create and manage a Kubernetes cluster on vSphere. Very cool and it actually works. Oh, and the nice maintainers over at VMware TCE GitHub are very responsive to issues raised.  

I had an issue assigning an Ingress IP to my cluster on vSphere as I do not run NSX, so I thought I'd try deploying to a cloud where getting an Ingress IP should be easier. For this post, I will be brief for the duplicated commands from the last post and detailed for the AWS-specific commands. I'll also switch my desktop from MacOS to Ubuntu Linux just for fun.


We will jump right into the TCE Getting Started Page. I'll skip the section up top on getting the Tanzu CLI installed on Linux (basically, install Docker, install TCE CLI).

Use TCE to Deploy Kubernetes to AWS

$ tanzu management-cluster create --ui

Click Deploy under Amazon EC2

Step 1: IaaS Provider

I'm going to use One-Time Credentials as I actually know those and then click Connect.

Step 2: VPC for AWS

I'm going to use an existing VPC to keep my AWS account uncluttered and click Next

(You can find your AWS key pair names here.)

Step 3: Management Cluster Settings

I'll use m5.large as the price is reasonable and this is my money 🙂

If you need to create an AWS VPC with private and public subnets, see this tutorial.

Fill out all fields and click Next

Step 4: Metadata


Step 5: Kubernetes Network

Take the defaults

Step 6: Identity Management

Disable for Dev

Step 7: OS Image

I always choose Ubuntu for less drama

Step 8: Register



Check and click Review Configuration

Review in Detail

Check the deets, make a copy of the CLI command and click Deploy Management Cluster. My CLI command was: "tanzu management-cluster create --file /home/dennis/.config/tanzu/tkg/clusterconfigs/jy2wqrf6b9.yaml -v 6"

Here we go...

The deployment to AWS took about 15 minutes.

Validate the Cluster

Do Something with Kubernetes on AWS

Switch Context to the Cluster

Display the Nodes

Install and Test a Package

The next steps in the documentation are to create a duplicate workload cluster. In the interest of time, and my credit card, I will skip that step and deploy a package to the management cluster.

Check Health with Octant

Type octant at a shell prompt. Still no external IP address. I need to look into this, find a solution and update the post.


Well, I still did not figure out how to get an external IP address to my Kubernetes package, but that is definitely due to my knowledge of Kubernetes not due to TCE. Back to the books for me.

Thank You

Thank you for taking the time to read this Tanzu Community Edition on AWS walk-through. I hope you have found the post educational. I welcome your comments and feedback.