1
00:00:00,240 --> 00:00:05,490
In this video we are going to learn Amazon API Gateway Core Concepts.

2
00:00:05,700 --> 00:00:12,480
This is important because we will see these core concepts directly into a management console when creating

3
00:00:12,480 --> 00:00:13,830
our API gateways.

4
00:00:14,880 --> 00:00:21,840
So API Gateway has three main API types that we can create for our applications, which are the Amazon

5
00:00:21,840 --> 00:00:26,790
API, gateway HTTP API, rest API and the web socket API.

6
00:00:27,330 --> 00:00:30,370
We will use all types of API gateways during the course.

7
00:00:30,390 --> 00:00:32,010
Let me explain one by one.

8
00:00:32,400 --> 00:00:36,000
The first one is the API gateway http API.

9
00:00:36,770 --> 00:00:42,410
A set of pets and methods integrated with backend HTTP endpoints or lambda functions.

10
00:00:42,410 --> 00:00:46,160
We can distribute this collection in one or more states.

11
00:00:46,160 --> 00:00:52,670
Each load can expose one or more API methods with unique HTTP verb powered by the API gateway.

12
00:00:53,390 --> 00:00:58,970
This seems to be very similar with the rest API, but there are some differences that we will see in

13
00:00:58,970 --> 00:01:00,050
the upcoming videos.

14
00:01:00,590 --> 00:01:04,130
So the second type is API Gateway Rest API.

15
00:01:04,550 --> 00:01:10,550
Rest API is a collection of HTTP resources and methods integrated with the backend HTTP endpoints,

16
00:01:10,760 --> 00:01:13,610
lambda functions or other ADA services.

17
00:01:13,730 --> 00:01:17,150
We can distribute these collections in one or more states.

18
00:01:17,150 --> 00:01:20,630
Typically, API resources are organized in a resource.

19
00:01:20,630 --> 00:01:22,760
Today based on application logic.

20
00:01:22,880 --> 00:01:30,080
Each API resources can expose one or more API methods with a unique HTTP verb powered by API gateway,

21
00:01:31,430 --> 00:01:35,480
and the last API gateway type is API Gateway web socket API.

22
00:01:35,840 --> 00:01:41,780
Web Socket API is a collection of web circuit vaults and raw keys that are integrated with the backend

23
00:01:41,780 --> 00:01:45,830
HTTP endpoints, lambda functions or other services.

24
00:01:45,830 --> 00:01:49,070
We can deploy this collection in one or more states.

25
00:01:49,160 --> 00:01:55,550
API methods are invoked through the frontend web socket connections that we can associate with a registered

26
00:01:55,550 --> 00:02:00,350
custom domain name so we can continue the core concepts.

27
00:02:01,460 --> 00:02:04,340
API deployment is one of two core concepts.

28
00:02:04,430 --> 00:02:07,940
API deployment is a snapshot of our API Gateway API.

29
00:02:07,970 --> 00:02:14,270
The deployment must be associated with one or more API states for the client it is use it.

30
00:02:14,660 --> 00:02:16,880
And another core concept is API.

31
00:02:16,880 --> 00:02:24,020
End point and point is a hostname for an API deployed to the specific region in the API gateway.

32
00:02:24,230 --> 00:02:28,220
The hostname is in the form of the these URLs.

33
00:02:28,220 --> 00:02:31,760
You can see that this is the one of the API endpoint.

34
00:02:31,800 --> 00:02:37,310
They include API ID execute API region and the Amazon URL.

35
00:02:37,700 --> 00:02:43,610
And there are three types of endpoint are supported in the API endpoint.

36
00:02:43,640 --> 00:02:48,380
These are the optimized, private and regional API endpoints.

37
00:02:48,470 --> 00:02:52,250
We will follow the default one, which is the regional API endpoint.

38
00:02:52,250 --> 00:02:58,760
This is the default hostname of an API Gateway API that is deployed to the specific region.

39
00:02:59,420 --> 00:03:02,450
So another core concept is proxy integration.

40
00:03:02,450 --> 00:03:07,160
Proxy integration is simplified API gateway integration configurations.

41
00:03:07,160 --> 00:03:13,880
We can set a proxy integration as a HTTP proxy integration or Lambda Proxy Integration API gateway for

42
00:03:13,880 --> 00:03:21,500
HTTP proxy integration forward all request and response between frontend and the HTTP backend API gateway

43
00:03:21,500 --> 00:03:27,380
sends the entire request as input to the backend lambda function for the Lambda Proxy Integrations API

44
00:03:27,380 --> 00:03:31,850
gateway, then converts to the lambda function output into front end HTTP response.

45
00:03:32,090 --> 00:03:39,980
So in this API, proxy integration is most common use with a proxy resource represented by the greedy

46
00:03:40,010 --> 00:03:41,180
path variables.

47
00:03:41,180 --> 00:03:48,440
So we will also use proxy integration when we creating rest API into Amazon API gateway from the management

48
00:03:48,440 --> 00:03:49,070
console.