Struct aws_sdk_ssm::input::CreateDocumentInput
source · [−]#[non_exhaustive]pub struct CreateDocumentInput {
pub content: Option<String>,
pub requires: Option<Vec<DocumentRequires>>,
pub attachments: Option<Vec<AttachmentsSource>>,
pub name: Option<String>,
pub display_name: Option<String>,
pub version_name: Option<String>,
pub document_type: Option<DocumentType>,
pub document_format: Option<DocumentFormat>,
pub target_type: Option<String>,
pub tags: Option<Vec<Tag>>,
}
Fields (Non-exhaustive)
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.content: Option<String>
The content for the new SSM document in JSON or YAML format. We recommend storing the contents for your new document in an external JSON or YAML file and referencing the file in a command.
For examples, see the following topics in the Amazon Web Services Systems Manager User Guide.
requires: Option<Vec<DocumentRequires>>
A list of SSM documents required by a document. This parameter is used exclusively by AppConfig. When a user creates an AppConfig configuration in an SSM document, the user must also specify a required document for validation purposes. In this case, an ApplicationConfiguration
document requires an ApplicationConfigurationSchema
document for validation purposes. For more information, see What is AppConfig? in the AppConfig User Guide.
attachments: Option<Vec<AttachmentsSource>>
A list of key-value pairs that describe attachments to a version of a document.
name: Option<String>
A name for the SSM document.
You can't use the following strings as document name prefixes. These are reserved by Amazon Web Services for use as document name prefixes:
-
aws-
-
amazon
-
amzn
display_name: Option<String>
An optional field where you can specify a friendly name for the SSM document. This value can differ for each version of the document. You can update this value at a later time using the UpdateDocument
operation.
version_name: Option<String>
An optional field specifying the version of the artifact you are creating with the document. For example, "Release 12, Update 6". This value is unique across all versions of a document, and can't be changed.
document_type: Option<DocumentType>
The type of document to create.
document_format: Option<DocumentFormat>
Specify the document format for the request. The document format can be JSON, YAML, or TEXT. JSON is the default format.
target_type: Option<String>
Specify a target type to define the kinds of resources the document can run on. For example, to run a document on EC2 instances, specify the following value: /AWS::EC2::Instance
. If you specify a value of '/' the document can run on all types of resources. If you don't specify a value, the document can't run on any resources. For a list of valid resource types, see Amazon Web Services resource and property types reference in the CloudFormation User Guide.
Optional metadata that you assign to a resource. Tags enable you to categorize a resource in different ways, such as by purpose, owner, or environment. For example, you might want to tag an SSM document to identify the types of targets or the environment where it will run. In this case, you could specify the following key-value pairs:
-
Key=OS,Value=Windows
-
Key=Environment,Value=Production
To add tags to an existing SSM document, use the AddTagsToResource
operation.
Implementations
pub async fn make_operation(
&self,
_config: &Config
) -> Result<Operation<CreateDocument, AwsErrorRetryPolicy>, BuildError>
pub async fn make_operation(
&self,
_config: &Config
) -> Result<Operation<CreateDocument, AwsErrorRetryPolicy>, BuildError>
Consumes the builder and constructs an Operation<CreateDocument
>
Creates a new builder-style object to manufacture CreateDocumentInput
The content for the new SSM document in JSON or YAML format. We recommend storing the contents for your new document in an external JSON or YAML file and referencing the file in a command.
For examples, see the following topics in the Amazon Web Services Systems Manager User Guide.
A list of SSM documents required by a document. This parameter is used exclusively by AppConfig. When a user creates an AppConfig configuration in an SSM document, the user must also specify a required document for validation purposes. In this case, an ApplicationConfiguration
document requires an ApplicationConfigurationSchema
document for validation purposes. For more information, see What is AppConfig? in the AppConfig User Guide.
A list of key-value pairs that describe attachments to a version of a document.
A name for the SSM document.
You can't use the following strings as document name prefixes. These are reserved by Amazon Web Services for use as document name prefixes:
-
aws-
-
amazon
-
amzn
An optional field where you can specify a friendly name for the SSM document. This value can differ for each version of the document. You can update this value at a later time using the UpdateDocument
operation.
An optional field specifying the version of the artifact you are creating with the document. For example, "Release 12, Update 6". This value is unique across all versions of a document, and can't be changed.
The type of document to create.
Specify the document format for the request. The document format can be JSON, YAML, or TEXT. JSON is the default format.
Specify a target type to define the kinds of resources the document can run on. For example, to run a document on EC2 instances, specify the following value: /AWS::EC2::Instance
. If you specify a value of '/' the document can run on all types of resources. If you don't specify a value, the document can't run on any resources. For a list of valid resource types, see Amazon Web Services resource and property types reference in the CloudFormation User Guide.
Optional metadata that you assign to a resource. Tags enable you to categorize a resource in different ways, such as by purpose, owner, or environment. For example, you might want to tag an SSM document to identify the types of targets or the environment where it will run. In this case, you could specify the following key-value pairs:
-
Key=OS,Value=Windows
-
Key=Environment,Value=Production
To add tags to an existing SSM document, use the AddTagsToResource
operation.
Trait Implementations
This method tests for self
and other
values to be equal, and is used
by ==
. Read more
This method tests for !=
.
Auto Trait Implementations
impl RefUnwindSafe for CreateDocumentInput
impl Send for CreateDocumentInput
impl Sync for CreateDocumentInput
impl Unpin for CreateDocumentInput
impl UnwindSafe for CreateDocumentInput
Blanket Implementations
Mutably borrows from an owned value. Read more
Attaches the provided Subscriber
to this type, returning a
WithDispatch
wrapper. Read more
Attaches the current default Subscriber
to this type, returning a
WithDispatch
wrapper. Read more