sample classic template input parameters for fw instance type mismatch whats available in the marketplace.

[PerryKuhnen]

I followed the instructions on the Palo Alto site exactly to create the vpc-classic-v1.2.1.template with 3 AZ . The template creates all the artifacts except for the firewalls. The initlambda has an error An error occurred (NoSuchKey) when calling the GetObject operation: The specified key does not exist.

[PerryKuhnen]

The NoSuchKey error can be ignored. What really happens is that if you choose an instance type from the dropdown list and that instance is not in the actual list of instance supported in the marketplace you will get an error in the autoscaling group.

Launching a new EC2 instance. Status Reason: The instance configuration for this AWS Marketplace product is not supported. Please see the AWS Marketplace site for more information about supported instance types, regions, and operating systems. Launching EC2 instance failed.

Below on the left are the input options and on the right are the values actually supported by AWS marketplace. (Based on PAYG1) from the template from market place

• m4.xlarge m4.xlarge
• m4.2xlarge m4.2xlarge
• m4.4xlarge m4.4xlarge
• m3.xlarge m3.xlarge
• m3.2xlarge m3.2xlarge - c4.xlarge not supported
• c4.2xlarge c4.2xlarge
• c4.4xlarge c4.4xlarge - c3.xlarge not supported
• c3.2xlarge c3.2xlarge
• c3.4xlarge c3.4xlarge Also the following are in the market place but not listed in the drop down c3.8xlarge c4.8xlarge

[jpeezus]

Thanks for following up with the insights from your work on the GitHub thread as well as the Live Community. As mentioned in the Live Community we will take a look at this and make any necessary changes to save anyone else grief. This definitely helps and we appreciate it. Thanks again Perry.