![]() ![]() ![]() Your own CloudFront distribution in front of your gateway.Other sources, but those sources have to be publicly accessible.Adding an Amazon Web Application Firewall (WAF), for example, is not possible. It uses CloudFront distributions, but you can’t edit the distribution.Important details to remember regarding the Edge Optimized : The combined API Gateway and CloudFront would later be called Edge Optimized API Gateway, preferring to the Edge locations available in CloudFront. In its initial Gateway came paired with a CloudFront distribution. At that Lambda Functions could not be placed in a VPC - this feature was released in February 2016. If you want to learn more about Serverless, check out my blog post on Building a stack bot with serverless.īecause a picture speaks a thousand words, here is a visualization:Īt its release in July 2015, API Gateway allowed access to Lambda and publicly available HTTP endpoints. You choose to configure API, it is hosted by AWS. The technology is completely invisible - all you get is a management interface. The Serverless services, manages its hosting, redundancy, scaling, patching. Authentication through Cognito or your own identification providerĪWS API Gateway resides in an AWS-managed environment.Throttling in general or for specific users.Presenting an API frontend for services.Monitoring and managing traffic coming into multiple services.Versioning different APIs, allowing for backward compatibility. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |