All change types provide a JSON schema for your input in the creation, modification, or access, of resources. The schema provides the parameters, and their descriptions, for you to create a request for change (RFC).
The successful execution of an RFC results in execution output. For provisioning RFCs, the execution output includes a "stack_id" that represents the stack in CloudFormation and can be searched in the CloudFormation console. The execution output sometimes includes output of the ID of the instance created and that ID can be used to search for the instance in the corresponding AWS console. For example, the Create ELB CT execution output includes a "stack_id" that is searchable in CloudFormation and outputs a key=ELB value=<stack-xxxx> that is searchable in the Amazon EC2 console for Elastic Load Balancing.
Let's examine a CT schema. This is the schema for CodeDeploy Application Create, a fairly small schema.
Some schemas have very large Parameter
areas.
|
The first part of the schema provides information to AMS about the requested change type.
|
The TimeoutInMinutes parameter allows you to indicate a boundary time for running the change type. Valid values are 60 up to 360, for long-running UserData.
| |
The Parameters section is where you specify settings for the resource you are creating, or the action you are requesting.
| |
The "additional properties" sections let you know what parameters are required and which are optional. |
Note
This schema allows up to seven tags; however, EC2, EFS, RDS, and the multi-tier create schemas allow up to 50 tags.