One “registry manager” role with the EC2 use case and the new policy from Step 3 attached
2.
One “cluster manager” role created with the EKS - Cluster use case and AmazonEKSClusterPolicy
After this role is created, click on its name, then Attach Policy and select AmazonEKSServicePolicy
3.
One “worker node” role with the EC2 use case and these policies:
AmazonEKSWorkerNodePolicy
AmazonEC2ContainerRegistryReadOnly
AmazonEKS_CNI_POLICY
5.
Create an EC2 instance provisioned with the Plotly AMI according to Installation on Amazon Web Services (This instance will act as the Replicated Management Node), with these Instance Details changed from the default:
1.
Set the Network to the VPC from Step 1 and select a Subnet from that VPC
2.
Set Auto-assign public IP to Disable
3.
Set the IAM role to the “registry manager” EC2 service account from Step 4a
4.
Select an existing security group and assign the group you created in Step 2
Depending on your network, you may need to assign additional security groups; please consult your cloud infrastructure administrator if unsure
6.
SSH into your EC2 instance and:
1.
Install Python 3
2.
Install aws-cli v2 (guide) and configure it with at least your AWS Access Key IS and AWS Secret Access Key (guide)
Cluster Service Role: the “cluster manager” IAM Role created in Step 4b
3.
VPC: the VPC you created in Step 1
4.
Security groups: all groups suggested by the wizard
5.
Cluster endpoint access: private
12.
Click on the cluster name, then click the Cluster security group (under the Networking tab) and add an Inbound rule allowing traffic on port 443 from your EC2 instance’s subnet
13.
From your EC2 instance’s command line, add your new cluster’s configuration to your kubeconfig (guide)
Node IAM Role Name: the “worker node” IAM Role created in Step 4c
3.
Allow remote access to nodes from selected security groups and choose the group you created in Step 2
4.
Disk size: 200 GiB
5.
At least 4 nodes
15.
From your EC2 instance’s command line, add the Roles you created in Step 4 to the cluster configmap (guide) with the below example 1. Replace WORKER_NODE_ROLE_ARN with the ARN of the role you created in Step 4c 2. Replace REGISTRY_MANAGER_ROLE_ARN with the ARN of the role you created in Step 4a 3. You can retrieve each role’s ARN by visiting its Summary page in the IAM Management Console
1
apiVersion: v1
2
kind: ConfigMap
3
metadata:
4
name: aws-auth
5
namespace: kube-system
6
data:
7
mapRoles: |
8
- rolearn: WORKER_NODE_ROLE_ARN
9
username: system:node:{{EC2PrivateDNSName}}
10
groups:
11
- system:bootstrappers
12
- system:nodes
13
- rolearn: REGISTRY_MANAGER_ROLE_ARN
14
username: kubectl-access-user
15
groups:
16
- system:masters
Copied!
16.
Create an Elastic Container Registry repository (guide) to contain the images for your Dash apps