--- title: Creating a cluster with multi-architecture compute machines on AWS --- # Creating a cluster with multi-architecture compute machines on AWS {#creating-multi-arch-compute-nodes-aws} To deploy a cluster on Amazon Web Services (AWS) with multi-architecture compute machines, you must first create a single-architecture installer-provisioned cluster that uses the multi-architecture installer binary. You can also migrate your current cluster with single-architecture compute machines to a cluster with multi-architecture compute machines. After creating a multi-architecture cluster, you can add nodes with different architectures to the cluster. ## Adding a multi-architecture compute machine set to your AWS cluster {#multi-architecture-modify-machine-set-aws_creating-multi-arch-compute-nodes-aws} After creating a multi-architecture cluster, you can add nodes with different architectures. You can add multi-architecture compute machines to a multi-architecture cluster in the following ways: - Adding 64-bit x86 compute machines to a cluster that uses 64-bit ARM control plane machines and already includes 64-bit ARM compute machines. In this case, 64-bit x86 is considered the secondary architecture. - Adding 64-bit ARM compute machines to a cluster that uses 64-bit x86 control plane machines and already includes 64-bit x86 compute machines. In this case, 64-bit ARM is considered the secondary architecture. > [!NOTE] > Before adding a secondary architecture node to your cluster, it is recommended to install the Multiarch Tuning Operator, and deploy a `ClusterPodPlacementConfig` custom resource. For more information, see "Managing workloads on multi-architecture clusters by using the Multiarch Tuning Operator". **Prerequisites** - You installed the OpenShift CLI (`oc`). - You used the installation program to create a 64-bit ARM or 64-bit x86 single-architecture cluster with the multi-architecture installer binary. **Procedure** 1. Log in to the OpenShift CLI (`oc`). 2. Create a YAML file and add the configuration to create a compute machine set to control the 64-bit ARM or 64-bit x86 compute nodes in your cluster. ```yaml {title="Example MachineSet object for an AWS 64-bit ARM or x86 compute node"} apiVersion: machine.openshift.io/v1beta1 kind: MachineSet metadata: labels: machine.openshift.io/cluster-api-cluster: name: -aws-machine-set-0 namespace: openshift-machine-api spec: replicas: 1 selector: matchLabels: machine.openshift.io/cluster-api-cluster: machine.openshift.io/cluster-api-machineset: -- template: metadata: labels: machine.openshift.io/cluster-api-cluster: machine.openshift.io/cluster-api-machine-role: machine.openshift.io/cluster-api-machine-type: machine.openshift.io/cluster-api-machineset: -- spec: metadata: labels: node-role.kubernetes.io/: "" providerSpec: value: ami: id: ami-02a574449d4f4d280 apiVersion: awsproviderconfig.openshift.io/v1beta1 blockDevices: - ebs: iops: 0 volumeSize: 120 volumeType: gp2 credentialsSecret: name: aws-cloud-credentials deviceIndex: 0 iamInstanceProfile: id: -worker-profile instanceType: m6g.xlarge kind: AWSMachineProviderConfig placement: availabilityZone: us-east-1a region: securityGroups: - filters: - name: tag:Name values: - -node subnet: filters: - name: tag:Name values: - -subnet-private- tags: - name: kubernetes.io/cluster/ value: owned - name: value: userDataSecret: name: worker-user-data ``` where: `` : Specifies the infrastructure ID that is based on the cluster ID that you set when you provisioned the cluster. If you have the OpenShift CLI (`oc`) installed, you can obtain the infrastructure ID by running the following command: ```terminal $ oc get -o jsonpath="{.status.infrastructureName}{'\n'}" infrastructure cluster ``` `-` : Specifies the infrastructure ID, role node label, and zone. `` : Specifies the role node label to add. `ami.id` : Specifies a Red Hat Enterprise Linux CoreOS (RHCOS) Amazon Machine Image (AMI) for your AWS region for the nodes. The RHCOS AMI must be compatible with the machine architecture. ```terminal $ oc get configmap/coreos-bootimages \ -n openshift-machine-config-operator \ -o jsonpath='{.data.stream}' | jq \ -r '.architectures..images.aws.regions."".image' ``` `instanceType` : Specifies a machine type that aligns with the CPU architecture of the chosen AMI. For more information, see "Tested instance types for AWS 64-bit ARM". `availabilityZone` : Specifies the zone. For example, `us-east-1a`. Ensure that the zone you select has machines with the required architecture. `region` : Specifies the region. For example, `us-east-1`. Ensure that the zone you select has machines with the required architecture. 3. Create the compute machine set by running the following command: ```terminal $ oc create -f ``` - Replace `` with the name of the YAML file with compute machine set configuration. For example: `aws-arm64-machine-set-0.yaml`, or `aws-amd64-machine-set-0.yaml`. **Verification** 1. Verify that the new machines are running by running the following command: ```terminal $ oc get machineset -n openshift-machine-api ``` The output must include the machine set that you created. ```terminal {title="Example output"} NAME DESIRED CURRENT READY AVAILABLE AGE -aws-machine-set-0 2 2 2 2 10m ``` 2. You can check if the nodes are ready and schedulable by running the following command: ```terminal $ oc get nodes ``` **Additional resources** {._additional-resources} - [Installing a cluster on AWS with customizations](/openshift-docs-markdown/installing/installing_aws/ipi/installing-aws-customizations#installing-aws-customizations) - [Migrating to a cluster with multi-architecture compute machines](/openshift-docs-markdown/updating/updating_a_cluster/migrating-to-multi-payload#migrating-to-multi-payload) - [Tested instance types for AWS 64-bit ARM](/openshift-docs-markdown/installing/installing_aws/ipi/installing-aws-customizations#installation-aws-arm-tested-machine-types_installing-aws-customizations) - [Managing workloads on multi-architecture clusters by using the Multiarch Tuning Operator](/openshift-docs-markdown/post_installation_configuration/configuring-multi-arch-compute-machines/multiarch-tuning-operator#multiarch-tuning-operator)