This document quickly guides you on how to access the API Gateway using a custom domain name in a cloud-native gateway. The cloud-native gateway provides access via IP address but does not offer a domain name entry point. Therefore, you need to add an A record in your domain's DNS that points to the IP address provided by the cloud-native gateway.
Overview
You need to complete the following steps sequentially:
1. Add an A record in DNS and bind it to the IP address provided by the cloud-native gateway.
2. Bind a certificate (if HTTPS is used to access the gateway).
Operation steps
Step 1: Adding an A Record in DNS to Bind the IP address Provided by the Cloud Native Gateway
2. Select the cluster grouping to access, view Access Address > Public Network CLB, and get the access IP.
3. Add an A record in DNS and bind the domain name to the public IP.
Step 2: Binding a Certificate (If HTTPS Is Used to Access the Gateway)
If you need to use HTTPS to access gateway resources, refer to the certificate management procedure to bind a certificate. Note:
If no certificate is bound, a certificate mismatch with the custom domain name occurs when you access the domain using HTTPS. For testing with the curl tool, add the -k parameter to skip server certificate verification. In a production environment, you must bind a certificate to use HTTPS.