1
00:00:00,210 --> 00:00:06,240
In this video, we are going to continue to learn API, get a HTTP API core concepts.

2
00:00:06,270 --> 00:00:08,220
This time we will learn states.

3
00:00:08,700 --> 00:00:13,710
States are independent, configurable environments that are API can be deployed.

4
00:00:14,100 --> 00:00:19,590
We have to deploy a stage for API configuration to change take effect.

5
00:00:19,590 --> 00:00:22,320
But also we can configure stage to auto deploy.

6
00:00:22,440 --> 00:00:27,300
By default, all HTTP APIs created through the console have a default stage.

7
00:00:27,300 --> 00:00:28,560
Name the default.

8
00:00:29,300 --> 00:00:36,620
All chains that we make our API are auto deployed to the default stage and we can also add states that

9
00:00:36,770 --> 00:00:40,400
represent the environments, for example, development and production.

10
00:00:41,180 --> 00:00:46,310
So an API stage is a logical reference to lifecycle stage to our API.

11
00:00:46,400 --> 00:00:49,940
We can give the example dev proto better and so on.

12
00:00:50,060 --> 00:00:57,200
An API states are identified by the API, ID and stage name and they are included in the URL of the

13
00:00:57,200 --> 00:00:58,580
invoke of the API.

14
00:00:59,480 --> 00:01:05,690
So each state is named reference to the deployment of the API and it is made available for the client

15
00:01:05,690 --> 00:01:07,100
application to invoke.

16
00:01:07,310 --> 00:01:11,300
We can create a default stage that is served from the base of our API.

17
00:01:11,540 --> 00:01:17,780
As you can see an example in here, these are generated from the default stage of the HTTP API.

18
00:01:19,700 --> 00:01:23,570
A deployment is a snapshot of our API configuration.

19
00:01:23,570 --> 00:01:28,370
After we deploy an API to the stage it is available for clients to invoke.

20
00:01:28,370 --> 00:01:31,700
We have to deploy an API for change to take effect.

21
00:01:31,730 --> 00:01:38,300
If we enable automatic deployments, change, an API are automatically released for us in order to have

22
00:01:38,300 --> 00:01:40,850
API to automatically deploy our API.

23
00:01:40,880 --> 00:01:44,780
When we make updates, keep automatic deployments enabled.

24
00:01:44,900 --> 00:01:50,360
If we turn off the automatic deployments, we have to manually deploy our API for change to take effect.

25
00:01:50,660 --> 00:01:51,080
Okay.

26
00:01:51,230 --> 00:01:57,410
We have understood the API gateway HTTP API core concepts which are the roles integration end stage.

27
00:01:57,440 --> 00:01:59,030
Let's do some practice.