CreateActivationRequest (p.awso.0.9.1.doc.awso.ssm.Awso_ssm.Values

Sourcetype nonrec t = {

description : ActivationDescription.t option;
(*
A user-defined description of the resource that you want to register with Systems Manager. Don't enter personally identifiable information in this field.
*)
defaultInstanceName : DefaultInstanceName.t option;
(*
The name of the registered, managed node as it will appear in the Amazon Web Services Systems Manager console or when you use the Amazon Web Services command line tools to list Systems Manager resources. Don't enter personally identifiable information in this field.
*)
iamRole : IamRole.t;
(*
The name of the Identity and Access Management (IAM) role that you want to assign to the managed node. This IAM role must provide AssumeRole permissions for the Amazon Web Services Systems Manager service principal ssm.amazonaws.com. For more information, see Create the IAM service role required for Systems Manager in a hybrid and multicloud environments in the Amazon Web Services Systems Manager User Guide. You can't specify an IAM service-linked role for this parameter. You must create a unique role.
*)
registrationLimit : RegistrationLimit.t option;
(*
Specify the maximum number of managed nodes you want to register. The default value is 1.
*)
expirationDate : ExpirationDate.t option;
(*
The date by which this activation request should expire, in timestamp format, such as "2024-07-07T00:00:00". You can specify a date up to 30 days in advance. If you don't provide an expiration date, the activation code expires in 24 hours.
*)
tags : TagList.t option;
(*
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 activation to identify which servers or virtual machines (VMs) in your on-premises environment you intend to activate. In this case, you could specify the following key-value pairs: Key=OS,Value=Windows Key=Environment,Value=Production When you install SSM Agent on your on-premises servers and VMs, you specify an activation ID and code. When you specify the activation ID and code, tags assigned to the activation are automatically applied to the on-premises servers or VMs. You can't add tags to or delete tags from an existing activation. You can tag your on-premises servers, edge devices, and VMs after they connect to Systems Manager for the first time and are assigned a managed node ID. This means they are listed in the Amazon Web Services Systems Manager console with an ID that is prefixed with "mi-". For information about how to add tags to your managed nodes, see AddTagsToResource. For information about how to remove tags from your managed nodes, see RemoveTagsFromResource.
*)
registrationMetadata : RegistrationMetadataList.t option;
(*
Reserved for internal use.
*)

}

Sourceval context_ : string

val make : 
  ?description:??? ->
  ?defaultInstanceName:??? ->
  ?registrationLimit:??? ->
  ?expirationDate:??? ->
  ?tags:??? ->
  ?registrationMetadata:??? ->
  iamRole:IamRole.t ->
  unit ->
  t

Source

val to_value : 
  t ->
  [> `Structure of
       (string
        * [> `Integer of RegistrationLimit.t
          | `List of
            [> `Structure of (string * [> `String of TagKey.t ]) list ] list
          | `String of ActivationDescription.t
          | `Timestamp of ExpirationDate.t ])
         list ]

Sourceval to_query : t -> Awso.Client.Query.t

Sourceval of_xml : Awso.Xml.t -> t

Sourceval of_string : string -> t

Sourceval of_json : Yojson.Safe.t -> t

Sourceval to_json : t -> Yojson.Safe.t