The domain name binding feature allows you to bind your own domain name to a service, so that the service can be accessed at it.
- If you need the HTTPS protocol that supports independent domain names, you should submit the SSL certificate for your domain name by uploading it or by entering the certificate name, content, and private key.
- A modified CNAME record will take effect after a period of time. Be sure to proceed with the configuration after it takes effect; otherwise, the configuration will fail.
On the custom domain name configuration page, if the protocol is HTTPS&HTTPS or HTTPS, the forced HTTPS feature can be enabled. After it is enabled, API Gateway will redirect requests using the custom domain name over the HTTP protocol to the HTTPS protocol.
custom domain name/environment name. For example,
www.XXXXX.com/releasepoints to the release environment in the service,
www.XXXXX.com/prepubpoints to the pre-release environment in the service, and
www.XXXXX.com/testpoints to the test environment in the service.
custom domain name/custom path. This URL points to the environment that you map. For example, if the configured path is
/mypathand the environment is the release environment, the URL of the release environment will be
www.XXXXX.com/mypath. If you want to use the root path, directly configure the path as
When a custom path mapping is used, the default path mapping (
custom domain name/environment name) will not take effect.
Both the custom path mapping and default path mapping can be modified after configuration.