Deploy an Amazon EKS cluster on AWS Graviton with Rafay
Introduction
Set up Rafay and AWS access
Create an Amazon EKS cluster using a Rafay cluster manifest
Deploy NGINX to the Amazon EKS cluster and clean up
Next Steps
Deploy an Amazon EKS cluster on AWS Graviton with Rafay
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Ensure the cross-account IAM role is configured in AWS and added to Rafay as a cloud credential. In the cluster manifest, reference this credential by name. If it’s missing or has insufficient permissions, cluster creation will fail.
The project, blueprint name and version, and the cloud credential must already exist in Rafay. If any of these don’t match, the cluster won’t be created.
A running cluster with a Graviton-based (
arm64) node group will be available for workloads. Nodes should advertise the label kubernetes.io/arch=arm64, indicating they can run arm64 pods.The provided manifest pins the pods using
nodeSelector: kubernetes.io/arch: arm64. After deployment, the pod should schedule and run on nodes labeled arm64. If it remains Pending, verify the node group is active and the selector matches node labels.Delete the NGINX workload and namespace created for the test, then deprovision the EKS cluster from Rafay. This releases the associated AWS resources.