Why the error occurs

Flexera Ocean validates that every instance type defined in a VNG also appears in the cluster-level instance type whitelist. If the cluster does not include a type you’re trying to add to a VNG—or if you remove a required type at the cluster level—you’ll see this error.

Common scenarios

Scenario 1: Adding a new instance type to a custom VNG

• Cluster-level whitelist: Only c5.xlarge

• What you're trying to do: Add c5.2xlarge to a custom VNG

• Why it fails: c5.2xlarge isn’t part of the cluster-level whitelist

• How to fix it:

  1. Add c5.2xlarge at the cluster level

  2. Update the cluster

  3. Add c5.2xlarge to the custom VNG

Scenario 2: Replacing an instance type in a custom VNG

• Cluster-level whitelist: m5.xlarge, m5.4xlarge

• Custom VNG whitelist: Same as cluster

• What you're trying to do: Remove m5.4xlarge and replace it with c5.4xlarge

• Why it fails: c5.4xlarge doesn’t exist at the cluster level

• How to fix it:

  1. Add c5.4xlarge at the cluster level

  2. Update the cluster

  3. Add c5.4xlarge to the custom VNG

  4. Remove m5.4xlarge if needed

Best practice

If you’re not using the cluster-level/default VNG, it’s easier to leave the cluster-level whitelist undefined. When you don’t specify a cluster-level whitelist, all instance types are available, giving you more flexibility when defining VNG-specific whitelists.