What is Amazon API Gateway?
What is Amazon Route 53?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Amazon API Gateway?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
API Gateway in conjunction with Lambda has allowed us to become 'serverless'. We have a number of API endpoints that range from simple CRUD operations, through to triggering chains of complex background jobs. Like Lambda, this service has released us from getting bogged down in infrastructure management, freeing up huge amounts of time to focus on solving business problems.
Since most of zerotoherojs.com infrastructure is on AWS, Route53 is the obvious DNS of choice.
I’m also considering CloudFlare, but haven’t decided the pros and cons of migrating yet.
We utilize it as main DNS for fron-tend servers, Dynamic DNS for internal VPCS and simple signal flag storage for autoscaled instances
It provides me with POST endpoints; I don't run servers and some third-party services need to POST data to my application.
PrometheanTV utilizes the Amazon Route 53 service to manage various domains utilized by the products and services.
Triggers the Lambda function from a GitHub WebHook push into
Excellent API Gateway, some quirks but most are being addressed over time, easy integration with Lambda
- DNS registration.
- DNS routing for private/local in VPC.
- DNS HA/Load balancing.
Amazon AWS Domain Name Services. The logical choice for AWS hosted web sites.