If your goal is to generate IAM access keys for a new user, login to the AWS console, go to IAM, go to users, Add User, click 'Programmatic access', then Set permissions for the user and finish by creating the user. On the next screen will be the access keys. You need to download (or copy) the Secret access key as it will NOT be shown again. Step 1: Generate an AWS Access Key ID and Secret Access Key At the end of this step, you will have generated an AWS Access Key ID and Secret Access Key and created a local AWS profile to hold these credentials. If you already have an AWS Access Key ID and Secret Access Key and a local AWS profile, you can skip this step.

Introduction

Amazon Web Services (AWS) is a well-known provider of cloud services, while Kubernetes is quickly becoming the standard way to manage application containers in production environment. Amazon Elastic Container Service for Kubernetes (EKS) brings these two solutions together, allowing users to quickly and easily create Kubernetes clusters in the cloud.

This guide walks you, step by step, through the process of provisioning a new Kubernetes cluster using Amazon EKS and then deploying WordPress to the cluster using a Bitnami Helm chart.

Overview

This guide will introduce you to Amazon EKS by provisioning a Kubernetes cluster and deploying the Bitnami WordPress Helm chart on it. This will give you a pre-configured WordPress blog that you can start using right away. But WordPress is just an example: there are hundreds of other Bitnami applications to choose from, and they’re all equally easy to set up.

Here are the steps you’ll follow in this tutorial:

Generate an AWS Access Key ID and Secret Access Key
Create an AWS IAM service role
Generate an AWS key pair for the worker nodes
Create an AWS VPC
Create and connect to an Amazon EKS cluster
Add worker nodes to the Amazon EKS cluster
Add a storage class to the Amazon EKS cluster
Install Helm
Deploy the WordPress Helm chart
Log in and start using WordPress

The next sections will walk you through these steps in detail.

Assumptions and prerequisites

This guide assumes that:

You have an AWS account with an active subscription and are able to log in using AWS IAM account credentials. If you don’t have either of these, create a new account and then create an IAM user in your AWS account.
You have installed the latest version of aws, the AWS command-line interface (CLI), to a location in your system path. In case you haven’t, install it using these instructions.
You have installed the latest version of heptio-authenticator-aws, the Heptio Authenticator for AWS, to a location in your system path. In case you haven’t, install it using these instructions.
You have installed the latest version of kubectl, the Kubernetes command-line tool, to a location in your system path. In case you haven’t, install it using these instructions.

NOTE: You must use kubectl v1.10 or later with Amazon EKS.

IMPORTANT: At the time of writing, Amazon EKS is only available in the us-west-2 and us-east-1 regions. Therefore, before proceeding with the remainder of this guide, select one of these two regions in the AWS console and perform the operations listed below in that region alone.

Step 1: Generate an AWS Access Key ID and Secret Access Key

At the end of this step, you will have generated an AWS Access Key ID and Secret Access Key and created a local AWS profile to hold these credentials. If you already have an AWS Access Key ID and Secret Access Key and a local AWS profile, you can skip this step.

The first step is to generate an AWS Access Key ID and Secret Access Key, which will be used to authenticate your interaction with the Amazon EKS service. To do this:

Log in to the AWS IAM console using your AWS IAM account credentials.
Select the “Users” section in the left navigation bar and search for your IAM user record.
Within the user record, select the “Security credentials” tab and find the “Access keys” section.
Click the “Create access key” button.

A new key pair, consisting of an “Access Key ID” and “Secret Access Key”, will be generated and displayed. The “Secret Access Key” value will not be displayed again, so accurately down the “Access Key ID” and “Secret Access Key” values displayed.

On your local system, run the following command to create an AWS profile. Enter the AWS Access Key ID, Secret Access Key and selected region when prompted.

This will create a profile file in your home directory on your local system named ~/.aws/credentials. Typically, this file contains a default profile named default with your credentials. These credentials will be used when interacting with your Amazon EKS cluster.

Step 2: Create an AWS IAM service role

At the end of this step, you will have created an AWS IAM service role to handle operations related to your Amazon EKS cluster.

The next step is to create a service role that will interact with the Amazon EKS cluster. To do this:

Navigate to the AWS IAM console and log in (if you’re not already logged in).
Select the “Roles” section in the left navigation bar and click the “Create role” button.
Select “AWS service” as the type of entity and “EKS” as the service. Click the “Next: Permissions” button to proceed.
Click the “Next: Review” button to proceed.
Enter a name for the service role and click “Create role” to create the role. Note the name of the service role.

Step 3: Generate an AWS key pair for the worker nodes

At the end of this step, you will have generated an SSH key pair to access your EC2 instances. If you already have an SSH key pair for the AWS region you are operating in, you can skip this step.

To generate an SSH key pair, which you will need to log in to your EC2 instances, follow the steps below:

Log in to the AWS Console.
From the Amazon Web Services menu, select the EC2 service.
If required, use the region selector in the top right corner to switch to the region where your instance will be launched.
From the Amazon EC2 dashboard, select the “Key Pairs” option in the “Network & Security” menu.
Click the “Create Key Pair” button. In the resulting dialog box, enter a name for the new key pair and click the “Create” button.
A new key pair, consisting of an SSH public and private key, will be generated. You will be prompted to download the private SSH key to your computer.
NOTE: You will only be able to download the private SSH key once. Store it safely as you will not be able to log in to your AWS servers without it.

Step 4: Create an AWS VPC

At the end of this step, you will have created an AWS VPC to host your Amazon EKS cluster.

Amazon EKS also requires a Virtual Private Cloud (VPC) in which to deploy the cluster. To create this VPC:

Navigate to the AWS CloudFormation console and log in (if you’re not already logged in).
Click the “Create Stack” button.
On the “Select Template” page, select the option to “Specify an Amazon S3 template URL” and enter the URL below:
Click “Next” to proceed.
On the “Specify Details” page, enter a name for the new stack. Click “Next” to proceed.
On the “Options” page, leave all values at their defaults. Click “Next” to proceed.
On the “Review” page, review and confirm the details of the stack. Click “Create” to proceed.

Stack creation will take a few minutes. Once complete, select the stack name in the list of available stacks and select the “Outputs” section in the lower left pane. Note the identifiers of the security group, VPC and VPC subnets.

Step 5: Create and connect to an Amazon EKS cluster

At the end of this step, you will have created an Amazon EKS cluster and configured kubectl to connect to its control plane.

At this point, you are ready to create a new Amazon EKS cluster. To do this:

Navigate to the Amazon EKS console and log in (if you’re not already logged in).
Click the “Create cluster” button.
Enter details into the

Generate Access Key And Secret Key Aws