Hi, everyone, and welcome back.
Now, in today's video, we are going to discuss about the basics of service quota.
Now, at a high level overview, note that eight of us maintains a list of service quotas for each account
to guarantee the overall availability and also to prevent the accidental provisioning.
For example, let's say a user has created a new account and this account got breached.
The attacker was able to find the access and secret key associated with that account.
Now, through those keys, the attacker tried to launch 100 EC two instances and perform Bitcoin mining
here.
So if there are no restrictions on the account, the attacker will be able to launch 100, 200, 500
big EC, two instances and perform some kind of a Bitcoin mining or other activity.
So in order to prevent that, because in such cases, not only it affects the underlying user whose
account got breached, but it also impacts the availability of the resources.
So in order to overcome this, it maintains service quotas.
Now, generally, if you look into the report of breached accounts to see what exactly attacker tries
to do, one of the common pattern is attacker launches large EC two instances and they do some kind
of a spamming or some kind of a mining activity there.
All right.
So this is where the overall service quota comes into picture.
Now, at a high level overview, you need to note that each service defines its quotas and it has the
default values associated with it.
And depending upon the service, you can increase the quota value.
For example, if you look into this screenshot, you have internet gateways per region.
So the applied quota value is five.
So this means that you will not be able to launch more than five internet gateways per region.
And you also have an adjustable, which is yes, for example, if you want to increase the limit, then
you can raise a request to eight and after evaluation will increase the overall quota for you.
So let's do one thing.
Let's jump into a quick demo to understand things in more detail.
So currently I am in the service quota console and if you see there are multiple set of services, you
have Athena, Dynamo, DB, EBS, VPC, etc. So let's do one thing.
Let's go ahead and explore certain services.
So you see there are a lot of services that are available.
Let's explore the EC two service, so we'll explore the Amazon, EC two over here and here.
Again, depending upon the exact feature, the quota will also change.
Let's look into elastic IP.
So if you see EC two VPC elastic IP, the applied value is five.
So before we proceed further, let's go ahead and see whether this applied quota value really works
or not.
So let's quickly go to the easy to console.
And within your let's go a bit down to the elastic IP.
Let's allocate elastic IP.
This is the number one.
Let's do it a few more times.
This is number two.
Number three.
Number four and number five.
So at this stage you'll see there are five elastic IP's that are created.
So now let's go ahead and try creating one more.
And immediately you see you got an error stating that the maximum number of address has been reached.
All right.
So I hope with this you understood the basics of quota.
The next important thing, let's say the organization genuinely needs more set of elastic IP addresses.
So how can we increase the number of APIs?
So you have to verify from the service quota service whether the adjustable is yes or no.
If it is no, you will not be able to.
If it is yes, then you will be able to increase the limit.
So how do we increase the limit?
You can go ahead and select the appropriate quota name.
You can request the quota increase and within year you can specify how many elastic IP addresses you
need.
So I'll say increase the quota to ten once, then you can request it.
Once you have made a request, you can go to the quota request history.
At this stage you see the status is still pending.
It can take a day or two or sometimes even three four days for the sales team to review, and after
review they will be able to increase the overall quota.
So let me also quickly show you on how exactly it looks once the teams approves it.
So let me go to one more region where I had recently applied for quota increase.
So this is for the Lambda Service.
The quota name is concurrent execution and the status here is closed.
So if you quickly open this up, you will see that the applied quota value was 100.
So earlier the quota associated with concurrent execution was just ten.
So I increase from 10 to 1000 and then you have the request status as close.
So at this stage the applied quota value year is 1000.
So with this will conclude today's video.