Page Comparison

...

The following tools are required to complete the integration setup:

• kubectl

• eksctl

• AWS CLI

• Helm

EKS Nodegroup IAM

By default, the EKS node group should have the following AWS-managed IAM roles attached:

• AmazonEC2ContainerRegistryReadOnly → This allows read-only access to Amazon EC2 Container Registry repositories

• AmazonEKS_CNI_Policy → This provides the Amazon VPC CNI Add-on permissions it requires to modify the IP address configuration on your EKS worker nodes

• AmazonEKSWorkerNodePolicy → This allows Amazon EKS worker nodes to connect to Amazon EKS Clusters

• AmazonSSMManagedInstanceCore → This is to enable AWS Systems Manager service core functionality

AWS IAM Authenticator

Apply the following changes to the EKS cluster’s aws-auth ConfigMap to ensure the dynamic X-Compute EKS nodes can join the cluster:

1. Edit the aws-auth ConfigMap in the kube-system namespace:

   Code Block
   language bash
   kubectl edit configmap aws-auth -n kube-system

2. Insert the following groups into the mapRoles section and replace the role ARN values with the outputs generated at this prerequisite step.

   Code Block
   language yaml
   - groups: - system:masters rolearn: <Insert the Role ARN of your Worker IAM Role> username: admin - groups: - system:masters rolearn: <Insert the Role ARN of your Controller IAM Role> username: admin

Amazon VPC CNI

Infrastructure Optimizer supports the Amazon VPC CNI pluginv1.18.2-eksbuild.1 or newer.

...

Amazon VPC CNI Plugin With IRSA

...