Amazon EKS Create and Delete Cluster: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 20: Line 20:
Also write down VpcId, SecurityGroups, SubnetId  
Also write down VpcId, SecurityGroups, SubnetId  


Create the cluster. From the Console → EKS → Create Cluster
* Cluster Service Role
* VPC
* Subnets (all existing are preselected)
* Security groups: use Control Plane Security Group.


* Create the cluster. From the Console → EKS → Create Cluster:
** Cluster Service Role
** Next
** VPC
** Subnets (all existing are preselected)
** Security groups: use Control Plane Security Group.
** Custer Endpoint Access
** Custer Endpoint Access


Revision as of 23:00, 3 September 2020

External

Internal

Creation Procedure

Create a dedicated IAM role following the procedure described here. Use the "EKS - Cluster" use case.

Edit the role trust relationship and ensure that the IAM user used to create the cluster (arn:aws:iam::999999999999:user/some.user) has sts:AssumeRole for the IAM role. This is how to enable an IAM User to assume an IAM Role.

Create a dedicated VPC and associated resources using the pre-defined CloudFormation stack as described here: https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html.

  • Use "public and private subnets" option.
  • Do not specify an IAM role.

Write down the name of the stack, as it may be needed to delete the resources.

Also write down VpcId, SecurityGroups, SubnetId

Create the cluster. From the Console → EKS → Create Cluster

  • Cluster Service Role
  • VPC
  • Subnets (all existing are preselected)
  • Security groups: use Control Plane Security Group.
    • Custer Endpoint Access

Deletion Procedure

Delete the cluster.

Remove the associated resources by running Delete on the CloudFormation stack used to create resources.

Retrieved from "https://kb.novaordis.com/index.php?title=Amazon_EKS_Create_and_Delete_Cluster&oldid=68518"