Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).



When your cluster and the subnets that you reference for your cluster belong to different virtual private clouds (VPCs), the cluster terminates with a VALIDATION_ERROR_SUBNET_NOT_FROM_ONE_VPC error. You can launch clusters with Amazon EMR with the instance fleets configuration across subnets in a VPC. For more information about instance fleets, see Configure instance fleets in the Amazon EMR Management Guide.


To resolve this error, use subnets that belong to the same VPC as the cluster.

To troubleshoot the failed EMR cluster, refer to the ErrorDetail information returned from the DescribeCluster and ListClusters APIs. For more information, see Error codes with ErrorDetail information. The ErrorData array within ErrorDetail returns the following information for this error code:


For each subnet:VPC pair, the ID for the VPC that the subnet belongs to.


For each subnet:VPC pair, the ID for the subnet.


The public URL of the documentation for the error code.

Steps to complete

Perform the following steps to identify and fix the error:

  1. Review the subnet IDs that are listed in the ErrorData array and confirm that they belong to the VPC where you want to launch the EMR cluster.

  2. Modify your subnet configurations. You can use one of the following methods to find all available public and private subnets in a VPC.

    • Navigate to the Amazon VPC Console. Choose Subnets and list all of the subnets that reside within the Amazon Web Services Region for your cluster. To find only public or private subnets, apply the Auto-assign public IPv4 address filter. To find and select subnets in the VPC that your cluster uses, use the Filter by VPC option. For more information on how to create subnets, see Create a subnet in the Amazon Virtual Private Cloud User Guide.

    • Use the Amazon CLI to find all available public and private subnets in the VPC that your cluster uses. For more information, see the describe-subnets API. To create new subnets in a VPC, see the create-subnet API.

  3. Launch a new cluster with subnets from the same VPC as the cluster.