Hi, everyone, and welcome back.
Now in today's video, we are going to discuss about the config aggregator.
Now, again, nowadays you will see most of the organizations are based on a multi account based setup.
So when you have hundreds of accounts, you are not going to log into each account and look into the
config rules or config dashboards.
What you need, you need a centralized access where all of the data from other database accounts come
to a single console and this is where the config aggregator comes into picture.
So at a very high level overview, a aggregator is a config resource type that collects the config configuration
and compliance data from following.
First one is multiple accounts and multiple regions.
Second is single account and multiple regions, and it also supports the organization.
So all the accounts that are part of the organization and have the config enabled, you can centralize
the data so this can be better understood with this diagram where in the account C you have the config
aggregator and you have an account A and account B and all of these accounts have the config enabled,
very important part to remember.
And then the data from all of these accounts can be aggregated to a central account.
See where you can run the queries, you can go ahead and look into the compliance status and so on.
All right.
So I hope with this you understood the basics of config aggregator.
So let's go ahead and have a quick demo to understand things in more detail.
Now for today's video, I have an account one in this specific browser, and this is where our config
aggregator is set up.
So if you'll see in the config console, I have an aggregator and the name of the aggregator here is
sample aggregator and there is one account that is associated with it.
Let's quickly open this up.
It is giving us the account ID ending with triple PHI and the status is okay.
So if you look into the account ID of the current account where the aggregator is set up, it ends with
seven, seven, eight, eight.
And I have one more account in a different browser called as a sandbox account.
And this ends with triple file grid.
Now, once you have the aggregator setup, you can go ahead and also explore the resources.
For example, let's go a bit on the lower pages.
You see, you have certain subnets, you have an EC, two instance Internet gateway and so on.
So this specific EC2 instance, it also shows you the account ID which is triple file.
So if I open up this easy to instance, the ID is one, see if it is running in the southeast region.
So let's also verify in our sandbox account.
If we go to the Singapore region, you see we have an instance with the idea of 1cf, All right.
So all of these data and resources you will be able to see from the aggregator point of view as well.
Apart from that, whenever you run the config queries, so there are multiple queries that are available
like active dynamo, DB, count the EC two instance currently running easy to instance and so on.
So when you run these queries, these query also have a query scope.
So in query scope you have this account and region only and you also have the option of aggregator.
So based on the requirements, you can select one among them.
For example, if I just select this account region, you only have one easy to instance that is running.
If I select the sample aggregator again, you have one easy to instance that is running in the southeast
region over here.
Now, one very important part here to remember is that whenever you are setting up the aggregator,
the authorization is very important.
So in the external account, if you need to allow a specified aggregator account to collect your data,
then you have to add the appropriate authorization step.
For example, you're in the sandbox account.
So this is the external account.
You have to authorize the aggregator account to collect your data.
All right.
So this authorization step is quite important.
For example, in the sandbox account, since our aggregator was able to see the resources associated
with the sandbox account, let's quickly go to the config service here.
Now in here, if you quickly look into the authorization, we have authorized an account with seven,
seven, eight, eight account ID to collect the data.
So the overall authorization is very simple.
All you'll have to do is you have to specify the account ID where the aggregator is present and the
appropriate region grid.
So that's a very high level overview about the US config aggregator and with this will conclude today's
video.