The course is part of these learning paths
Amazon API Gateway
API Gateway is a fully managed service by Amazon that makes it easy for developers to create, publish, maintain and monitor their APIs at any scale without having to worry about versioning, authorizations, throttling and other administrative tasks. In this course, authored by Tehreem Siddiqui and narrated by Adam Hawkins, you will learn how to create and deploy REST API through API Gateway to expose HTTP endpoints, AWS Lambda functions and other AWS services.
Hey there. Welcome back to the API Gateway course. This lesson introduces the Amazon API Gateway and its uses. Let's dive right in.
The Amazon API Gateway provides central access for various functionalities such as exposing back end services, data access, lambda functions, ECS containers, or even any existing Web application running inside or even outside of AWS. Now all of this sounds pretty good at a high level so what's the point anyway? Well, the API Gateway generally unifies API handling across different applications or code bases. So there's no need to worry about building and logging, caching authentication or other kinds of expansion points that you had to deal with in traditional API management.
In general, the API getaway pushes shared functionality into infrastructure and moves functionality out of the application level. The Amazon API Gateway provides many benefits to developers. It encapsulates versioning along with support from multiple stages such as UAT staging or production. Also, API calls have been using the same authentication signature as other AWS services. This means you can leverage IAM rules to manage access to your APIs. You may also create and distribute API keys for third party developers. And this is where things start to get pretty cool.
API Gateway may be integrated with Cloud Front for easy caching and global CDN. The API Gateway also provides a centralized place to manage all of your APIs with CloudWatch. This telemetry data is generally enough to gauge performance and assess operational state. The API Gateway's also key for service applications, system maps, HTTP requests and responses to lambda function calls. Finally, you may also use the API death initial languages like Swagger to automatically generate entire client libraries in pod real languages.
I think you can see why that would be useful. Now all of these features make the API Gateway a compliant package. Also like most AWS services you pay for what you use so it may be cheaper than building a similar setup yourself from EC2 instances. Now my friend it's time to move from theory to practice. That's why you're even taking this course right? So join me for the next lesson where we get down and dirty building our first application.
About the Author
Tehreem is a Sr. Software Engineer with passion in Cloud Technologies, Big Data analytics, Software Testing and Automation. She has over 10 years of work experience comprising of her tenure at ServiceNow, Microsoft and Harmonic Inc. Most recently she has been developing learning content in-line with the emergence of Public Clouds and XaaS platforms with focus on AWS, Microsoft Azure and GCP. Tehreem resides in BayArea, CA with her family and when not working she enjoys nature/outdoors, movies and fine dining.