1
00:00:03,990 --> 00:00:10,810
The next step in the process would be to modify our pipeline and to upload the artifact from catalepsy

2
00:00:11,160 --> 00:00:20,070
to Adewusi S3 to the S3 market that we have created in order to interact with Amazon Web Services from

3
00:00:20,070 --> 00:00:24,840
Get Lecci, we need to use a tool that AWB provides.

4
00:00:25,110 --> 00:00:29,010
It's the AWB command line interface that AWB Seelie.

5
00:00:29,550 --> 00:00:35,940
Fortunately, there's already a darker image, but it includes the AWB Seelie so we can use it directly

6
00:00:35,940 --> 00:00:36,580
in website.

7
00:00:37,000 --> 00:00:38,450
Let me show you how that works.

8
00:00:40,330 --> 00:00:43,570
So let's go ahead then and deploy stage.

9
00:00:45,820 --> 00:00:47,620
And also the associated job.

10
00:00:51,720 --> 00:00:54,270
I'm going to sign the diploid job to the stage.

11
00:00:56,660 --> 00:00:59,520
And now comes the part that you need to pay attention to.

12
00:01:00,200 --> 00:01:05,030
So I'm going to define an image that I'm going to use, but this time I'm going to set some additional

13
00:01:05,030 --> 00:01:05,600
properties.

14
00:01:18,110 --> 00:01:23,240
Some darker images provide an entry point, this makes it easier when you're running the darker image

15
00:01:23,240 --> 00:01:24,540
to directly interact with that.

16
00:01:25,370 --> 00:01:28,850
But we're seeing this typically causes some problems.

17
00:01:29,120 --> 00:01:34,550
So any images that have an entry point different, even if you don't know what it is, will cause problems.

18
00:01:34,790 --> 00:01:40,310
So for that reason, we need to override the entry point and to say practically it doesn't have an entry

19
00:01:40,310 --> 00:01:40,640
point.

20
00:01:46,250 --> 00:01:49,760
So this is how we can specify no entry point for this image.

21
00:01:51,340 --> 00:01:55,370
Mean the script will have the Seelie available.

22
00:01:56,140 --> 00:02:03,250
This goes something like this can simply say us and because we want to interact with the simple storage

23
00:02:03,250 --> 00:02:06,790
service, S3 can simply say S3.

24
00:02:07,210 --> 00:02:14,140
And then what are you going to do is we're going to copy KTP and we're going to reference the built

25
00:02:14,140 --> 00:02:14,740
folder.

26
00:02:16,180 --> 00:02:16,780
Lipps.

27
00:02:18,120 --> 00:02:23,010
And artifact name will be cast API that jar.

28
00:02:24,550 --> 00:02:30,850
And then we're going to specify the path where we are going to copy this, this will be three.

29
00:02:31,990 --> 00:02:37,960
Slash, slash now going to use the S3 Buckett variable that we have defined previously.

30
00:02:41,080 --> 00:02:47,290
And again, specified the path where they should go and this will still be cast API that DJA.

31
00:02:49,270 --> 00:02:55,180
Because AAUW works with Regents', it is always a good idea to specify which region we are going to

32
00:02:55,180 --> 00:02:55,500
use.

33
00:02:55,810 --> 00:03:02,470
So for that, before wanting to copy command on S3, we're gonna say let's configure.

34
00:03:04,350 --> 00:03:08,720
And I said the region to us is the one, because this is the region that I have been using.

35
00:03:08,760 --> 00:03:11,550
But if you have a different region, you may use that one.

36
00:03:12,630 --> 00:03:17,850
Just to keep things simple, I'm not putting this in a variable, but for your case, it may be a good

37
00:03:17,850 --> 00:03:22,200
idea to put in a variable anything that is variable that may change.

38
00:03:23,010 --> 00:03:28,350
So from this point of view, this is all that we need in order to copy our artifact to S3.

39
00:03:29,010 --> 00:03:35,160
The problem now is that if we simply run this command innumeracy, I will have no idea who we are.

40
00:03:35,430 --> 00:03:40,950
And if we have access to the specific target in this case without providing any credentials, we will

41
00:03:40,950 --> 00:03:42,450
not have access to the market.

42
00:03:42,630 --> 00:03:44,810
So as this stands, this will not work.

43
00:03:45,930 --> 00:03:51,990
So we order to get this to work, we need to generate some credentials to save them and get Lipsky so

44
00:03:51,990 --> 00:03:59,880
that we can provide these credentials to a WCI and then a WCI would be able to copy this file to the

45
00:03:59,880 --> 00:04:00,720
respective bucket.

46
00:04:00,930 --> 00:04:02,180
And trust me, it is quite easy.

47
00:04:03,450 --> 00:04:09,840
Going back to the AWB management console, you have to go to all services and identify I am.

48
00:04:11,680 --> 00:04:18,839
I am stands for identity and access management, practically, this is the service within AWB ensures

49
00:04:18,850 --> 00:04:21,950
that when you're calling a service, you actually have the right credentials.

50
00:04:22,300 --> 00:04:25,480
I'm going to click here on users at the user.

51
00:04:26,770 --> 00:04:28,820
Now, to simply call my user catalepsy.

52
00:04:31,180 --> 00:04:37,210
And I will make sure that this user has programatic access, what this means is practically that we

53
00:04:37,210 --> 00:04:42,070
can use the AWB, CLIA, in this case, wheat, this user.

54
00:04:42,280 --> 00:04:43,330
This is what we want to do.

55
00:04:43,930 --> 00:04:45,130
It's going to go to permissions.

56
00:04:45,400 --> 00:04:48,400
We need to tell us what this user can do.

57
00:04:49,080 --> 00:04:49,480
This case.

58
00:04:49,480 --> 00:04:53,110
We only want to give this user permissions to S3.

59
00:04:53,410 --> 00:04:59,470
So we're going to use policies and policies are predefined rules that can be applied to users.

60
00:04:59,860 --> 00:05:04,300
Of course, you can create your own policies, but just to simplify things, you're going to use an

61
00:05:04,300 --> 00:05:05,260
existing policy.

62
00:05:05,890 --> 00:05:08,950
So in the search field, I'm going to search for S3.

63
00:05:10,530 --> 00:05:16,530
And to make things very, very simple, I'm to select Amazon as three full access, and what this means

64
00:05:16,530 --> 00:05:24,210
is that this user will have access to the S3 bucket, can create and delete and so on, so will have

65
00:05:24,210 --> 00:05:27,030
full access, but only to the S3 service.

66
00:05:28,410 --> 00:05:29,550
You don't see any tanks.

67
00:05:31,120 --> 00:05:34,240
Now, after this overview page, we can go ahead and create that user.

68
00:05:35,670 --> 00:05:40,320
Now, at this final page, it's important that you do not close this yet because we need to save this

69
00:05:40,320 --> 00:05:42,750
information and we know that the user is guilty.

70
00:05:43,590 --> 00:05:48,830
But now what AWB has done has created an excess in a secret access key.

71
00:05:49,320 --> 00:05:55,230
What do we need to do is to copy this information into your lecci variable so that we can use them in

72
00:05:55,230 --> 00:05:55,710
script.

73
00:05:57,000 --> 00:06:02,280
The first variable name that we need to create is called a W.S., underscore excess.

74
00:06:02,280 --> 00:06:03,480
Underscore key.

75
00:06:03,480 --> 00:06:04,400
Underscore a.

76
00:06:06,710 --> 00:06:11,000
And we're going to copy this idea that we have seen from the U.S. consul.

77
00:06:12,350 --> 00:06:19,340
The next variable that will define is called a secret access key with underscores between the words.

78
00:06:20,360 --> 00:06:24,620
I'm going to click here on show, I'm going to copy this secret access key.

79
00:06:25,960 --> 00:06:27,540
And pasted here in this field.

80
00:06:29,190 --> 00:06:30,870
After I'm done, I'm going to see if the variables.

81
00:06:33,230 --> 00:06:38,300
Now we have everything in place in order to start running our pipeline, so I'm going to committees

82
00:06:38,540 --> 00:06:40,030
and let's see how it works.

83
00:06:45,350 --> 00:06:50,720
If you go back to take a look at the pipeline, we see that the deployment succeeded even though it

84
00:06:50,720 --> 00:06:54,790
didn't do a complete deployment, it only copied the artifact to S3.

85
00:06:54,800 --> 00:07:01,700
And just in case you're wondering, how does the Racheli know to use practically the username and password

86
00:07:01,700 --> 00:07:02,510
that we have given?

87
00:07:02,750 --> 00:07:06,290
This is because we have used the convention when we have named our variables.

88
00:07:07,130 --> 00:07:12,050
The way the variables are named isn't arbitrary, isn't something that I have decided.

89
00:07:12,440 --> 00:07:20,090
This is specified in the Serai documentation and I will look for these environmental variables to see

90
00:07:20,090 --> 00:07:24,320
if they exist and if they exist, it will pick them up and use them automatically.

91
00:07:24,470 --> 00:07:27,380
And this is why this deployment now is working.

92
00:07:28,540 --> 00:07:34,330
Going back to the three buckets, if we go now into cars, API deployments or how you have named your

93
00:07:34,330 --> 00:07:40,020
bucket, it will see that it contains now our artifact that we have generated from catalepsy.

94
00:07:41,130 --> 00:07:47,400
If you want to learn more about the WASC ally, commands will link you resources to the official.

95
00:07:47,400 --> 00:07:51,990
A.W. has documentation regarding these tools as a resource to this video.