aws_route53_resolver_endpoint cost estimation
An inbound or outbound DNS resolver endpoint for hybrid name resolution, billed per elastic network interface (IP) per hour. Two IPs are ~$183/month, plus DNS query charges.
An aws_route53_resolver_endpoint enables DNS resolution between a VPC and an on-premises network — inbound endpoints let on-prem resolve VPC/private-hosted-zone names, outbound endpoints forward VPC queries to on-prem resolvers. Cost is per elastic network interface (IP) per hour: ~$0.125/IP-hour, and AWS requires at least two IPs per endpoint for availability, so a minimum endpoint is ~$183/month.
The per-IP fee is the standing cost, and it's charged per IP regardless of query volume. On top, resolver queries forwarded through the endpoint bill per million queries. Both an inbound and an outbound endpoint (the common hybrid setup) means two endpoints, ~$365/month minimum before queries.
The cost decisions are how many endpoints you genuinely need (do you need both directions?) and how many IPs per endpoint (two is the minimum; more add availability and cost). Resolver endpoints are easy to leave running after a hybrid-connectivity project ends.
c3x prices the endpoint from ip_address_count, so the standing per-IP cost is visible before deployment.
Terraform example
A minimal but realistic configuration that C3X can estimate.
resource "aws_route53_resolver_endpoint" "outbound" {
name = "onprem-forwarder"
direction = "OUTBOUND"
security_group_ids = [aws_security_group.resolver.id]
ip_address {
subnet_id = aws_subnet.private[0].id
}
ip_address {
subnet_id = aws_subnet.private[1].id
}
}Pricing dimensions
What you actually pay for when you provision aws_route53_resolver_endpoint.
| Dimension | Unit | What's being charged |
|---|---|---|
| Resolver endpoint IPs | per IP-hour | Per elastic network interface (IP) per hour, minimum two IPs per endpoint, billed continuously regardless of query volume. $0.125/IP-hour → 2 IPs ≈ $182.50/month |
| DNS queries | per million | Queries forwarded through the resolver endpoint bill per million. Usage-based. |
Sample C3X output
One endpoint with the minimum two IPs, 24/7:
aws_route53_resolver_endpoint.outbound
└─ Resolver endpoint IPs (2) 1460 ip-hours $182.50
Monthly $182.50Optimization tips
Common ways to reduce aws_route53_resolver_endpoint cost without changing the workload.
Only create the directions you need
~$183/month per unneeded endpointInbound (on-prem resolves VPC names) and outbound (VPC forwards to on-prem) are separate endpoints, each ~$183/month minimum. Many setups need only one direction — don't provision both reflexively.
Use the minimum IPs that meet your availability target
~$91/month per IP avoidedTwo IPs (in two AZs) is the required minimum and gives HA. Additional IPs add throughput and availability but each is ~$91/month — add them only when query throughput demands it.
Share resolver endpoints across VPCs
Per duplicate endpoint avoidedA resolver endpoint and its rules can be shared (via Resource Access Manager) across VPCs in an organization, so you don't run separate endpoints per VPC for the same on-prem connectivity.
Decommission endpoints after hybrid projects end
Full endpoint cost when retiredEndpoints bill continuously whether or not queries flow. Reclaim ones left over from completed migrations or retired on-prem connectivity.
FAQ
How is a Route 53 Resolver endpoint billed?
Per elastic network interface (IP) per hour — ~$0.125/IP-hour — with a required minimum of two IPs per endpoint, so ~$183/month minimum. Queries forwarded through it bill per million on top. The per-IP fee is charged regardless of query volume.
Do I need both inbound and outbound endpoints?
Only if you need DNS resolution in both directions. Inbound lets on-prem resolve VPC names; outbound forwards VPC queries to on-prem. Each is a separate ~$183/month endpoint — provision only the direction(s) your hybrid setup actually requires.
How does c3x estimate the cost?
From ip_address_count, pricing the per-IP standing fee (minimum two IPs). DNS query volume is usage-driven and modelled separately.
Related resources
Estimate this resource in your own Terraform
Free, open source, no API key. C3X parses your Terraform and shows line-item cost for every resource, including aws_route53_resolver_endpoint.