The Ocean Console UI enforces compatibility between instance types and VNG image architecture. However, using the API or Terraform modules, it is possible to enable instance types that are not compatible with the VNG image. For example, a custom VNG in an EKS cluster can be updated to include only Graviton instance types, even if the VNG image is x86_64.

There is no validation for instance type and Amazon Machine Image (AMI) compatibility in API or Terraform updates. This behavior is maintained to preserve backward compatibility. During scale-up events, the system automatically filters out invalid instance types based on the AMI architecture and other parameters.

The only potential issue occurs when a configuration includes only incompatible instance types. In such cases, after filtering, there are no valid instance types available for scaling, which prevents node launches.

Although users can make these misconfigurations through API or Terraform, scaling operations always ensure that only nodes compatible with the VNG's AMI architecture are launched.