Heroin and welcome back into this video will be discussing about the cloud formation stacks, it's now
in a very simple terms, cloud formation stacks.
It's basically allows us to deploy stacks across multiple eyewitness accounts or even multiple Idalis
region from a single location.
Now, this can be explained with the simple use case that we have over here.
Now, eatables config is basically a good practice to enable it across all the regions, have it in
order to enable it across all the regions.
Specifically, if you're doing from cloud formation, you had to maintain a stack across each and every
region and that that used to enable Aders config.
So there are 10 adris regions.
You have to maintain 10 individual stacks of your cloud formation.
Now the desert becomes tiresome, specifically if you have multiple accounts.
So what cloud formation came up with?
It came up with the feature of Stack Set, which basically allows us to deploy stacks like now what
do you do?
You just create a stack set and you deploy stack set across all the region and you just have one central
place from which you can push the stack so it becomes much more easier.
So let's do one thing.
Let me show you the demo so that it becomes easier for us to understand here.
Now, I'm in my cloud formation console now within a year, if I go to Stax, it's currently you see,
I have one stack set which is available here.
So this is the stakes right now with this, there is a called stack instances.
This basically means to which regions or to which AWB accounts the current stack has been pushed into.
So currently my stack has been pushed into a single account.
You see the account I receive, however, it has been pushed to multiple regions.
You have us with one.
You had you with three, you have a B ne two.
So these are the multiple AWB regions where your stack has been pushed into.
So let's say that if you want to enable AWB config across all the regions of your account, you can
just create a stack sick and you have a cloud formation template.
You just push your cloud formation template through stack sets to all the database regions.
So now to understand it in a better way, let's do one thing.
Let me go to cloud three and go to the cloud console, because this specific that enables cloud three
across multiple region.
So when I deployed it, what it did was it enabled cloud across the Northeast to us to three as well
as US West.
One reason I could have done all the region, but I'm just using the minimal one that is required for
the demo purposes now within the cloud.
Let me go to the Paris one.
So within Paris, if I go to trend, I have the trains which are created or, you know, within the
Paris when if you basically look into the cloud formation, let's go to cloud formation.
What this tax does is that if you see there are three regions, it basically it has a stack deployed
across all of these three regions.
So this part that you see all year, this is basically a stack.
Now, this stack interns basically create the required resources.
In our case, it created a tree, it created a trail bucket, and it created a trail bucket policy within
the Paris region.
And as similar for all the other regions where you are pushing now in order to verify how exactly this
works, what we do is we terminate this specific tax.
So I'll go to actions.
I click on delete stack from stack set.
So let me do it.
Delete stack from stacks.
Now you have to specify the account number over here, so I'll give this specific account number.
Basically, we already discussed that stack.
It allows us to deploy across multiple established accounts.
So in case you have your stacks like this which have been deployed to a destination account, you can
specify the area.
Now that you have put it, you have to specify the region.
Currently, only three regions would appear because your stack have been deployed through stack set
from only three regions.
So I just select all the three regions here.
So you're not California SEAL and Battis.
I'll do a next.
Let me do a submit so I know what it is doing it.
It is basically deleting it.
So whatever stats that were created across all of these regions, those tax would be deleted.
And in turn whatever resources which were created through those tags will also be deleted.
So we will quickly see.
Great.
So currently our operation is succeeded.
Now, if you go into stack instances, let me just quickly do a refresh.
Currently, there are no static instances.
So basically all the stacks which were deployed at their destination account, destination region have
been deleted now within the cloud formation.
Also, if you look into the Paris region, you see there are no stacks which are available.
So this is the high level overview about what we do.
I hope you understood on Wattstax.
It allows us to do not only it allows us to deploy our stack across multiple regions, but it also allows
us to deploy our stacks across multiple A.W. seconds.
And at this central place where you manage everything, it really becomes much more simpler for the
administrator.
So this is it about today's video.
I hope this has been informative and I look forward to seeing the next video.