You may not be able to add Arm64 instance types to a custom virtual node group. This usually happens when the AMI doesn’t support Arm64 or when the cluster has a whitelist or blacklist that excludes these instance types. This article explains why this happens and how to fix it.
- Check if the AMI supports Arm64.
- If the virtual node group's AMI doesn’t support Arm64, you won’t be able to select Arm64 instance types.
- Add an AMI that supports Arm64 to the virtual node group.
- After updating the AMI, select the Arm64 instance types in the virtual node group settings.
- Check the cluster configuration for a whitelist or blacklist.
- If the cluster uses a whitelist, make sure Arm64 instance types are included.
- If the cluster uses a blacklist, remove the Arm64 instance types from the blacklist.
- After updating the cluster configuration, add the required Arm64 instance types to the virtual node group.

After updating the AMI or adjusting the whitelist/blacklist in the cluster configuration, you can add Arm64 instance types to the virtual node group.
AWS provides specific documentation that explains how to determine whether an AMI supports Arm64. The key reference is the AWS EC2 User Guide section on AMI architecture, which states that each AMI defines the architectures it supports, such as arm64 or x86_64.
Here are the most helpful AWS sources:
Was this helpful?
Related Articles
Fix “virtual node group’s architecture doesn’t match the template filter” in ECS 2Number of Views Manually launch an instance using a specific launch specification or virtual node group 3Number of Views Why custom parameters in virtual node groups show as null 2Number of Views Set a maximum capacity per virtual node group using eksctl 4Number of Views Reasons on‑demand nodes can run in Ocean AKS virtual node groups 5Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Revenera Assistant
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago