Here is an example (this was when I tried a `p3.8xlarge`, and I set the Availability Zone = Auto for the cluster)
```In zone us-east-1c, insufficient capacity for the following node type: p3.8xlarge. AWS Error: Failure happened when talking to AWS, AWS API error code: Unsupported AWS error message: Your requested instance type (p3.8xlarge) is not supported in your requested Availability Zone (us-east-1c). Please retry your request by not specifying an Availability Zone or choosing us-east-1a, us-east-1d, us-east-1e, us-east-1f. In zone us-east-1d, insufficient capacity for the following node type: p3.8xlarge. AWS Error: Failure happened when talking to AWS, AWS API error code: Unsupported AWS error message: Your requested instance type (p3.8xlarge) is not supported in your requested Availability Zone (us-east-1d). Please retry your request by not specifying an Availability Zone or choosing us-east-1a, us-east-1e, us-east-1f.```
The odd thing is it gives that message once, and then just gives a more succinct message in the Event Log: `No zone supports both the driver instance type [p3.8xlarge] and the worker instance type [p3.8xlarge]` afterwards. And every time I try to start the cluster it continues with that message, as if it doesn't try again across the different AZ's.