Stack Parameters

Input parameters for a CloudFormation stack are given with the parameters property. It's an object of key-value pairs where the keys are parameter names, and the values are configuration for the parameter value. The value configuration can be a single static value, an object, or a list of the two aforementioned types. The object form is used when the parameter value is resolved at deployment time using a parameter resolver.

Static Parameters

The simplest way to specify the value for a parameter is to hard code the value to the stack configuration file.


A single static value for a parameter named VpcId:

VpcId: vpc-06e4ab6c6c

A list of values for a parameter named CidrBlocs:


Dynamic Parameters

In many cases, it's not wise or even possible to hard code all parameter values. When you need to assign parameter values dynamically at deployment time, you can use parameter resolvers. There are a few built-in parameter resolvers, and you can also implement your own.

You use the resolver property to specify which parameter resolver should be used to resolve the value for a parameter.

Below, you can find some examples of built-in parameter resolvers. In the next section we'll learn more about parameter resolvers.

Example: Reading Value for a Parameter from Another Stack's Outputs

If we have two stacks configured within the same Takomo project, we can use the stack-output resolver to read the first stack's output value and use it as a parameter value in the second stack.

resolver: stack-output
stack: /vpc.yml
output: vpcId

If the stacks are not configured within the same Takomo project, we need to use the external-stack-output resolver.

resolver: external-stack-output
stack: vpc-stack
output: vpcId
region: eu-west-1
commandRole: arn:aws:iam::123456789012:role/deployer

Example: Using Stack Secret as Parameter Value

If our Takomo project contains stack secrets, we can use them as parameter values.

resolver: secret
stack: /rds.yml
secret: password

See Also