Become an AWS pro by getting hands-on with API Gateway. Developed by AWS Solution Certified Architects, you’ll build secure apps, integrate services, and create a chat app. No setup, no cleanup, no hassle.

awsdocker.tar.gz

aws_access_key_id

aws_secret_access_key

PHONE_NUMBER

KEY_ID

AWS CLI

AWS CLI-Ehtesham

API Gateway is an important component of the AWS serverless stack and has great potential to enable low latency, low-cost, and secure applications. This course takes you through all aspects of the AWS API Gateway and contains ready-to-use code snippets to implement different patterns of serverless API development in AWS. 

You’ll learn core concepts and get hands-on experience with core API Gateway capabilities. You’ll also dive deep into data mapping and WebSocket APIs and build a fully functional multi-user chat application with WebSocket API. You’ll learn about various services that can integrate with the API Gateway. Throughout the course, you’ll use IaC to provision resources, coupled with an introduction to CloudFormation. You’ll conclude the course by building a fully functional chat application with a bot that listens to the conversation and sends random jokes when asked.

Through detailed lessons covering theoretical and practical knowledge, this course helps you master the AWS API Gateway service.

AWS API Gateway: The Unsung Warrior

## HTTP vs. REST API
HTTP APIs in the AWS API Gateway started as an alternative to the REST API. A cheaper, faster alternative with reduced functionality. Initially, it allowed only Lambda functions and external HTTP integration.

Over the years, it has gathered a lot of functionality and is popular in serverless deployments. If we don’t plan to use the REST API functionality, we should use the HTTP API. Better still, we can use the REST API and the power that it offers.

The HTTP, as well as the REST API in the AWS API Gateway, are technically REST APIs that use the HTTP protocol. Their names don’t indicate the difference in technology underneath.


## A sample implementation
As we can see in the CloudFormation template below, HTTP API is much simpler and more manageable. However, it lacks some of the power of the REST API. This one integrates the request to an external API.





# HTTP vs. REST API
HTTP APIs in the AWS API Gateway started as an alternative to the REST API. A cheaper, faster alternative with reduced functionality. Initially, it allowed only Lambda functions and external HTTP integration.

Over the years, it has gathered a lot of functionality and is popular in serverless deployments. If we don’t plan to use the REST API functionality, we should use the HTTP API. Better still, we can use the REST API and the power that it offers.

The HTTP, as well as the REST API in the AWS API Gateway, are technically REST APIs that use the HTTP protocol. Their names don’t indicate the difference in technology underneath.


# A sample implementation
As we can see in the CloudFormation template below, HTTP API is much simpler and more manageable. However, it lacks some of the power of the REST API. This one integrates the request to an external API.





Understand HTTP API and its comparison with the REST API. 

Introduction to API Gateway

API Gateway: High Level View

Getting Started with AWS API Gateway

API Gateway: Basic Configurations

Data Mapping Deep Dive

Leveraging AWS API Gateway for Public API Integration

Websocket Deep Dive

AWS Service Integration Deep Dive

Integrating AWS Services with API Gateway

Appendix

API Gateway Evaluation

Chat Application with Jokes Bot

Building a Chat Application Using Lambda Function and API Gateway

HTTP API

HTTP vs. REST API