1
00:00:00,150 --> 00:00:02,690
In this video, we are going to create.

2
00:00:02,700 --> 00:00:07,380
Q On Amazon using the Amazon console for that purpose.

3
00:00:07,410 --> 00:00:13,280
Please click this create queue button and after that this will be comes to configurations.

4
00:00:13,290 --> 00:00:16,890
First configuration is the details of the queue.

5
00:00:16,890 --> 00:00:21,750
That means type of the queue, so we can choose the queue type for our application.

6
00:00:21,750 --> 00:00:26,220
The important thing is we can change the queue type after we created the queue.

7
00:00:26,220 --> 00:00:28,530
So that's why we should select the correct one.

8
00:00:28,560 --> 00:00:33,540
The standard one is the at least once delivery and message ordering isn't preserved.

9
00:00:33,540 --> 00:00:36,030
So this is the best effort ordering.

10
00:00:36,030 --> 00:00:41,890
But if you would like to require the FIFO, that means first in first delivery we can choose the five

11
00:00:41,890 --> 00:00:42,570
focus.

12
00:00:42,570 --> 00:00:48,600
But for our case, I'm choosing the standard because that queue is high throughput with low cost.

13
00:00:48,600 --> 00:00:52,290
So I'm going to give the name of the queue as the order queue.

14
00:00:52,290 --> 00:00:56,910
So if you scroll down, you can see the other configurations, for example, set the maximum message

15
00:00:56,910 --> 00:01:03,810
size, visibility, timeout and retention period, maximum side deliberately and so on.

16
00:01:03,810 --> 00:01:06,870
So these are the other configurations that we can change.

17
00:01:06,870 --> 00:01:11,040
For example, visibility timeout is really important and default is 32nd.

18
00:01:11,130 --> 00:01:16,530
Basically visible to time out sets the length of the time that the message received from the queue and

19
00:01:16,530 --> 00:01:19,200
will not be visible to the other message consumers.

20
00:01:19,200 --> 00:01:22,890
The visible timeout begins when Amazon returns a message.

21
00:01:22,890 --> 00:01:28,200
If the consumer fails to process and delete the message before the visible timeout expires, the message

22
00:01:28,200 --> 00:01:30,540
becomes visible to other consumers again.

23
00:01:31,470 --> 00:01:33,930
So I don't change any conversation for now.

24
00:01:33,990 --> 00:01:40,170
If you scroll down, you can see the access policy configurations in here.

25
00:01:40,170 --> 00:01:44,220
So I'm also don't change any configuration in the access policy.

26
00:01:44,220 --> 00:01:46,560
We can define who can access our queue.

27
00:01:46,650 --> 00:01:51,510
We are selecting the basic use, the simple criteria to define basic access policy.

28
00:01:51,510 --> 00:01:57,240
That means only the Q owner and only the Q owner fault for defining who can send message and who can

29
00:01:57,240 --> 00:01:58,350
receive the message.

30
00:01:58,350 --> 00:02:02,550
So let's follow the basic policy definition.

31
00:02:02,550 --> 00:02:10,140
If you scroll down, you can see the load policy for identifying which source you can use this Q as

32
00:02:10,140 --> 00:02:18,350
the letter Q and also allow policy provider driving and adding the items from the editor.

33
00:02:18,360 --> 00:02:18,990
Q to this.

34
00:02:18,990 --> 00:02:23,940
Q Since we don't have any data structure, we don't change any policy for now.

35
00:02:23,940 --> 00:02:26,820
So if you scroll down, you can also set the editor.

36
00:02:26,820 --> 00:02:34,860
Q That means we can send undeliverable message to the Q And if a message can consume by the successfully,

37
00:02:34,860 --> 00:02:36,480
we can send it to the editor.

38
00:02:36,480 --> 00:02:44,010
Q The editor lets us to isolate the problematic message to determine why they are failing, but I don't

39
00:02:44,010 --> 00:02:44,760
have any data.

40
00:02:44,760 --> 00:02:49,740
Three Q That's why it is set disabled for the default configuration.

41
00:02:49,740 --> 00:02:55,110
So that means I'm leaving as it is for all these complications and click the create button.

42
00:02:56,220 --> 00:02:58,890
So here we can see the details of the order.

43
00:02:58,890 --> 00:03:06,570
Q Page So if you look at the details, you can see the name, type A run URL and the encryption for

44
00:03:06,570 --> 00:03:07,620
the first details.

45
00:03:07,620 --> 00:03:13,260
If you expand this, you can see all the details of the Q in here, and if you scroll down, you can

46
00:03:13,260 --> 00:03:15,630
see the subscriptions of this.

47
00:03:15,630 --> 00:03:22,330
Q In order to implement final pattern, it could be very easy to add a subscription to Psns for Esquire's.

48
00:03:22,470 --> 00:03:25,200
Q And we also go to Lambda.

49
00:03:25,410 --> 00:03:29,820
That means we can set incoming message to trigger a lambda function.

50
00:03:29,820 --> 00:03:37,170
And also we have the letter Q We can set the Q to receive undeliverable message in here, and the monitoring

51
00:03:37,170 --> 00:03:39,020
is the same as the lambda execution log.

52
00:03:39,030 --> 00:03:42,930
So you can see the monitoring, tagging, access policy and so on.

53
00:03:42,930 --> 00:03:45,720
So all these complications can be set in here.

54
00:03:45,810 --> 00:03:51,050
Amazon SAS for providing the along to receive message and subscribe from the SNS topic.

55
00:03:51,090 --> 00:03:56,220
As you can see that we don't specify any this configuration, we only create the order.

56
00:03:56,220 --> 00:03:58,380
Q Send and receive message to this.