Amazon EKS Create and Delete Cluster: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 6: | Line 6: | ||
* [[Amazon_EKS_Operations#Create_a_Cluster|Amazon EKS Operations]] | * [[Amazon_EKS_Operations#Create_a_Cluster|Amazon EKS Operations]] | ||
=Procedure= | =Creation Procedure= | ||
* [[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". | ||
| Line 19: | Line 19: | ||
** Custer Endpoint Access | ** Custer Endpoint Access | ||
= | =Deletion Procedure= | ||
* Delete the cluster. | |||
Revision as of 22:13, 3 September 2020
External
Internal
Creation Procedure
- 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 enable an IAM User to assume an IAM Role.
- Create a VPC and 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.