AWS API Gateway Support
API Gateway REST API vs HTTP API: choosing and migrating.
HTTP APIs are cheaper and faster to set up, but they leave out features that REST APIs have. Moving a REST API to an HTTP API is only safe if you do not depend on those features. We compare what you actually use and migrate in a controlled way.
When You Need This
The situations where this work pays for itself.
Signs it is time
- Your API Gateway bill is mostly request charges and the API is simple
- You are building a new Lambda-backed API and must pick a type
- You need JWT authorization with Cognito or another OIDC provider
- You need API keys, usage plans, request validation or WAF and are unsure which type supports them
- Latency overhead of the gateway matters to you
What you get
- A feature comparison table for your specific API
- A cost and latency comparison using your numbers
- Infrastructure as code for the new API
- A cutover and rollback plan
How we do it
A clear, safe process you can follow along with.
1. List the features in use
We export your REST API definition and check for usage plans, API keys, request validation, caching, WAF association, resource policies, private APIs, VTL mapping templates and edge-optimized endpoints.
2. Compare against HTTP API support
HTTP APIs support Lambda and HTTP integrations, JWT and Lambda authorizers, CORS configuration and custom domains. They do not support usage plans or API keys, and several REST-only features. We confirm against current documentation, since features change.
3. Estimate cost and latency
We use your request volume and payload sizes with the current price list to compare, and measure latency through both types on a test route.
4. Decide per API
Where a REST-only feature is essential, we keep REST. Otherwise HTTP API is usually the better default. Mixed estates are fine, each API on the type it needs.
5. Rebuild and test the HTTP API
We create the HTTP API from infrastructure as code, using payload format 2.0 or 1.0 on the Lambda integrations, replacing mapping templates with function code, and run the same test suite against both.
6. Cut over with a custom domain
We shift traffic using the domain mapping or Route 53 weighted records, watch 4XX, 5XX and latency, and keep the REST API until the metrics are stable.
Mistakes we help you avoid
Common ways this goes wrong, and what we do instead.
Migrating without checking authorizers
Cognito user pool authorizers on REST become JWT authorizers on HTTP API, and claims are validated differently.
Relying on API keys for security
API keys identify and throttle clients, they are not authentication. Use a real authorizer either way.
Ignoring payload format differences
Lambda event shapes differ between format 1.0 and 2.0. Handlers need updates.
Moving everything at once
Migrate one API or stage at a time so you can compare metrics.
Frequently Asked Questions
Is HTTP API cheaper than REST API?
HTTP APIs are priced lower per request than REST APIs. Actual savings depend on volume, so we calculate with your traffic.
Can HTTP API use WAF or usage plans?
No. WAF association, API keys and usage plans are REST API features. If you need them in front of an HTTP API, a CloudFront distribution with WAF can sit in front.
Can I convert a REST API to an HTTP API automatically?
There is tooling that imports OpenAPI definitions, but unsupported features must be handled by hand. We review and test the result.
Want Help With API Gateway REST API vs HTTP API: choosing and migrating?
Schedule an appointment. Tell us about your environment and we will outline the safest, highest-value approach.
Schedule Appointment › No commitment required