The steps to attain this
To create an Amazon Elastic Kubernetes Service (EKS) cluster utilizing CloudFormation, you may comply with these steps:
-
Create a CloudFormation template: Begin by making a CloudFormation template in YAML or JSON format. This template will outline the sources required in your EKS cluster, together with the cluster itself, employee nodes, and different obligatory elements.
-
Outline the EKS cluster useful resource: Inside your CloudFormation template, outline an AWS::EKS::Cluster useful resource. Specify the specified configuration in your EKS cluster, such because the model, identify, and role-based entry management (RBAC) configuration.
-
Outline the employee node sources: Subsequent, outline the employee node sources in your CloudFormation template. This may be accomplished utilizing AWS::AutoScaling::AutoScalingGroup and AWS::EC2::LaunchTemplate sources. Specify the specified occasion kind, AMI, and different configurations in your employee nodes.
-
Outline the required IAM roles and insurance policies: EKS requires a number of IAM roles and insurance policies for its operation. In your CloudFormation template, outline the required IAM roles and insurance policies utilizing AWS::IAM::Function and AWS::IAM::Coverage sources. These roles will grant permissions to your EKS cluster and employee nodes to work together with different AWS companies.
-
Add any further sources or configurations: Relying in your particular necessities, it’s possible you’ll want to incorporate further sources or configurations in your CloudFormation template. For instance, you would possibly wish to provision a VPC, subnets, safety teams, or configure networking settings.
-
Launch the CloudFormation stack: As soon as your CloudFormation template is prepared, you may launch a CloudFormation stack utilizing the AWS Administration Console, AWS CLI, or AWS SDKs. Present the CloudFormation template file, specify any required parameters, and provoke the stack creation course of.
-
Monitor the stack creation: CloudFormation will create and provision the required sources in response to your template. You may monitor the progress of the stack creation within the CloudFormation console or use the AWS CLI or SDKs to test the stack standing.
-
Entry your EKS cluster: After the CloudFormation stack creation is full, you may entry your EKS cluster utilizing the AWS Administration Console, AWS CLI, or Kubernetes command-line instruments (kubectl). You’ll usually want the cluster identify and applicable credentials to authenticate and work together with the cluster.
By following these steps, you may create an EKS cluster utilizing CloudFormation and outline the required sources and configurations to satisfy your particular necessities.
The code to attain this
Right here’s an instance CloudFormation template in YAML format that you should utilize to create an EKS cluster with employee nodes:
AWSTemplateFormatVersion: "2010-09-09"
Parameters:
ClusterName:
Sort: String
Description: Identify of the EKS cluster
WorkerNodeGroupName:
Sort: String
Description: Identify of the employee node group
VpcId:
Sort: AWS::EC2::VPC::Id
Description: ID of the VPC the place the cluster will likely be created
SubnetIds:
Sort: Record<AWS::EC2::Subnet::Id>
Description: Record of subnet IDs in numerous availability zones
KeyName:
Sort: AWS::EC2::KeyPair::KeyName
Description: Identify of an present EC2 key pair for SSH entry to employee nodes
Assets:
EKSCluster:
Sort: AWS::EKS::Cluster
Properties:
Identify: !Ref ClusterName
ResourcesVpcConfig:
SecurityGroupIds:
- !Ref ClusterSecurityGroup
SubnetIds: !Ref SubnetIds
ClusterSecurityGroup:
Sort: AWS::EC2::SecurityGroup
Properties:
GroupDescription: EKS cluster safety group
VpcId: !Ref VpcId
NodeInstanceProfile:
Sort: AWS::IAM::InstanceProfile
Properties:
Roles:
- !Ref NodeInstanceRole
NodeInstanceRole:
Sort: AWS::IAM::Function
Properties:
AssumeRolePolicyDocument:
Model: "2012-10-17"
Assertion:
- Impact: Permit
Principal:
Service: ec2.amazonaws.com
Motion: sts:AssumeRole
ManagedPolicyArns:
- arn:aws:iam::aws:coverage/AmazonEKSWorkerNodePolicy
- arn:aws:iam::aws:coverage/AmazonEKS_CNI_Policy
- arn:aws:iam::aws:coverage/AmazonEC2ContainerRegistryReadOnly
NodeAutoScalingGroup:
Sort: AWS::AutoScaling::AutoScalingGroup
Properties:
AutoScalingGroupName: !Ref WorkerNodeGroupName
VPCZoneIdentifier: !Ref SubnetIds
MinSize: 1
MaxSize: 3
DesiredCapacity: 2
LaunchConfigurationName: !Ref NodeLaunchConfig
Tags:
- Key: kubernetes.io/cluster/${ClusterName}
Worth: "owned"
PropagateAtLaunch: true
NodeLaunchConfig:
Sort: AWS::AutoScaling::LaunchConfiguration
Properties:
ImageId: ami-xxxxxxxxxxxxxx # Specify the suitable employee node AMI ID in your area
InstanceType: t3.medium # Specify the specified employee node occasion kind
IamInstanceProfile: !Ref NodeInstanceProfile
SecurityGroups:
- !Ref NodeSecurityGroup
KeyName: !Ref KeyName
NodeSecurityGroup:
Sort: AWS::EC2::SecurityGroup
Properties:
GroupDescription: EKS employee node safety group
VpcId: !Ref VpcId
Outputs:
ClusterName:
Description: EKS cluster identify
Worth: !Ref ClusterName
ClusterEndpoint:
Description: EKS cluster endpoint
Worth: !GetAtt EKSCluster.Endpoint
WorkerNodeGroupName:
Description: EKS employee node group identify
Worth: !Ref WorkerNodeGroupName
On this template, you may change ami-xxxxxxxxxxxxxx with the suitable AMI ID in your area and specify the specified occasion kind (t3.medium within the instance). Additionally, make certain to offer legitimate values for different parameters reminiscent of ClusterName, WorkerNodeGroupName, VpcId, SubnetIds, and KeyName.
This template will create an EKS cluster with the desired identify and VPC configuration. It’s going to additionally create a employee node group utilizing an Auto Scaling Group and launch configuration. The employee nodes will likely be related to the EKS cluster and can have the required IAM roles and safety teams.
You should utilize this CloudFormation template to create a stack utilizing the AWS Administration Console, AWS CLI, or AWS SDKs.
