Amazon EKS Create and Delete Cluster: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 10: Line 10:
* [[AWS_Security_Operations#Create_an_IAM_Role|Create a dedicated IAM role]]. The use case should be "EKS - Cluster".
* [[AWS_Security_Operations#Create_an_IAM_Role|Create a dedicated IAM role]]. The use case should be "EKS - Cluster".
** Make sure the IAM user you are going to call into the cluster (arn:aws:iam::999999999999:user/some.user) has sts:AssumeRole for the IAM role. This is how to [[AWS_Security_Operations#Enable_an_IAM_User_to_Assume_an_IAM_Role|enable an IAM User to assume an IAM Role]].
** Make sure the IAM user you are going to call into the cluster (arn:aws:iam::999999999999:user/some.user) has sts:AssumeRole for the IAM role. This is how to [[AWS_Security_Operations#Enable_an_IAM_User_to_Assume_an_IAM_Role|enable an IAM User to assume an IAM Role]].
* Create a VPC and record VpcId, SecurityGroups, SubnetId
 
 
Create a VPC using the pre-defined CloudFormation stack as described here:
 
Record VpcId, SecurityGroups, SubnetId  
 
 
* Create the cluster. From the Console → EKS → Create Cluster:
* Create the cluster. From the Console → EKS → Create Cluster:
** Cluster Service Role
** Cluster Service Role

Revision as of 22:15, 3 September 2020

External

Internal

Creation Procedure


Create a VPC using the pre-defined CloudFormation stack as described here:

Record VpcId, SecurityGroups, SubnetId


  • 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

Deletion Procedure

  • Delete the cluster.