Setting up EKS Cluster in Amazon Web Services(AWS)
If you do not have a valid HiveMQ license, the HiveMQ cluster uses a trial licence that allows up to 25 concurrent client connections and is limited to testing and evaluation purposes only. To obtain a HiveMQ licence that is suitable for production use, or request an evaluation licence that allows more connections, contact our customer service team. |
While creating this guide, our Kubernetes Version is v1.27.9, it might be different in your case
Requirements
Kubectl, Helm and MQTT CLI Prerequisite - Software Packages
Amazon Account
HiveMQ License (optional)
Install Amazon CLI
The AWS Command Line Interface is an open-source tool that enables you to interact with AWS services using commands in your command-line shell.
To install the AWS CLI on macOS with Homebrew, open a terminal and enter the following. For other operating systems, see AWS CLI installation.brew install awscli
Verify AWS CLI Installation: Open a new terminal or command prompt and run the following command. This should display the installed AWS CLI version.(For us , its aws-cli/2.15.17 Python/3.11.7 Darwin/23.3.0 source/arm64 prompt/off)
aws --version
Configure AWS CLI: After installing the AWS CLI, do the following steps to configure it. (For more information, see Configure the AWS CLI in the AWS Command Line Interface User Guide.)
If you do not have existing access keys, please use the steps here to create new access key and note it or download the csv file.
Run the following command
aws configure
Optionally, you can configure a named profile, such as
--profile cluster-admin
. If you configure a named profile in the AWS CLI, you must always pass this flag in subsequent commands. E.g.aws configure --profile cluster-admin
This command will prompt you to enter the following information:
AWS Access Key ID: Enter your AWS access key.
AWS Secret Access Key: Enter your AWS secret key.
Default region name: Enter the AWS region you want to use (e.g.,
us-west-1
).Default output format: You can leave this as
json
.
For example:
EKS CLI (
eksctl
)eksctl
is a command line tool for working with EKS clusters that automates many individual tasks. To install the AWS CLI on macOS with Homebrew, open a terminal and enter the following. For other operating systems, see the installation ineksctl
documentation.
Set Up Your Kubernetes Cluster With Elastic Kubernetes Service (EKS)
Create a New IAM User
Run the following command to create a new IAM user:
Attach AdministratorAccess Policy
Run the following command to attach the AdministratorAccess policy to the newly created user:
Create Access Key
Run the following command to create an access key for the user:
Following is the output displayed after the successful creation of the access key, Please copy and save
AccessKeyId
andSecretAccessKey
values for the next steps.Run the following command:
Optionally, you can configure a named profile, such as
--profile cluster-admin
. If you configure a named profile in the AWS CLI, you must always pass this flag in subsequent commands.
This command will prompt you to enter the following information:
AWS Access Key ID: Enter your AWS access key.
AWS Secret Access Key: Enter your AWS secret key.
Default region name: Enter the AWS region you want to use (e.g.,
us-west-1
).Default output format: You can leave this as
json
.
For example:
Create EKS Cluster
In case of errors in the following command “request send failed, Post "https://sts.eu-east-1.amazonaws.com/", please try changing some other region e.g. eu-west-1
To create an EKS cluster with all the necessary resources for your cluster, enter the following command with the desired location (in this procedure, we use
eu-west-1
) and instance typec5.2xlarge (8 CPUs, 16 GiB RAM)
, enter the following command and wait until the process completes. Processing time take up to ~5 minutes and can vary:
Above command will also create IAM role and required permissions for eksctl.
Your AWS account bills you for all resources you create. |
Manage the cluster
To manage the resulting Kubernetes cluster with kubectl, download the access credentials of the cluster: (region eu-west-1 in our case, please replace it with your region)
To verify that all three nodes are available, enter:
The output from the command is similar to the following: (k8s v1.27.9 in our case, it might be different for you)
Delete Cluster
If you do not need your cluster anymore, please use the following commands to delete the cluster.
List all services running in your cluster.
Delete any services that have an associated
EXTERNAL-IP
value. These services are fronted by an Elastic Load Balancing load balancer, and you must delete them in Kubernetes to allow the load balancer and associated resources to be properly released.Delete the load balancer from AWS console.
Delete the cluster and its associated nodes with the following command,