Skip to content

Billing Instructions for NAT Gateway and Internal Endpoint

Note

The billing instructions on this page apply to Dedicated deployments. For Dedicated Flex deployments, the services are free of charge.

After the initial activation of the NAT Gateway or Internal Endpoint service, you will automatically receive a 14-day free trial. After the first trial instance ends or is deleted, the next created instance will be charged. The service can be billed either hourly or through an annual subscription. Charges will be included in the monthly consolidated bill under your main EMQX Cloud account.

ServiceHourly PriceAnnual Price
NAT Gateway$0.10/hour$876/year
Internal Endpoint$0.05/hour$438/year

Details of the charges can be viewed on the Bills page.

Note

Annual subscriptions cannot be created directly by users in the Console.

If you want to switch to annual billing, please create a support ticket. The EMQX Cloud operations team will create the annual subscription for you.

Before requesting the annual subscription, you must first create the service using hourly billing in the Console.

NAT Gateway Traffic Billing

Enabling NAT Gateway incurs additional egress traffic charges for all deployments, regardless of edition. Both directions of traffic are billable:

  • Outbound traffic from the deployment to the internet through NAT Gateway
  • Return traffic from the internet back to the deployment

All such traffic is counted as deployment egress traffic and charged at the standard egress rate ($0.15/GB). The total billable traffic may therefore exceed what appears to be outbound-only traffic.

For VPCs connected via PrivateLink or VPC Peering, traffic using non-standard private CIDRs (address ranges outside 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16) will be counted as egress traffic. Contact the EMQX Cloud team if this applies to your setup.

TIP

When the deployment hosting the service is stopped, services that are not in the trial period will continue to be billed normally. To avoid additional charges, please delete the service associated with this deployment.

For instructions on creating and managing these services, see: