1
00:00:04,840 --> 00:00:10,450
When job fails, it is always a good idea to start right from the beginning and to understand step by

2
00:00:10,450 --> 00:00:12,150
step what happened in this process.

3
00:00:13,260 --> 00:00:20,220
In this case, the comment that generated the error is to create application version command.

4
00:00:20,790 --> 00:00:27,570
As you can see, as soon as we started uploading our artifact to Elastic Bienstock to create a new version,

5
00:00:28,230 --> 00:00:29,090
there was an error.

6
00:00:29,610 --> 00:00:32,810
And in this case, the error that occurred is EXIS denied.

7
00:00:33,360 --> 00:00:39,750
So it seems that our user in this case, the catalepsy, a user that we have created, is not authorized

8
00:00:39,750 --> 00:00:43,640
to perform, create application version and create application version.

9
00:00:43,650 --> 00:00:47,550
Obviously, in this case is a permission that our user does not have.

10
00:00:51,580 --> 00:00:59,770
In order to fix this, all we have to do is to modify the security settings in I for the user catalepsy.

11
00:01:03,420 --> 00:01:06,500
I'm going to go to the users catalepsy.

12
00:01:09,700 --> 00:01:14,290
And you will see here that we have the possibility of adding permissions now, even if we don't know

13
00:01:14,290 --> 00:01:18,190
exactly which permissions we are going to add, we can start searching for the.

14
00:01:19,880 --> 00:01:24,560
So the quickest way to solve this is to start searching for Elastica Bienstock.

15
00:01:31,500 --> 00:01:37,230
And the permission that we're going to sign is the full access permission, and this will provide full

16
00:01:37,230 --> 00:01:42,630
access to the AWACS, Elastic Bienstock and all the underlying services.

17
00:01:42,810 --> 00:01:45,690
And this case will be the S3 bucket.

18
00:01:46,170 --> 00:01:49,810
And Ishita is for elastic compute.

19
00:01:50,010 --> 00:01:51,990
And this creates virtual machines.

20
00:01:53,040 --> 00:01:54,120
So let's check this.

21
00:01:55,020 --> 00:01:55,830
Review it.

22
00:01:58,340 --> 00:01:59,390
And permissions.

23
00:02:00,840 --> 00:02:04,770
Now we're used that will now have all the provisions necessary for the pipeline to run.

24
00:02:07,320 --> 00:02:14,080
Since Elastic Bienstock already includes access to S3, you may want to remove this permission as now

25
00:02:14,100 --> 00:02:15,290
this is redundant.

26
00:02:19,230 --> 00:02:24,060
Because the rest of the pipeline is OK, I'm going to simply retried the deployed job.

27
00:02:29,970 --> 00:02:34,150
But going back to the console, we can now see that everything is successful.

28
00:02:34,680 --> 00:02:39,810
So what has happened is that we have created a version and we have get a response back.

29
00:02:39,810 --> 00:02:43,680
And, for example, we'll see here that the version is seven.

30
00:02:44,310 --> 00:02:50,370
And this was the artifact that we have used from version seven and so on.

31
00:02:50,700 --> 00:02:54,540
And after that, we have deployed this artifact.

32
00:02:54,540 --> 00:03:01,140
So we have updated the environment to say so in the technical term that is being used by a Bienstock

33
00:03:01,140 --> 00:03:01,890
and Adewusi.

34
00:03:04,240 --> 00:03:10,030
So if we now go to Elastic Bienstock, we can simply refresh this information and you will see here

35
00:03:10,030 --> 00:03:13,000
that a running version is now version seven.

36
00:03:13,960 --> 00:03:16,320
And that everything seems to be working fine.

