How Do I Fix the "Failed to get subnet" Error When Creating a Datasource Connection in DLI?

Symptom

When you create a VPC peering connection for the datasource connection, the following error information is displayed:

Failed to get subnet 2c2bd2ed-7296-4c64-9b60-ca25b5eee8fe. Response code : 404, message : {"code":"VPC.0202","message":"Query resource by id 2c2bd2ed-7296-4c64-9b60-ca25b5eee8fe fail.the subnet could not be found."}

Cause Analysis

The VPC Administrator permission is required to use the VPC, subnet, route, VPC peering connection, and port for DLI datasource connections.

The customer's failure to grant the VPC permission resulted in an error in the DLI datasource connection, which stated that the subnet could not be found.

Procedure

1. Log in to the DLI management console. In the navigation pane on the left, choose Global Configuration > Service Authorization.
2. On the agency settings page, select required permissions.

   DLI Datasource Connections Agency Access is the permissions to access and use VPCs, subnets, routes, and VPC peering connections in datasource scenarios.

   For more information, see DLI Agency Permissions.

3. Select the permissions to be included in dli_management_agency and click Update.
   Figure 1 Updating agency permissions
   

4. After updating the agency, recreate the datasource connection and rerun the job.