Hear you and welcome back now into this week, you will be discussing about or use in organization now
or you stands for organizational unit and it is basically used to group accounts together and to administer
them in a single unit.
So till now, we have been creating service control policies and we are tightening that a KPIs to our
individual account directly.
Now, when you have organization that has hundreds of endless accounts, it is a little difficult if
you work at the individual account level.
So what you can do with the organizational unit, you can create a group.
So organizational unit is nothing but a group, and within the group you go ahead and add multiple eatables
accounts here and then what you can do the service control policy that you create.
You attach that service control policy to group level or at the organizational unit level.
So this is what it really means.
So once you associate so let's say you have a Denice three in a production or you saw all the accounts
that are part of the production or you will have the three access denied.
So this is what we use that all about.
So let's do one thing before we go ahead and discuss things in more detail.
Let's go ahead and try.
I don't know if you go back to our organization service, you'll see that you have an organizational
structure where everything is under root.
So this is very similar to a Linux based structure if you have worked with the Linux file system, very
similar to that.
So you have root and under root, you have various structure of accounts like auditing testing.
One among them is their management account.
Now, if you want to go ahead and create an organizational unit, you can go ahead and quickly do that.
So let's create a new organizational unit.
Let's call it as production.
And will create new you.
And in a similar way, you can go ahead and create the oil.
Let's call it as developing and let's create.
Oh, you're great.
So now you see you have to or use that data available now, whatever accounts that you have, you can
go ahead and move those accounts.
Let's move our audit account.
To the U.
Of, Let's say, development.
All right.
And now what will happen is any policy that you create, let's try it out.
So we have a service control policies, so any policy that you create, you can attach this policy at
the EU level.
So now you can attach it at the EU level.
In this case, it is development.
So if we look into the targets, the target is the EU.
So any number of con maybe even 50 accounts you have in the EU only account will be associated with
this specific policy.
Great.
So I hope at a high level overview, you understood the basic concept of organizational unit.
Now let's look into some of the important concepts related to organization.
So whenever you go ahead and create a policy, the policy can be applied at the member account level.
We have seen the policies can be applied at the EU level we have already seen, and the policies can
also be applied at the organization you route.
Let's look into it now.
If you look into the service control policy, you have one full IWC access policy now.
If you looking to the target, it is associated with all of the target, including the do now.
When you create the ACP, let's look into the denialists ACP indeed target.
Let's detached from the developmental you.
And when you go in a statute, you can either attach it to her or you live in.
You can either attach it to a specific member account level or you can either attach it to the dead.
So then you do the entire route.
That means it covers all of the organisation unit and its members are gone.
So let's go ahead and attach the policy now.
So if we look into the target, the target is rude.
And if you open up route, it basically gives you the list of all the organization units audio.
All right.
So this is the first concept of policy attachment that you can associated at American or EU level and
even the organization.
Second concept is that the organization unit can also have nested members.
So another or you you can also have a specific nested or you let's look into it now under development
or you, you can also create a new or use area.
So let's create a new organization unit.
And let's call it as payments.
Dev E.W. is I've got let's create the organizational unit.
I know this is that effort as a mistake or you and we didn't state or you can also associate the memorandum
and the policies can also be applied accordingly.
This structure of organizational unique nested 0U really allows you to go ahead and organize things
in a well manner.
No, now for a single account or to either account, it might not really make sense, but for the organization
that has hundreds of accounts, the concept of or use the concept of nested views are very important
and you will be designing that structure whenever you're working in such organizations.
Great.
So before we conclude, let's look into some of the important points.
The first one is that the service control policy don't affect users or roles in the management account.
They affect only their member accounts in your organization.
Very important part to remember.
Second important point is that by default, it is organization attached is a AWG managed policy, coalesce
full eatables access to all the root or use and the accounts.
So this helped ensure that as you build your organization, nothing is blocked until you want it to
be.
Now this is something that we have already seen, whether full idolized access based service control
policy is associated with all the accounts of the organization.
Great.
So I hope with this you understood the basic concept of organizational unit, and with this will conclude
today's video.