Hey, John, and welcome back now in the earlier video, we were exploring about the basics of a dabblers
convict, we look into various features that it has to offer related to the resource configuration changes
related to the auditing complaint and related to the conformance back.
So in today's video, we'll go ahead and implement these features from scratch so that we understand
the exact steps that are required in production environments.
Now currently in the easy to dashboard and we'll be creating two resources.
Your first one would be the instance and second one would be the security group.
So let's go ahead and quickly launch an instance.
You will be using the Amazon Linux EMR.
And the intense type you can use anyone that supports the freakier eligible in this case, it is B 3.0
micro once, then you can go ahead and do a review and launch.
And let's do a launch in terms of keeping if you have a keeper, you can select it.
If you do not have a keeper, you can select proceed without the keeper.
And on the instance.
That's great.
So are instances now running?
Let's go ahead and click here.
So this is the first part.
Let's go ahead and create a security group.
Let's just call it as config hyphen Høst.
And within the rules, we just use a default one where there are no rules and you have one in outbound
rule over here.
Let's go out and create a security group.
So these are the basic configurations of the resources that are running.
So now at this stage, let's go ahead and enable the eatables config.
Now, within you, you can either click on get static or from the left hand side as well, you can go
ahead and set up the config.
Let's keep it simple.
Let's get started here.
So under general setting, you can either record all the resources that are supporting or if you do
not want that, you can also go ahead and select a specific resource that you intend to monitor.
To keep it simple, let's use the default settings audio and in the delivery method where the logs will
be stored.
You can go ahead and create a bucket.
You can just give it a random name.
I hope this name is not taken and let's just call it as best I can confirm once then again, since S3
namespace is global, you need to have a unique MEMORIA.
Let's click on next.
The step two is related to the managed rules.
Again, there are a lot of Manege rules that are available.
We'll skip it as of now.
We'll be discussing this in more detail in the upcoming steps.
Let's click on Next and will do again for.
That's great.
So now at this stage, under the resource inventory, you see it states that your resources are being
discovered now depending upon the resources that are part of this specific region, the amount of time
that it generally takes would also differ, certainly this time when the resources are being discovered.
Let's go ahead and explore the feature related to the dabblers config rules that helps in the overall
audit and compliance.
Now, under the rules, currently, there are no rules that are added.
So let's go ahead and add a new rule.
Now, again, there are established managed rules that are available.
If there is a use case where the established managed rule is not available, then you can also go ahead
and create a custom rule here.
So we'll be using the simply the list managed rule to keep things simple as of now.
And the one that we're interested in is the approved Ismay's varieties.
So what this will do is it will take the easy to instance to verify, for instance, is running from
a specific Imai.
If it is not, then it will be reported.
So this is an interesting one and a useful one for production environment as well.
So generally, what do you specify, the email, the search and the production environment, what happens
is there is a hard on the email and all the individuals who are planning to create a Ekta instance,
they are supposed to create it from a hardened image.
So what we be doing is let's assume that we had an email.
It is in my iPhone one, two, three, four, five.
So this is the security had an email that is created by the security and this configurability we two
instances.
And if these two instances are being launched on this hardened Aimi, if not, then it was reported.
So that is the basic skills that we want to achieve.
So let's click on Next.
It will give you a review screen and Les Gordon and.
That's great.
So this is the first rule that has been added.
Let's go to the Dysport.
So currently you'll see that the compliance status is zero zero zero zero.
So do know that this country will not give you a real time B statistics.
It takes a little amount of time for it to audit a year.
So, again, under the noncompliant rule, there are no non-compliant rules that are available.
However, once it goes ahead and verifies, the resources are easy to understand.
Since it was not launched on the security team, it should come under that non-compliant status.
So this is associated with audit and compliance.
So if you look into the screenshot or you're under the noncompliance, you see there are a lot of non-compliant
rules and similarly are in management that we have created that should also be under the noncompliance.
The second important features is associated with the conformance back as we're discussing conformance
back is basically a collection of eatables config rules that allows you to achieve a specific use case.
For example, let's go to the conformance back.
So currently there are no conformance back that are available.
Let's deploy conformance back from a sample template.
Now, again, there are a lot of templates that are available.
So let's say that you are planning for Picards compliant infrastructure so you can go ahead and select
the conformance back of Arkadiusz directly.
So depending upon the use case, you can use one among them for simplicity.
Let's go ahead and use the operational best practices for the identity and access management.
Let's go ahead and do a next under the name.
I'll just say I am conferment.
Let's do a next and we'll go ahead and deploy this conformance back.
That's great.
So our deployment of our conformance back is completed, so let's go back to the dashboard and within
the dashboard now, you'll see that under the noncompliant rules are approved, Amys by idee is under
the noncompliance status.
In fact, it will go to the rules.
Aurier, you should see that there are multiple rules that are available.
So except this approved in May by all of the rules that we have are part of the conformance back itself.
Now let's look into the approved EMH idea and within a year you see that there is one instance and that
actually is under the noncompliance status.
And it also gives you the instance ID and various other details related to it, like the air in the
IP address of the two instance, the launch time and the Amadie from which it was launched.
So this is quite helpful.
Now let's go back to the dashboard and also under the resource inventory, you see, it was able to
detect a lot of resources that was associated with this specific regional security group roundtables
and so on.
Now, at this specific speed, let's take an example of easy instance.
So currently it is showing you the easy to instincts.
And under the resource timeline, you will see that you have a cloud trail event associated with that
and instances primarily because we have created a new instance here.
Apart from that, there are no other primary events that are available.
So let's do some modification.
Let's go to the.
Let's go to the instances.
Will go ahead.
And will stop this instance.
All right, so are instances now stop and let's also go.
Let's do it right click and change the instant state from thirty three, micro to be three.
Once that will go ahead and start the instance again.
That's great.
So this is the first change, the next change.
Let's go to the security group and within the config security group that we have available.
Let's go ahead and add a new rule.
On the board of 22 and we just do a little 0002 Let's do a safe.
And also, there was one outbound rule that was created earlier.
Let's go ahead and also delete this specific rule.
That's great.
So after the eatables config has been enabled, we modified multiple resources, Aurier, and the same
can be reflected at the config level as well.
So let's go to the config.
Now, one important part to remember specifically working with conflict again, is that the changes
that you will see are not directly a realtime one.
So let me give you an example.
So let's go to the Ekta instance.
Let's open up that resource, identify.
Now, if you'll click on the resource timeline here, you'll only see the one that was associated with
the event when we had started the instance here.
So since we have perform a modification just a few seconds back, it takes a little amount of time for
the config to go ahead and read in the scan to detect the new event, and then it will add it under
the UN's section here.
So let's do one thing.
Let's go ahead and pause this we do for a few minutes and we'll be back once the resources are updated.
All right.
So it has been a few minutes.
And if you see our new configurations have been detected now, let's look into it.
So you have a cloud event of certain instances, then you have cloud event of stop instances, and then
you should also have a cloud event of modifying instance attribute.
So this is where we change the instance from microtonal.
Apart from that, you also have one more cloud relieved of state instances.
So just from analyzing the cloud event associated under the resource timeline, it is easier for us
to understand on what might have happened or to the specific resource.
Along with that configuration changes something that is unique to the established config where it shows
on what was the earlier configuration, including the public IP address associated with AC2 instance.
So to know that this is a public IP and this will change after you stop and start the instance, and
hence it is showing you what was the public IP, which was dead earlier.
Now, since we stopped and started the instant the public eye became so filthy, 79 that 66 to 200 or
253 and now it is giving you the latest configuration associated with the instances.
Now, along with that, it is also showing you if you look on the left, you have a configuration incense
type of A3 micro and the configuration instanced type of T3 dot nano.
So this is the one associated with the EU.
Now let's go back to the dashboard here.
Let's open up the security group.
So there are multiple security groups that are available.
Let's verify the I.D., so let's go to AC2.
Under the security group, here are configures.
He has the idea of two one seven, so this is the security group.
So here we have the security group ending with two one seven Wadena.
Let's go to the Resource Tamlin.
And again, you'll see a combination of Cloud Treliving and the configuration team.
So the first cloud relevant is when we went ahead and created a security group, second one where we
added a specific ingress rule and 31 is where we went ahead and removed the outbound rules.
And if you would like to look into the configuration changes here on the left hand side, you will see
greater increases associated with the outbound.
So it is showing that there was a specific outbound rule of zero zero zero zero which was removed.
And there is also one more rule that is available.
And that rule is a rule for the SSA sport, which is both 22 and the C++ is zero zero zero zero.
That's great.
So at a high level overview, I hope you understood the basics of eatables config and also the associated
features.
Now, again, after you have completed the testing, you can go ahead and switch off the recorder status
here.
So let's click on EDIT.
You can go ahead and select the enabled recording part.
And you can go ahead and see if that changes, so this will ensure that you do not really have any unexpected
cost and along with that, all the rules that you have created.
Let me also show you so if you go to the conformists back, you can go ahead and delete the conformance
back.
Let's go ahead and type delete.
So when you go to the rules or you you should see all the rules associated with the conformance, Bakari,
and for the rule that we have created.
Let's go ahead and delete the rule.
Let's press delete.
So at this stage, it will not really give you any information whether the deletion is in process or
not.
This is a little confusing.
Let's go ahead and refresh the page.
And now you see the rule no longer exist.
That's great.
So this will conclude today's video.