Hear you and welcome back now in today's video, we will be discussing about the aid organizations now
at the high level overview aid abuse of in delays, policy based management, as well as the future
of consolidated billing for multiple leaderless accounts through the feature of organization.
So at a high level of what we just know that when we discuss about the aid organization service, there
are two core features of it.
First one is the policies and second one is the consolidated billing.
Now, in fact, in most of the organizations that I have seen, they have the organizations enabling.
Now on top of enabling the organization, which of the features are being used depends the startups.
Generally, they just use consolidated billing.
However, the more mature, security centric organization, they extensively also make use of consolidated
billing, but also the policies based feature.
So let's go ahead and discuss each one of them in more detail.
Now, the first good feature is the consolidated billing.
So in this, a management account is able to access the billing information and also be for all the
member accounts.
So you have one account you can collect as the management account or, in this case, being account.
Now, an organization might have multiple a recurring somewhat organization have more than 100 database
accounts, so it's not like you will be logging into each of those database accounts to look into the
bill, pay the bills and so on.
So that is a bit of a being there.
So what do you do you integrate all of these accounts so that the paying account receives the bill of
all of the other accounts and the paying account or the management account can also pay the bills for
all of them.
So this is what the consolidated billing is all about, and with the help of the Eatables Organization's
consolidated billing is something that can be achieved.
Now, the second very important feature in organization is policies.
So at a high level overview, the policies enables us to apply a new type of management to the eatables
accounts in your organization.
So let's say you have an organization service and there are two accounts that are integrated with the
account and are going to be now from the organization.
You can set a specific set of policies, so for the account you have, a policy call is denied disable
cloud print.
So as the name suggests, it will deny any attempts to disable the cloud service and for the account
to be.
You have denied all SD.
So basically that means no user in the account.
We will be able to access the S3 services.
No, when these policies are applied to the aiders account, even the root user of that account will
not be able to perform that operation.
And this is what organization really offers.
This is a very secure way of writing policies.
So these are the two core features.
Let's do one thing less directly jumping to the demo and understand it in a better way.
Now for today's demo, I have two database accounts open in two different tabs.
The first tab is associated with the management account.
Now, let me also show you that.
So from the management account, if they'll open up the organization's service, we'll look into how
exactly it looks like.
So within it, you'll see that you have an account which is designated as a management account.
So management account is where you go ahead and manage everything, and then you have various other
accounts like you audit account.
Then you have certain accounts that are in a folder like structure here.
So these are basically the member accounts here now from the management account.
So from the management account, you can go ahead and set various policies for audit accounts here.
Now, before we do that, let's look into the first feature of consolidated billing.
So from my management account, let's go to the billing dashboard and let's look into the bill of August
21.
Now you have the Billiat, and the interesting part is details back on and within you.
You see, you're getting details of multiple other accounts.
So the first one is basically our management account and then you're getting the build details of other
accounts that are part of the organization.
So these are all the member accounts of the organization here.
So as we were discussing in the consolidated billing, the management account has the access to the
billing information and can also be the bill of all of the member accounts.
So this is what it really looks like.
The second very important part is the policies.
So let's look into it.
Now, let's go back to the organizations here.
And if you go to police easier, you'll see that I have one very important set of policy that is Enable,
which is service control policy, these are very powerful set of policies.
Now if I leave quickly open this up, you see, I have one policy of denial a street that is created.
So if you look into the policy, you have a night effect.
Action is a street state, a resource is staffed, so all of the street access is denied.
And if we look into the target, the target is an audit account here.
Now, as you're discussing from the management account, you can associate a specific set of policy
to individual accounts.
So for accounting, you can say deny, disable cloud trade for account where you can tell, deny all
history and this is what it really means.
No.
From the second tab, I am logged in as a root user to this audit account, where this specific service
control policy is associated with.
From the root user if they'd try and open up the S3 service.
You see, we're getting a permission denied message audio.
Now, depending upon the use cases, you can write a lot of service control policies and associated
based on the function of a specific database account.
I still remember in one of the organization that I was consulting with.
One of my primary project was the revolving around leaderless organization and in organization.
I did not really work with consolidated billing, but my primary area was writing a service control
policies.
So you can create a great amount of service control policies, organize them based on various organizational
units.
Now again, one important part, specifically when we were writing a service control policies, is that
they have the control to bring down your entire production within just a minute or two.
So you have to be very careful while writing service control policies because once you attach it, the
entire account, including the route user, will not be able to access the service.
Depending upon the condition that you write in the ECB's.
So we have to be very careful while writing this.
So a very interesting feature.
We'll be discussing these things in more detail when the time comes.
However, with this will conclude the basics of the organization service.