api_gateway: none in the networking field of the Realtime API configuration and Batch API configuration. If the API Gateway endpoint is not created, your API can still be accessed via the API load balancer; cortex get API_NAME will show the load balancer endpoint if API Gateway is disabled. API Gateway is enabled by default, and is generally recommended unless it doesn't support your use case due to limitations such as the 29 second request timeout, or if you are keeping your APIs private to your VPC. See below for common configurations. To disable API Gateway cluster-wide (thereby enforcing that all APIs cannot create API Gateway endpoints), set api_gateway: none in your cluster configuration file (before creating your cluster).api_load_balancer_scheme: internal in your cluster configuration file (before creating your cluster). This will force external traffic to go through your API Gateway endpoint, or if you disabled API Gateway for your API, it will make your API only accessible through VPC Peering. Note that if API Gateway is used, endpoints will be public regardless of api_load_balancer_scheme. See below for common configurations.localhost as the Common Name (CN). Therefore, clients will need to skip certificate verification when making HTTPS requests (e.g. curl -k). Alternatively, you can set up a custom domain, which will use ACM to provision SSL certs for your domain.localhost as the Common Name (CN). Therefore, clients will need to skip certificate verification when making HTTPS requests (e.g. curl -k). Alternatively, you can set up a custom domain, which will use ACM to provision SSL certs for your domain.