8.11 Displaying the AWS Nitro System Based Cloud Instance Sizes That AWS Recently Supported in the AWS Cloud Instance Sizes list

For each release, PlateSpin Migrate adds support for new cloud instances and instance families that AWS has released up to a stipulated date prior to the PlateSpin Migrate release. After that date, any new AWS instances are not available by default in the Cloud Instance Size list option when you configure migration to AWS.

The AWS Cloud Instance Size list displays only instances that are defined in the AWS-Instances.ini file in the following package found on the PlateSpin Server:

<install-drive>:\Program Files\PlateSpin Migrate Server\Packages\B9059B80-55E4-4B9C-B85B-EFEFC85EAAE2\1.package\

You can add definitions to this file for new AWS Nitro Based instances and instance families to make the instances available in the AWS Cloud Instance Sizes list when you configure workloads for migration to AWS.

  1. Log in to the PlateSpin Migrate Server host machine as the Administrator user.

  2. Navigate to the PlateSpin Migrate installation directory, such as C:\Program Files\PlateSpin Migrate Server\.

  3. Open the .\Packages\B9059B80-55E4-4B9C-B85B-EFEFC85EAAE2\ folder and copy the 1.package file out of this folder to a temporary directory.

  4. Rename 1.package with the .zip file extension (1.zip), then extract the contents of the file to the temporary directory.

  5. Edit the file named AWS-Instances.ini to add an entry for the new instance or instance family that you want to support by using one of the following applicable formats:

    • If the instance or the instance family supports both NVMe EBS volumes and enhanced networking: 

      [Instance name or Instance family name]
      Device.Storage = nvme
      Device.Network = ena

    • If the instance or the instance family supports only enhanced networking: 

      [Instance name or Instance family name]
      Device.Network = ena

    NOTE:If the network and storage capabilities of an instance is not the same as that of the family it belongs to, you must have a separate entry for the instance and the support details listed within this entry takes precedence for the instance instead of its instance family entry.

  6. Repackage the modified file as 1.package.