Access Amazon IoT SiteWise through an interface VPC endpoint
When you create an interface endpoint, we generate endpoint-specific DNS hostnames that you can use to communicate with Amazon IoT SiteWise. The private DNS option is enabled by default. For more information, see Using private hosted zones in the Amazon VPC User Guide.
If you enable private DNS for the endpoint, you can make API requests to Amazon IoT SiteWise through one of the following VPC endpoints.
-
For the data plane API operations, use the following endpoint:
data.iotsitewise.cn-north-1.amazonaws.com.cn
-
For the control plane API operations, use the following endpoint:
data.iotsitewise.cn-north-1.amazonaws.com.cn
If you disable private DNS for the endpoint, you must do the following to access Amazon IoT SiteWise through the endpoint:
-
Specify the VPC endpoint url in API requests.
-
For the data plane API operations, use the following endpoint url. Replace
vpc-endpoint-id
with your VPC endpoint ID.vpc-endpoint-id
.data.iotsitewise.cn-north-1.vpce.amazonaws.com.cn -
For the control plane API operations, use the following endpoint url. Replace
vpc-endpoint-id
with your VPC endpoint ID.vpc-endpoint-id
.api.iotsitewise.cn-north-1.vpce.amazonaws.com.cn
-
-
Disable host prefix injection. The Amazon CLI and Amazon SDKs prepend the service endpoint with various host prefixes when you call each API operation. This feature causes the Amazon CLI and Amazon SDKs to produce URLs that are not valid for Amazon IoT SiteWise when you specify a VPC endpoint.
Important
You can't disable host prefix injection in the Amazon CLI or the Amazon Tools for PowerShell. This means that if you disable private DNS, then you can't use these tools to access Amazon IoT SiteWise through the VPC endpoint. Enable private DNS to use the Amazon CLI or the Amazon Tools for PowerShell to access Amazon IoT SiteWise through the endpoint.
For more information about how to disable host prefix injection in the Amazon SDKs, see the following documentation sections for each SDK:
For more information, see Access an Amazon service using an interface VPC endpoint in the Amazon PrivateLink Guide.