Softwr

Software · head to head

AWS API Gateway vs Microsoft Azure API Management

AWS API Gateway logo

AWS API Gateway

Software

Fully managed API gateway service for creating and managing APIs at scale

From
Free
Rated
-
Microsoft Azure API Management logo

Microsoft Azure API Management

Software

Hybrid, multi-cloud API management service on Azure

From
Free
Rated
-

The short version

  • Each has a real cost: AWS API Gateway rEST APIs cost $3.50 per million calls against $1.00 for HTTP APIs, so the older and more featureful type is three and a half times dearer; Microsoft Azure API Management prices are not shown on the pricing page itself; every tier renders as a placeholder and routes to the calculator or sales
  • They diverge on capability: AWS API Gateway covers REST APIs, Microsoft Azure API Management covers API Gateway.

Where they differ

Only the attributes on which AWS API Gateway and Microsoft Azure API Management actually diverge.

Attributes where AWS API Gateway and Microsoft Azure API Management differ
AttributeAWS API GatewayMicrosoft Azure API Management
Pricing modelusage-basedsubscription
PlatformsAWS CloudCloud, Hybrid, Multi-cloud
Founded20061975

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Unknown).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in AWS API Gateway

  • REST APIs
  • WebSocket APIs
  • HTTP APIs
  • Lambda
  • EC2
  • DynamoDB
  • CloudWatch
  • IAM

Only in Microsoft Azure API Management

  • API Gateway
  • Developer Portal
  • API Policies
  • Azure services
  • AWS
  • Google Cloud
  • On-premises
  • Cloud support

What people use each for

The jobs each tool is most often brought in to do.

AWS API Gateway

  • Fronting Lambda functions with an HTTP endpointnot Microsoft Azure API Management
  • REST and HTTP API management with throttling and keysnot Microsoft Azure API Management
  • WebSocket APIs for real-time clientsnot Microsoft Azure API Management
  • Private APIs reachable only inside a VPCnot Microsoft Azure API Management
  • Publishing a developer portal for API consumersnot Microsoft Azure API Management

Microsoft Azure API Management

  • API gateway and lifecycle management on Azurenot AWS API Gateway
  • Throttling, keys and policies in front of backend servicesnot AWS API Gateway
  • Developer portal for internal and partner APIsnot AWS API Gateway
  • Hybrid deployments using self-hosted gatewaysnot AWS API Gateway

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

AWS API Gateway

  • REST APIs cost $3.50 per million calls against $1.00 for HTTP APIs, so the older and more featureful type is three and a half times dearer
  • Data transfer out is charged at $0.09 per GB on top of request pricing
  • WebSocket APIs bill connection minutes as well as messages, at $0.25 per million minutes
  • Private APIs avoid data transfer charges but incur AWS PrivateLink costs instead
  • The developer portal is $125 a month, with additional portal products at $12.50 each
  • The free tier lasts 12 months rather than being ongoing

Microsoft Azure API Management

  • Prices are not shown on the pricing page itself; every tier renders as a placeholder and routes to the calculator or sales
  • Two parallel generations of tiers, classic and v2, so the choice is which lineage before which size
  • The Developer tier is explicitly not for production
  • Self-hosted gateways and workspace gateways are charged separately from the service

Pricing, plan by plan

AWS API Gateway

Free
  • Free TierFree
    • 1M requests per month
    • Basic API management
  • Pay-as-you-go$3.5/per 1M requests
    • Unlimited requests
    • HTTP APIs
    • REST APIs

Microsoft Azure API Management

Free
  • FreeFree
    • 1M calls/month
    • Community support
  • Developer$50/monthly
    • 10M calls/month
    • Email support
  • Premium$500/monthly
    • Unlimited calls
    • Priority support
    • SLA

Which should you pick?

Choose AWS API Gateway if

  • You need rest apis.
  • You want to start without paying.
  • You work on AWS Cloud.
  • You also want websocket apis.

Choose Microsoft Azure API Management if

  • You need api gateway.
  • You want to start without paying.
  • You work on Cloud, Hybrid, Multi-cloud.
  • You also want developer portal.

Questions people ask

Is AWS API Gateway or Microsoft Azure API Management better?
Neither clearly leads. AWS API Gateway starts at Free and Microsoft Azure API Management at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, AWS API Gateway or Microsoft Azure API Management?
AWS API Gateway starts at Free and Microsoft Azure API Management at Free.
Does AWS API Gateway or Microsoft Azure API Management run on more platforms?
AWS API Gateway runs on AWS Cloud. Microsoft Azure API Management runs on Cloud, Hybrid, Multi-cloud.
Can I use AWS API Gateway for free?
Both have a free tier, so you can try either at no cost before committing.
What is AWS API Gateway best used for?
AWS API Gateway is most often used for fronting lambda functions with an http endpoint, rest and http api management with throttling and keys, websocket apis for real-time clients, private apis reachable only inside a vpc. Of those, fronting lambda functions with an http endpoint and rest and http api management with throttling and keys are not what Microsoft Azure API Management is typically brought in for.
What can AWS API Gateway do that Microsoft Azure API Management cannot?
AWS API Gateway covers REST APIs, WebSocket APIs, HTTP APIs, Lambda. Microsoft Azure API Management covers API Gateway, Developer Portal, API Policies, Azure services.

Related pages

Other head to heads