How Do I Do If I Can't Bind an Enhanced Datasource Connection to a Queue?

Symptom

An enhanced datasource connection failed to pass the network connectivity test. Datasource connection cannot be bound to a queue. The following error information is displayed:

Failed to get subnet 86ddcf50-233a-449d-9811-cfef2f603213. Response code : 404, message : {"code":"VPC.0202","message":"Query resource by id 86ddcf50-233a-449d-9811-cfef2f603213 fail.the subnet could not be found."}

Cause Analysis

VPC Administrator permissions are required to use the VPC, subnet, route, VPC peering connection, and port for DLI datasource connections.

The binding fails because the user does not have the required VPC permissions.

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.