Seleziona le tue preferenze relative ai cookie

Utilizziamo cookie essenziali e strumenti simili necessari per fornire il nostro sito e i nostri servizi. Utilizziamo i cookie prestazionali per raccogliere statistiche anonime in modo da poter capire come i clienti utilizzano il nostro sito e apportare miglioramenti. I cookie essenziali non possono essere disattivati, ma puoi fare clic su \"Personalizza\" o \"Rifiuta\" per rifiutare i cookie prestazionali.

Se sei d'accordo, AWS e le terze parti approvate utilizzeranno i cookie anche per fornire utili funzionalità del sito, ricordare le tue preferenze e visualizzare contenuti pertinenti, inclusa la pubblicità pertinente. Per continuare senza accettare questi cookie, fai clic su \"Continua\" o \"Rifiuta\". Per effettuare scelte più dettagliate o saperne di più, fai clic su \"Personalizza\".

Change type schemas

Modalità Focus
Change type schemas - AMS Advanced User Guide
Questa pagina non è tradotta nella tua lingua. Richiedi traduzione

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.

{ "$schema": "http://json-schema.org/draft-04/schema#", "name": "Create CodeDeploy application", "description": "Use to create an AWS CodeDeploy application resource with the specified name.", "type": "object", "properties": { "Description": { "description": "The reason for the request.", "type": "string", "minLength": 1, "maxLength": 500 }, "VpcId": { "description": "ID of the vpc to use, in the form vpc-0123abcd or vpc-01234567890abcdef.", "type": "string", "pattern": "^vpc-[a-z0-9]{8}$" }, "StackTemplateId": { "description": "Must be stm-sft6rv00000000000", "type": "string", "enum": ["stm-sft6rv00000000000"] }, "Name":{ "description": "A name for the stack or stack component; this becomes the Stack Name.", "type": "string", "minLength": 1, "maxLength": 255 }, "Tags": { "description": "Up to seven tags (key/value pairs) to categorize the resource.", "type": "array", "items": { "type": "object", "properties": { "Key": { "type": "string", "minLength": 1, "maxLength": 127 }, "Value": { "type": "string", "minLength": 1, "maxLength": 255 } }, "additionalProperties": false, "required": [ "Key", "Value" ] }, "minItems": 1, "maxItems": 7 }, "TimeoutInMinutes": { "description": "The maximum amount of time, in minutes, to allow for execution of the change. This will not prolong execution, but the RFC fails if the change is not completed in the specified time. Valid values are 60 up to 360, for long-running UserData.", "type": "number", "minimum": 0, "maximum": 60 }, "Parameters": { "description": "Specifications for the stack.", "type": "object", "properties": { "CodeDeployApplicationName": { "description": "The name of an AWS CodeDeploy application.", "type": "string", "minLength": 1, "maxLength": 100, "pattern": "^[a-zA-Z0-9._+=,@-]{1,100}$" } }, "additionalProperties": false, "required": [ "CodeDeployApplicationName" ] } }, "additionalProperties": false, "required": [ "Description", "VpcId", "StackTemplateId", "Name", "TimeoutInMinutes", "Parameters" ] }

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.

PrivacyCondizioni del sitoPreferenze cookie
© 2025, Amazon Web Services, Inc. o società affiliate. Tutti i diritti riservati.