Here and welcome back now in the early we do, we were discussing about the overview about Steiglitz,
we also had a demo on what exactly success might look like.
So into this video, we'll go ahead and we'll create our own statistic and we'll look into what are
the steps that are required for configuring Woodstock's it.
Now, I have created a slide which basically states deployment instruction.
Now, what you need to do is that there are two AM rules which are required.
One rule would be for the administrator account where your tax rate would be created and one rule would
be for their destination account.
So let's say you have multiple A.W. account and the account where you will be centrally managing your
taxes.
So there'll be one rule that would be required and the rule naem there should be a dabblers cloud formation
stack set administrator rules.
So this name convention is something that you cannot change.
So you need to have the exactly the same.
And one for the destination account where the tax would be created.
So in the destination account you need to have a roll call database, cloud formations that set execution.
So for our example purposes, we'll be having both of these rules within the same account because a
lot of people might not have multiple accounts.
I'll just show you how we can do that within this e-mail account as well.
So let's go to cloud formation and I'll go to success.
So this was the most access that we had created.
Let's create a new stack so you can either use your own template here or you can use the simple template.
Now for the simple template.
You have a very simple template which are available related to config, related to cloud trail.
Let's select enable list cloud.
So this template basically enables the cloud.
Now let's click on Next.
Let's give it a.
I'll say loud, real stacks, it's practical right now, we lead this barometer to default once I click
on Next.
Now within the permission, basically, it is asking you for permission.
So this is the Iame rule that you have to create.
So we discussed that there are two things that we need to create.
One.
The one is the AM.
For one is Dianabol for a destination account.
So let's go ahead and create the Ambros.
So within my am I go to rules, I click on create rules.
So this rule, the first rule that will be doing is that it would be besoin administrator.
So I just select cloud formation here.
Let me click on next.
I'll just ignore setting up the policies.
Let's just create the rule so you need to give the rule name.
Let me copy the ruling, I'll post it over here and we can go ahead and create a rule on it.
So this is a first rule.
Let's create one more rule.
This thing, it would be based on another eyewitness account, Doriot, because of that rule, would
be at their destination site.
So we need to basically enable that trust policy.
So you have to specify the accountability.
Now, in my case, I already have the account.
So this is the account of my current account where we are doing the practical I will select next.
And this time I'll be administrator access to it.
Let's give the ruling.
And I'll go ahead and create a rule.
So the reason why we added administrator access here is because from the central account, if your state
is creating easy instance or if your state is creating a VPC, you do not really know.
And this is the reason why we have created administrator access audio for demo purposes.
Great.
So now let's go back to roll and we'll go to the rule.
Which states establish cloud formations tax administrator know within.
You basically need to add a policy asset in line policy.
Let me open up a Dewson and within the Mainard, but I already have a sample policy which is created
Audur.
I'll be sharing it after this video so that you can directly use it.
So this is the policy that you need to set.
You can do a review and will go and create policy and state based policy.
I would do a great policy.
Great.
So now we have both the rules which are created in case you have multiple Idalis account, then your
the state execution would be created in that destination.
A.W. Sakar.
Anyways, so let's come back to the cloud formations that.
Now, within, you will select the eatables cloud formations to accept Administrator A.
This is the rule and the IAM execution drolly is the rule.
That is the final word here.
Let's click on next.
No, it is basically asking to deploy stacking again.
So if you have multiple idalis accounts where your eatables cloud formation stack set execution roll
is already created, you can specify your account.
It is Aurier.
Now, in my case, I already have my account.
So this is the current account where we are doing the practical.
I just put it, you know, you have to specify the region where you want your template to be deployed
to.
So for the region, let me select Mumbai, let's select Ireland and let select Tokyo.
You can select multiple regions as well and we can go ahead and we can do a next.
So basically, these regions that you have created, this is where our cloud formations stack would
be deployed.
The stack said that we are creating.
Let me do a next and let's go ahead and let's click on Submit.
Great.
So currently it is running.
Now, if you look into the stack instances, it basically says the status as outdated.
Now, this status would change as soon as the cloud formations stack is deployed across the destination
region and the resources are created.
Now, one of the regions that we had selected was Mumbai.
So let's go to Mumbai.
So within the Mumbai, you see your stack creation is in process.
So the creative process.
So now what Wattstax set has done, it has deployed the three stacks across three regions, which is
northeast one, south one, and you waste one.
And this individual stack will create the appropriate resources, which are part of this simple template
that we were using.
So now as we refresh so we can now conclude that it was deployed in the south one region, which is
Mumbai, and if we just refresh the Mumbai region, you see the create complete is the status.
And this is the reason why your state has this current.
Now, as soon as the tax sets.
Deploys the appropriate STAC, both of these would also turn into crime.
So let's quickly wait for a moment.
Great.
So now our staff is deployed across all the three regions.
And basically we already discussed that the art stack is created in the Mumbai region.
Now, if you want to verify, you can go to cloud drill selected trails.
And you have your stocks that have gone global.
So this was the trail which was created.
So this is the high level of your view about stocks?
It's I hope from now you started to understand the idea about taxes and what is the flexibility and
how it allows you to deploy, create, as well as delete this tax from this central account.
Now, in case, if you want to delete this, you can go to actions and you can delete the stacks from
Stacks said, let's click here.
You again will have to deploy and you have to specify the account number.
So basically, let's say you have deployed Glau Trillion five accounts and now you want to delete the
cloud in one account.
So you have to specify the account number here.
So I specified the account number here.
Now you have to specify the region.
It will only show you the regions where it was deployed to.
You can go ahead and you can do a next.
And let's click on Submit.
So the earlier type was create this type operation is delete.
So let's quickly wait for a moment for this to be deleted.
Great.
So the status is now showing us succeeded.
If you go to stack instances, you should typically see that there are no static instances.
And from cloud formation, let me click and refresh.
You should see that the stack is now deleted and from the cloud trail as well.
Let's click on Refresh.
You should see that it is deleted.
So once you have done that, in case if you want to delete the stack set, you can go to action, click
on delete stacks and stacks.
It is also deleted.
So this is the high level overview about the cloud formation stack set.
In terms of the practicality aspect, I hope this video has been informative for you and I look forward
to seeing the next video.