So from a complete anatomy, we have already used resources.
And we have used also mappings now in this video, we're going to talk about parameters, value creating,
cloud formation stack, you see parameters option there.
We'll see in this video how we can give you the power of entering some parameters so it can be used
to parameters keeper and the instance type.
So let's go to templated anatomy parameters.
Defining parameters in a template.
So the parameters, the section logical body type string, there are a few other types will see that
also default against the default value.
If a user does not provide anything, it's going to take that default value.
So, for example, here to do microinsurance type.
You can give the allowed Valena list format cap, so if you give this parameter allowed values and you
give the list of allowed values, you'll get a dropdown over order.
Let's see the other properties.
Allowed values and array containing a list of values which will create a dropdown constrained description
default the following year, can your description maximum length, maximum value, minimum length,
you can mention all that, no echo.
If you're taking secret data like passwords, you would like to not print that when the user is typing
so you can put a Neuk or their.
So there are different types, you have string, you can take no as an input list, it's an array of
individual floats.
Established specific parameters type, you can also point user to an established parameter, like,
for example, existing Kebir so you can listed Siletz created with specific parameters type.
So we're going to create a keeper list.
So instant's IDs, it's going to list all the instance ID available.
Keep in, OK, if you use this, then the user will get the list of existing keys, and for that we
really need to create a key.
So let's go to our.
Console.
I'm in Ireland region.
And I'll prepare a few things before I create the stack, first, I'll go to the keeper and let's create
some key.
I will name it as the profile hyphen ki.
And format and I will create keeper so the public is downloaded and I'll give user the list of the keys.
Let's get a few more key.
I will see.
You, Witwicky.
That's fine, you should be fine so we can get the list of these two guys.
OK, now let's write our template.
Will name it as input parameters.
Dr. Weinmann.
Copy everything from the previous template.
As it is.
And just about this, I'll put parameters, so I'll go to the documentation.
Take an example from here.
This one.
List of incidents die.
Let's put their.
And I'll keep it as it is, I want to give you want to add more list like I.
Let's do one more city to dot small.
Also give to dot medium.
OK, that's one parameter, we'll get a drop down list there.
That's correct.
One more parameter.
And we'll see key neame, that's the logical Odey You can give anything, I'll give some description.
And I want the list of all the available keys so I can type.
It's called the documentation parameters.
So now the commission is going to access the existing parameter, we should all the list of keys available
in that particular region.
Also, I would like to refer these things in my instance profile, in my instance resource.
So instanced type.
Now I'm going to refer Zaref.
And.
Let's get the logic, logical lady instanced type parameter.
Also the key.
So key name.
And referring it to.
That's the logical idea of giving the same logic, a very similar name, but it's a lot this is a logical
area and this is a property, for instance.
Two different things.
OK, I will give one more parameter, which I'll put it in the tag.
It's a simple one, just name of service, description, strength, so user will see this and use it
if want can make change also to this annual reference in the tag.
Name.
So instead of using this, join.
I would say, Jeff.
Nima Service.
And everything else I'll keep as it is.
For mapping, I am creating instance in Ireland region, so I have to give that regional's over here.
So you you w one.
OK, let's launch Instant's and get an Amedee for Amazon Linux.
You won.
Let's create entry for that new hyphen, West IFN one my.
This seems good.
Let's go over once again parameters, I have three parameters, Nemov service, instanced type parameter
and Quini, they are all three different parameters.
This is just going to give a description.
So if a user wants user can change that also while creating instant type parameter again feedstuff type
string, but we have given a value, so we'll get a dropdown list of our entries.
Quini, this will also give dropdown list, but this will check the existing parameter.
Kenin.
OK, so here parameters are predefined by us here.
Parameters are defined by A.W. this.
Then we are mapping.
Based on a region name, it's going to pick up the mapping and in the instance we are referring to all
the parameters that we have defined, instanced type, key name.
And in the name of service.
And then we have the security group that you are referring here, which is seen from the previous video.
OK, let's do this, so let's go to confirmation.
Creates Jack.
Upload my template Chew's file.
Input parameter.
OK, let's go next.
Right now, we have the parameter let's let's give a name for input IFN parameters, for example.
OK, now you have the parameters dropdown list, see that P2 microdata small we can select, it's what
we have defined in our template.
Kinniburgh, this eatables is fetching for us.
We are Tukey I'm going to say I'm going to select Diski name of service if I want, I can make change
otherwise it will keep.
And they will not be anything, so let's use some name and put hyphen parameter an example.
I'm a spelling mistake.
OK, so three different parameters for next.
Next.
And creates Jack.
Excluding everything.
Let's check.
OK, so we have the instance, and that's the first parameter that we are seeing, we're here to do
micro.
That was also the parameter and the key.
Let's check the key.
The icky, so all these three parameters were taken successfully, all these three parameters of a different
style formation stack should be completed by now.
Yes, it's completed.
Let's quickly reiterate what we did.
We started now using parameters, which is optional, but can turn out to be very beneficial.
The examples over here in the documentation, which is easy to pick up.
So in our template, we have taken this, we have given three parameters, one, which is string parameter
that the user can type either parameter, which creates a dropdown list of our defined values.
Third parameter kini, this is going to create a dropdown list.
Which IWC will fetch the properties parameters for us and then we refer it in our instance by using
a raft function and we give the logical idea of the parameter.
So if you're done doing this, you can delete your stack.
And join me in the next video where we're going to see how to print Output's.