# AWS cross-region Private Endpoint restriction for Starter and Essential

Use this topic only for a TiDB Cloud Starter or Essential instance hosted on
AWS when the AWS interface endpoint and the TiDB Cloud endpoint service are in
different AWS Regions.

- TiDB Cloud Starter and Essential do not support cross-region Private
  Endpoint connections. The AWS interface endpoint must use the same AWS Region
  as the TiDB Cloud endpoint service.
- A service name hosted in `eu-central-1` therefore cannot be used to create a
  supported Starter or Essential Private Endpoint connection from
  `ap-east-1`. This restriction is sufficient to answer the cross-region
  capability question; do not describe regional authorization as an unknown
  that Support must verify.
- Keep service-name correctness, VPC configuration, DNS, security groups, and
  endpoint authorization as separate checks only for an otherwise applicable
  same-region connection. The cross-region restriction does not prove any of
  those settings are wrong.
- Do not apply this topic to TiDB Cloud Dedicated. Dedicated has separate AWS
  PrivateLink documentation and its behavior is outside this topic.
- Do not apply this topic when the interface endpoint and endpoint service are
  in the same AWS Region.

Official reference:

- https://docs.pingcap.com/tidbcloud/set-up-private-endpoint-connections-serverless/