Skip to main content
TrustRadius
Amazon API Gateway

Amazon API Gateway

Overview

What is Amazon API Gateway?

AWS offers the Amazon API Gateway supports the creation and publication of an API for web applications, as well as its monitoring and maintenance. The Amazon API Gateway is able to support thousands of API calls concurrently and provides traffic…

Read more
Recent Reviews
Read all reviews

Popular Features

View all 7 features
  • API usage data (12)
    8.3
    83%
  • API monitoring and logging (13)
    7.6
    76%
  • Rate limits and usage policies (12)
    7.0
    70%
  • API access control (12)
    6.6
    66%
Return to navigation

Pricing

View all pricing

Past 300 Million

$0.90

Cloud
Per Million

First 300 Million

$1.00

Cloud
Per Million

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Features

API Management

API management handles technical things like user permissions, version control,and security, in addition to business items like documentation and pricing

7.8
Avg 8.2
Return to navigation

Product Details

What is Amazon API Gateway?

Amazon API Gateway Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

AWS offers the Amazon API Gateway supports the creation and publication of an API for web applications, as well as its monitoring and maintenance. The Amazon API Gateway is able to support thousands of API calls concurrently and provides traffic management, as well as monitoring and access control.

Reviewers rate API versioning highest, with a score of 9.3.

The most common users of Amazon API Gateway are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(101)

Attribute Ratings

Reviews

(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
March 12, 2021

API Gateway is Great for Integrating REST and HTTP Access to Other AWS Resources

Michael Jenkins | TrustRadius Reviewer
Michael Jenkins
Senior Systems Reliability Engineer
The Walt Disney Company (Entertainment, 10,001+ employees)
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We are using API Gateway (API GW) as an HTTP front end for internal resources including lambda functions and load-balanced web applications. Other teams are using API GW as integration for static resources.

The main problem that API GW addresses for us is providing an authorization management point for access to internal services. We can use the API keys, authorization hooks, and usage plans to really dial in who can access our applications while controlling how they access them.
Pros and Cons
  • Swagger integration
  • Rate limiting
  • API key management
  • Lambda Integration
  • Testing and rapid development
  • Client certificates are troublesome when trying to attach them to API GW stages.
  • Debugging across several services can be difficult when API GW is integrated with Route 53 and another service like Lambda or EC2/ELB.
  • Creating internal/private APIs, particularly with custom domains, can be unintuitive.
Likelihood to Recommend
API GW is great for giving access to asynchronous operations that are fast and don't need to be online all the time. Lambda functions are the classic example.

In the past, an operation that is called on via an HTTP endpoint would be implemented using a server-based solution. With high availability in place that would include a server or two and a load balancer. Over time this setup can be costly, especially if the service is not used at full capacity; cycles are wasted when the servers are sitting there waiting to respond.

If the operation can be distilled down to a function, an API GW + Lambda solution could be put in place that performs the operation as needed only when requested. Comparing the low price point for API GW requests and Lambda CPU+Memory, the savings can be night and day over the server-based implementation.
Amazon API Gateway Feature Ratings
API Management (7)
85.71428571428571%
8.6
API access control
100%
10.0
Rate limits and usage policies
100%
10.0
API usage data
80%
8.0
API user onboarding
70%
7.0
API versioning
100%
10.0
Usage billing and payments
80%
8.0
API monitoring and logging
70%
7.0
Return on Investment
  • Faster API development.
  • Tighter control over resource access with API keys and usage plans.
  • Cost savings compared to server based API implementations.
Alternatives Considered
I have reviewed NGINX, Kong, and Azure API Management. While very capable, NGINX and Kong are server-based implementations; my team would prefer not to have another cluster of servers to manage. Having a managed service in API GW is preferable.

While Azure API Management is also a comparable product, the teams I support are heavily invested in AWS making the use of API GW much more approachable.
Other Software Used
Amazon Relational Database Service (RDS), Amazon Aurora, PagerDuty
Products Replaced
No
Key Differentiators
  • Price
  • Product Features
  • Product Usability
Return to navigation