Herion and welcome back.
Now, in today's video, we'll be discussing about regaining access to a log distributed nationally.
If you're working with these three budget policies regularly at a certain amount of time, there will
be a case where you will be locked out of your history budget and then you will need to find a way to
regain access to it.
So let's go ahead and look into it on what exactly this means.
Now, whenever you're writing a story, book policy, specifically their Denay related conditions,
you have to be very careful.
So in case, if your budget policy is not configured correctly, then all of the ATM users across your
account can be logged out, including the Amusa that has the administrative access.
So this is one of the screenshots.
So you'll see that when our year end user with the administrative access is trying to see the objects
of the extra budget, it is basically giving an edit stating insufficient permission to list the objects.
So this is basically where the users are logged out of this trip.
So let's do one thing.
Let's explore a budget policy will mess up the budget policy so that we get logged out and then we look
into the solution associated with it.
So today's budget policy is associated with a restriction by IP addresses.
Now, there can be cases where you only want a certain set of IP addresses or a C++ in this to be able
to connect to the S3 bucket.
So in such cases, you can go ahead and also create a bucket policy for it.
So this is a sample bucket policy, a very straightforward one.
So if you'll see the effect, this delay, the extraction is start.
So basically deny all the actions on this three bucket, provided there is a condition and the condition
is not IP address and you have the Syeda range.
So any request that is made to this is Terry Bucket, which is not within this range.
Go ahead and deny this request.
So let's try it.
So I have this policy trailer and this policy is very similar to the screenshot where you have the effect
of Disney Action is a three star and within the source IP address, I have specified my current source
IP address here.
So generally in Google, when you do a maybe you get the IP address here and the same IP address I have
specified with this idea, range of 32 and then I have the bucket area.
So let's go ahead and copy this up and form a three bucket.
Currently I have no bucket policy.
I have deleted all the earlier policies here and will be posting are deny policy brand new Aurier ones.
Then you can see the change grid.
Now in case if you are working with this policy, it is a little dangerous, so you have to be very
careful.
So let's look into it.
So when I go to the objects here, I'm able to see all the objects that are part of the bucket.
Now, in fact, let me also refresh the page.
And yes, we are able to see things perfectly.
Now, let's assume that you are creating such policy and what you did was by mistake.
You made a typo.
So instead of 157, you have 156.
So now what will happen?
Let's try it.
So let's go back to the operation.
Let's edit it and change from 157 to 156, just a small typo.
Her analysis of the change and immediately you see we are now getting error error related to the poor
mission review, error related to the bucket policy, error related to other settings.
And in fact, if you go to the objects here, you're able to see it.
In fact, if I just refresh the page, you see, we are not even able to see the objects here.
So essentially you're logged out of this as three buckets.
You cannot really even delete the bucket policy.
So this is the interesting part here.
All right.
So this is Delacourt of History Bucket.
So let's look into how we can overcome this now as we're discussing writing a strong set of a three
bucket policy specifically that deny policy can lead you to be locked out of the history bucket.
So the solution is pretty simple here.
In order to regain the control of these three bucket, you need to log in with the root user and you
have to delete the bucket policy.
This is important to note now from a different tab.
I'm currently logged into my account with the help of road user.
So if I quickly open this up, even for the road user, you will be getting this edit.
So what you need to do, you have to go to permissions.
You have the bucket policy that is visible.
Go ahead and delete the bucket policy and delete it.
Great.
So another bucket policies delete it.
So now from the end user, let's go ahead and refresh the page.
And now you see all the errors.
The URL went away and even if I click on the objects, we are able to see the objects as well.
So this will conclude today's video.