And welcome back now in today's we will be discussing about the AWB stacks now in a very simplified
definition, that is a label that you assign to any resource.
So each deck consist of a key and an optional value, both of which customers can define.
So from here, it is a little confusing.
So let's understand this with the simple use case.
So let's say that there are three, two instances that are present from you.
It is very difficult to identify what these two instances are for or for which.
But was this easy?
Two instances are being used.
So what you can do is once a specific label is being assigned to the easy doings things, now you can
quickly identify the true use associated with them.
So this is the reason why bags are very important here.
So let's understand the scene from the EU Council.
So currently you see that there are two easy two instances which are present, but from the name, it
is not very difficult to identify what this instance does.
So it is very important that whenever you learn to easy to instance, you should target.
So let's go ahead and do that.
So I go to the Times and let other tag here.
So I say my name and I said Pimenta.
Well then you can go to inducive and as soon as you take this specific development from the council,
now you see you're able to see that in a similar way.
Let's go ahead and take the second easy to instance.
The tag would be name and the value would be e-mail server once done.
Now you see the name is been populated from the easy to cancel.
So this is what Dag's does at a high level overview.
Now, I'll give you one real world scenario.
Many years back in one of the organization that I was working with, we had more than 200, 300 InSitu
instances.
And what many individuals they used to do is they used to launch Big Easy two instances in production,
but they did not really have any name associated with it.
So when we were working with reducing the overall cost, we had no idea what a specific two instance
did because it did not have any name associated with it.
So that was a very big thing.
So this is the reason why it is very important that you always tag the resources that you get in creating
in the business.
Now, one important part to remember is that a resource can have multiple tags that can be assigned
to it.
So you see that there are two easy to incidents and each instance has two tags which are assigned to
it.
One is the owner, one and second is the stack one.
Now you're the first, but is referred as the key.
And the second part here is therefore as the value.
Now, few more important things that you need to remember for sure is that Aders has hundreds of services
and not all of them support tagging.
This is one important part to remember.
Second important part is that the maximum number of tags, but a source is 50.
And thirdly, important to remember is that the tag, keys and values are keys sensitive.
This is very important.
Now, let me, in fact, show you this.
So let's go ahead and remove this specific tag here.
We have removed this tag and from the console also, you see the name has been removed.
So let me go ahead and add one more time.
I'll call its name and now I'll call it as e-mail server.
All right.
Let's do a C..
So even on a refresh, you see this specific tag is not populated or primarily because of this case
sensitivity area, so that Giesen values are is sensitive since we have a small annoyer.
But on the console it is requiring a capital and this is the reason why it is not being populated.
So as soon as you change it to capital and and you do see you see now it has been populated.
So this is one important part that we need to remember.
Now before we conclude, there are two important use cases associated with tags that we need to remember,
primarily because most of the organizations where will work with these to use cases would be implemented
in some manner.
So the first important use cases associated with billing Sirtex can be integrated in billing, and that
allows customers to understand database enough granularity so they can understand this with a diagram.
So you'll see that you have a total cost and associated with it are certain tags.
Now from here, you can quickly identify that a resource which has these specific tags has consumed
this much amount of cost.
So you have an owner of the.
Admin owner of Systems Engineering and so on.
So from here, you can quickly identify the debridement has this much amount of resources that cost
this much amount of money at the end of the month.
So I'll give you an example, because I used to work in the security team and we used to have a specific
budget in quarter so that budget would include all the resources that we create.
So if we have 10 equal instances that are running as part of it is that the instances should not exceed
the budget that was allocated to the security team and any resource that we used to create in that resource
haddock tag that the owner was the security team.
So the finance team at the end of the day would always verify whether the security team is within their
budget or not.
So this is one important use case.
Now that a lot of interesting stories here.
I'll give you an example, because in security team, there are a few interns who have joined.
And what he has to do is that they used to light the AC two instances for the security team, but they
used to tag a different team together.
So they used to take a of steam within the see two instances.
So at the end of the month, the bill went to the sets of steam instead of the security team.
So a lot of funny things that you will typically see whenever you are implementing that cost the location
tags for the inside of this anyways.
So let's jump into the second important use case for tax.
That is the item.
So tax can be used with IBM to control the access to the resources.
So this can be better explained with this use case here that we only want the user to delete resources,
which has a tag of Yamba's development.
So this can be a typical use case, primarily because you want developer within that development environment
to go ahead and delete their own resources.
However, you do not want that developer to ward and delete the resource which belongs to a different
team.
So this is one important use case where once you have tagged the resources properly, you can go ahead
and write the IBM policy based on that specific tax.
No.
One last important point to remember is that if you're planning to implement types within your organization,
it is important that you follow a target strategy.
So it is important to have a consistent and effective targeted strategy so we can understand the importance
of this with a simple example.
So let's say that Allison Mac, you are within the same team and both of them are creating certain resource.
So this is creating a resource with the tag of key as EMV and the value of production, no matter who's
also creating a resource with the tag of EMV, with a capital E and the value of production with a capital
B..
Now we already know that the tags are case sensitive, and if you have such inconsistencies within the
naming convention, then the overall access control as well as the billing related aspects will be difficult
to manage.
So it is very important that both Alice and Matthew should know that if they have to create a resource,
they should have a proper naming convention where everything is within the small letters.
So any naming convention, depending upon your organization.
So always follow the database tagging strategy document to begin with.
So it has a document of eatables tagging strategies where they have specified their gender based practices
related to how you can go ahead and categorize your resources based on tags and also how tags can be
used for various use cases like you have tags for cost allocation.
This is something that we have seen your tags for automation, you have tags for access, control and
so on.
So before you would create the tagging strategy, go ahead and read this document once because it is
very important for reference purposes.
So that's the high level overview about the tags.
I hope this video has been informative for you and I look forward to seeing the next video.