aws-sdk 2.990.0 → 2.994.0

package/clients/imagebuilder.d.ts

@@ -100,11 +100,11 @@ declare class Imagebuilder extends Service {
    */
   deleteDistributionConfiguration(callback?: (err: AWSError, data: Imagebuilder.Types.DeleteDistributionConfigurationResponse) => void): Request<Imagebuilder.Types.DeleteDistributionConfigurationResponse, AWSError>;
   /**
-   *  Deletes an image.
+   * Deletes an Image Builder image resource. This does not delete any EC2 AMIs or ECR container images that are created during the image build process. You must clean those up separately, using the appropriate Amazon EC2 or Amazon ECR console actions, or API or CLI commands.   To deregister an EC2 Linux AMI, see Deregister your Linux AMI in the  Amazon EC2 User Guide .   To deregister an EC2 Windows AMI, see Deregister your Windows AMI in the  Amazon EC2 Windows Guide .   To delete a container image from Amazon ECR, see Deleting an image in the Amazon ECR User Guide.  
    */
   deleteImage(params: Imagebuilder.Types.DeleteImageRequest, callback?: (err: AWSError, data: Imagebuilder.Types.DeleteImageResponse) => void): Request<Imagebuilder.Types.DeleteImageResponse, AWSError>;
   /**
-   *  Deletes an image.
+   * Deletes an Image Builder image resource. This does not delete any EC2 AMIs or ECR container images that are created during the image build process. You must clean those up separately, using the appropriate Amazon EC2 or Amazon ECR console actions, or API or CLI commands.   To deregister an EC2 Linux AMI, see Deregister your Linux AMI in the  Amazon EC2 User Guide .   To deregister an EC2 Windows AMI, see Deregister your Windows AMI in the  Amazon EC2 Windows Guide .   To delete a container image from Amazon ECR, see Deleting an image in the Amazon ECR User Guide.  
    */
   deleteImage(callback?: (err: AWSError, data: Imagebuilder.Types.DeleteImageResponse) => void): Request<Imagebuilder.Types.DeleteImageResponse, AWSError>;
   /**
@@ -228,19 +228,19 @@ declare class Imagebuilder extends Service {
    */
   importComponent(callback?: (err: AWSError, data: Imagebuilder.Types.ImportComponentResponse) => void): Request<Imagebuilder.Types.ImportComponentResponse, AWSError>;
   /**
-   *  Returns the list of component build versions for the specified semantic version.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: When you retrieve or reference a resource with a semantic version, you can use wildcards (x) to filter your results. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. For example, specifying "1.2.x", or "1.x.x" works to filter list results, but neither "1.x.2", nor "x.2.x" will work. You do not have to specify the build - Image Builder automatically uses a wildcard for that, if applicable. 
+   *  Returns the list of component build versions for the specified semantic version.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: With semantic versioning, you have the flexibility to use wildcards (x) to specify the most recent versions or nodes when selecting the source image or components for your recipe. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. 
    */
   listComponentBuildVersions(params: Imagebuilder.Types.ListComponentBuildVersionsRequest, callback?: (err: AWSError, data: Imagebuilder.Types.ListComponentBuildVersionsResponse) => void): Request<Imagebuilder.Types.ListComponentBuildVersionsResponse, AWSError>;
   /**
-   *  Returns the list of component build versions for the specified semantic version.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: When you retrieve or reference a resource with a semantic version, you can use wildcards (x) to filter your results. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. For example, specifying "1.2.x", or "1.x.x" works to filter list results, but neither "1.x.2", nor "x.2.x" will work. You do not have to specify the build - Image Builder automatically uses a wildcard for that, if applicable. 
+   *  Returns the list of component build versions for the specified semantic version.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: With semantic versioning, you have the flexibility to use wildcards (x) to specify the most recent versions or nodes when selecting the source image or components for your recipe. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. 
    */
   listComponentBuildVersions(callback?: (err: AWSError, data: Imagebuilder.Types.ListComponentBuildVersionsResponse) => void): Request<Imagebuilder.Types.ListComponentBuildVersionsResponse, AWSError>;
   /**
-   * Returns the list of component build versions for the specified semantic version.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: When you retrieve or reference a resource with a semantic version, you can use wildcards (x) to filter your results. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. For example, specifying "1.2.x", or "1.x.x" works to filter list results, but neither "1.x.2", nor "x.2.x" will work. You do not have to specify the build - Image Builder automatically uses a wildcard for that, if applicable. 
+   * Returns the list of component build versions for the specified semantic version.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: With semantic versioning, you have the flexibility to use wildcards (x) to specify the most recent versions or nodes when selecting the source image or components for your recipe. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. 
    */
   listComponents(params: Imagebuilder.Types.ListComponentsRequest, callback?: (err: AWSError, data: Imagebuilder.Types.ListComponentsResponse) => void): Request<Imagebuilder.Types.ListComponentsResponse, AWSError>;
   /**
-   * Returns the list of component build versions for the specified semantic version.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: When you retrieve or reference a resource with a semantic version, you can use wildcards (x) to filter your results. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. For example, specifying "1.2.x", or "1.x.x" works to filter list results, but neither "1.x.2", nor "x.2.x" will work. You do not have to specify the build - Image Builder automatically uses a wildcard for that, if applicable. 
+   * Returns the list of component build versions for the specified semantic version.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: With semantic versioning, you have the flexibility to use wildcards (x) to specify the most recent versions or nodes when selecting the source image or components for your recipe. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. 
    */
   listComponents(callback?: (err: AWSError, data: Imagebuilder.Types.ListComponentsResponse) => void): Request<Imagebuilder.Types.ListComponentsResponse, AWSError>;
   /**
@@ -268,11 +268,11 @@ declare class Imagebuilder extends Service {
    */
   listImageBuildVersions(callback?: (err: AWSError, data: Imagebuilder.Types.ListImageBuildVersionsResponse) => void): Request<Imagebuilder.Types.ListImageBuildVersionsResponse, AWSError>;
   /**
-   * List the Packages that are associated with an Image Build Version, as determined by Amazon EC2 Systems Manager Inventory at build time.
+   * List the Packages that are associated with an Image Build Version, as determined by Amazon Web Services Systems Manager Inventory at build time.
    */
   listImagePackages(params: Imagebuilder.Types.ListImagePackagesRequest, callback?: (err: AWSError, data: Imagebuilder.Types.ListImagePackagesResponse) => void): Request<Imagebuilder.Types.ListImagePackagesResponse, AWSError>;
   /**
-   * List the Packages that are associated with an Image Build Version, as determined by Amazon EC2 Systems Manager Inventory at build time.
+   * List the Packages that are associated with an Image Build Version, as determined by Amazon Web Services Systems Manager Inventory at build time.
    */
   listImagePackages(callback?: (err: AWSError, data: Imagebuilder.Types.ListImagePackagesResponse) => void): Request<Imagebuilder.Types.ListImagePackagesResponse, AWSError>;
   /**
@@ -409,11 +409,11 @@ declare namespace Imagebuilder {
   export type AccountList = AccountId[];
   export interface AdditionalInstanceConfiguration {
     /**
-     * Contains settings for the SSM agent on your build instance.
+     * Contains settings for the Systems Manager agent on your build instance.
      */
     systemsManagerAgent?: SystemsManagerAgent;
     /**
-     * Use this property to provide commands or a command script to run when you launch your build instance.  The userDataOverride property replaces any commands that Image Builder might have added to ensure that SSM is installed on your Linux build instance. If you override the user data, make sure that you add commands to install SSM, if it is not pre-installed on your source image. 
+     * Use this property to provide commands or a command script to run when you launch your build instance.  The userDataOverride property replaces any commands that Image Builder might have added to ensure that Systems Manager is installed on your Linux build instance. If you override the user data, make sure that you add commands to install Systems Manager, if it is not pre-installed on your source image. 
      */
     userDataOverride?: UserDataOverride;
   }
@@ -528,6 +528,10 @@ declare namespace Imagebuilder {
      * The operating system (OS) version supported by the component. If the OS information is available, a prefix match is performed against the parent image OS version during image recipe creation.
      */
     supportedOsVersions?: OsVersionList;
+    /**
+     * Describes the current status of the component. This is used for components that are no longer active.
+     */
+    state?: ComponentState;
     /**
      * Contains parameter details for each of the parameters that are defined for the component.
      */
@@ -606,6 +610,17 @@ declare namespace Imagebuilder {
   export type ComponentParameterType = string;
   export type ComponentParameterValue = string;
   export type ComponentParameterValueList = ComponentParameterValue[];
+  export interface ComponentState {
+    /**
+     * The current state of the component.
+     */
+    status?: ComponentStatus;
+    /**
+     * Describes how or why the component changed state.
+     */
+    reason?: NonEmptyString;
+  }
+  export type ComponentStatus = "DEPRECATED"|string;
   export interface ComponentSummary {
     /**
      * The Amazon Resource Name (ARN) of the component.
@@ -627,6 +642,10 @@ declare namespace Imagebuilder {
      * The operating system (OS) version supported by the component. If the OS information is available, a prefix match is performed against the parent image OS version during image recipe creation.
      */
     supportedOsVersions?: OsVersionList;
+    /**
+     * Describes the current status of the component.
+     */
+    state?: ComponentState;
     /**
      * The type of the component denotes whether the component is used to build the image or only to test it.
      */
@@ -664,7 +683,7 @@ declare namespace Imagebuilder {
      */
     name?: ResourceName;
     /**
-     * The semantic version of the component.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number, and that is not open for updates.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01.  Filtering: When you retrieve or reference a resource with a semantic version, you can use wildcards (x) to filter your results. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. For example, specifying "1.2.x", or "1.x.x" works to filter list results, but neither "1.x.2", nor "x.2.x" will work. You do not have to specify the build - Image Builder automatically uses a wildcard for that, if applicable. 
+     * The semantic version of the component.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number to the fourth node.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01.  Filtering: With semantic versioning, you have the flexibility to use wildcards (x) to specify the most recent versions or nodes when selecting the source image or components for your recipe. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. 
      */
     version?: VersionNumber;
     /**
@@ -746,7 +765,7 @@ declare namespace Imagebuilder {
      */
     owner?: NonEmptyString;
     /**
-     * The semantic version of the container recipe.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number, and that is not open for updates.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01.  Filtering: When you retrieve or reference a resource with a semantic version, you can use wildcards (x) to filter your results. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. For example, specifying "1.2.x", or "1.x.x" works to filter list results, but neither "1.x.2", nor "x.2.x" will work. You do not have to specify the build - Image Builder automatically uses a wildcard for that, if applicable. 
+     * The semantic version of the container recipe.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number to the fourth node.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01.  Filtering: With semantic versioning, you have the flexibility to use wildcards (x) to specify the most recent versions or nodes when selecting the source image or components for your recipe. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. 
      */
     version?: VersionNumber;
     /**
@@ -834,7 +853,7 @@ declare namespace Imagebuilder {
      */
     name: ResourceName;
     /**
-     * The semantic version of the component. This version follows the semantic version syntax.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number, and that is not open for updates.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01. 
+     * The semantic version of the component. This version follows the semantic version syntax.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number to the fourth node.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01. 
      */
     semanticVersion: VersionNumber;
     /**
@@ -902,7 +921,7 @@ declare namespace Imagebuilder {
      */
     description?: NonEmptyString;
     /**
-     * The semantic version of the container recipe. This version follows the semantic version syntax.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number, and that is not open for updates.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01. 
+     * The semantic version of the container recipe. This version follows the semantic version syntax.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number to the fourth node.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01. 
      */
     semanticVersion: VersionNumber;
     /**
@@ -1078,7 +1097,7 @@ declare namespace Imagebuilder {
      */
     description?: NonEmptyString;
     /**
-     * The semantic version of the image recipe. This version follows the semantic version syntax.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number, and that is not open for updates.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01. 
+     * The semantic version of the image recipe. This version follows the semantic version syntax.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number to the fourth node.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01. 
      */
     semanticVersion: VersionNumber;
     /**
@@ -1182,7 +1201,7 @@ declare namespace Imagebuilder {
      */
     description?: NonEmptyString;
     /**
-     * The instance types of the infrastructure configuration. You can specify one or more instance types to use for this build. The service will pick one of these instance types based on availability.
+     * The instance metadata options that you can set for the HTTP requests that pipeline builds use to launch EC2 build and test instances. For more information about instance metadata options, see one of the following links:    Configure the instance metadata options in the  Amazon EC2 User Guide  for Linux instances.    Configure the instance metadata options in the  Amazon EC2 Windows Guide  for Windows instances.  
      */
     instanceTypes?: InstanceTypeList;
     /**
@@ -1202,7 +1221,7 @@ declare namespace Imagebuilder {
      */
     logging?: Logging;
     /**
-     * The key pair of the infrastructure configuration. This can be used to log on to and debug the instance used to create your image.
+     * The key pair of the infrastructure configuration. You can use this to log on to and debug the instance used to create your image.
      */
     keyPair?: NonEmptyString;
     /**
@@ -1217,6 +1236,10 @@ declare namespace Imagebuilder {
      * The tags attached to the resource created by Image Builder.
      */
     resourceTags?: ResourceTagMap;
+    /**
+     * The instance metadata options that you can set for the HTTP requests that pipeline builds use to launch EC2 build and test instances.
+     */
+    instanceMetadataOptions?: InstanceMetadataOptions;
     /**
      * The tags of the infrastructure configuration.
      */
@@ -1323,7 +1346,7 @@ declare namespace Imagebuilder {
   }
   export interface DeleteImageRequest {
     /**
-     * The Amazon Resource Name (ARN) of the image to delete.
+     * The Amazon Resource Name (ARN) of the Image Builder image resource to delete.
      */
     imageBuildVersionArn: ImageBuildVersionArn;
   }
@@ -1333,7 +1356,7 @@ declare namespace Imagebuilder {
      */
     requestId?: NonEmptyString;
     /**
-     * The Amazon Resource Name (ARN) of the image that was deleted.
+     * The Amazon Resource Name (ARN) of the Image Builder image resource that was deleted.
      */
     imageBuildVersionArn?: ImageBuildVersionArn;
   }
@@ -1473,9 +1496,14 @@ declare namespace Imagebuilder {
      * Use to override the device's volume type.
      */
     volumeType?: EbsVolumeType;
+    /**
+     *  For GP3 volumes only – The throughput in MiB/s that the volume supports. 
+     */
+    throughput?: EbsVolumeThroughput;
   }
   export type EbsIopsInteger = number;
   export type EbsVolumeSizeInteger = number;
+  export type EbsVolumeThroughput = number;
   export type EbsVolumeType = "standard"|"io1"|"io2"|"gp2"|"gp3"|"sc1"|"st1"|string;
   export type EmptyString = string;
   export interface Filter {
@@ -1668,6 +1696,8 @@ declare namespace Imagebuilder {
      */
     infrastructureConfiguration?: InfrastructureConfiguration;
   }
+  export type HttpPutResponseHopLimit = number;
+  export type HttpTokens = string;
   export interface Image {
     /**
      * The Amazon Resource Name (ARN) of the image.  Semantic versioning is included in each object's Amazon Resource Name (ARN), at the level that applies to that object as follows:   Versionless ARNs and Name ARNs do not include specific values in any of the nodes. The nodes are either left off entirely, or they are specified as wildcards, for example: x.x.x.   Version ARNs have only the first three nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;   Build version ARNs have all four nodes, and point to a specific build for a specific version of an object.   
@@ -1682,7 +1712,7 @@ declare namespace Imagebuilder {
      */
     name?: ResourceName;
     /**
-     * The semantic version of the image.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number, and that is not open for updates.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01.  Filtering: When you retrieve or reference a resource with a semantic version, you can use wildcards (x) to filter your results. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. For example, specifying "1.2.x", or "1.x.x" works to filter list results, but neither "1.x.2", nor "x.2.x" will work. You do not have to specify the build - Image Builder automatically uses a wildcard for that, if applicable. 
+     * The semantic version of the image.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number to the fourth node.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01.  Filtering: With semantic versioning, you have the flexibility to use wildcards (x) to specify the most recent versions or nodes when selecting the source image or components for your recipe. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. 
      */
     version?: VersionNumber;
     /**
@@ -2001,7 +2031,7 @@ declare namespace Imagebuilder {
      */
     type?: ImageType;
     /**
-     * Details for a specific version of an Image Builder image. This version follows the semantic version syntax.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number, and that is not open for updates.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01.  Filtering: When you retrieve or reference a resource with a semantic version, you can use wildcards (x) to filter your results. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. For example, specifying "1.2.x", or "1.x.x" works to filter list results, but neither "1.x.2", nor "x.2.x" will work. You do not have to specify the build - Image Builder automatically uses a wildcard for that, if applicable. 
+     * Details for a specific version of an Image Builder image. This version follows the semantic version syntax.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number to the fourth node.  Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01.  Filtering: With semantic versioning, you have the flexibility to use wildcards (x) to specify the most recent versions or nodes when selecting the source image or components for your recipe. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. 
      */
     version?: VersionNumber;
     /**
@@ -2030,7 +2060,7 @@ declare namespace Imagebuilder {
      */
     name: ResourceName;
     /**
-     * The semantic version of the component. This version follows the semantic version syntax.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: When you retrieve or reference a resource with a semantic version, you can use wildcards (x) to filter your results. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. For example, specifying "1.2.x", or "1.x.x" works to filter list results, but neither "1.x.2", nor "x.2.x" will work. You do not have to specify the build - Image Builder automatically uses a wildcard for that, if applicable. 
+     * The semantic version of the component. This version follows the semantic version syntax.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: With semantic versioning, you have the flexibility to use wildcards (x) to specify the most recent versions or nodes when selecting the source image or components for your recipe. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. 
      */
     semanticVersion: VersionNumber;
     /**
@@ -2145,6 +2175,10 @@ declare namespace Imagebuilder {
      * The tags attached to the resource created by Image Builder.
      */
     resourceTags?: ResourceTagMap;
+    /**
+     * The instance metadata option settings for the infrastructure configuration.
+     */
+    instanceMetadataOptions?: InstanceMetadataOptions;
     /**
      * The tags of the infrastructure configuration.
      */
@@ -2221,6 +2255,16 @@ declare namespace Imagebuilder {
      */
     blockDeviceMappings?: InstanceBlockDeviceMappings;
   }
+  export interface InstanceMetadataOptions {
+    /**
+     * Indicates whether a signed token header is required for instance metadata retrieval requests. The values affect the response as follows:    required – When you retrieve the IAM role credentials, version 2.0 credentials are returned in all cases.    optional – You can include a signed token header in your request to retrieve instance metadata, or you can leave it out. If you include it, version 2.0 credentials are returned for the IAM role. Otherwise, version 1.0 credentials are returned.   The default setting is optional.
+     */
+    httpTokens?: HttpTokens;
+    /**
+     * Limit the number of hops that an instance metadata request can traverse to reach its destination.
+     */
+    httpPutResponseHopLimit?: HttpPutResponseHopLimit;
+  }
   export type InstanceProfileNameType = string;
   export type InstanceType = string;
   export type InstanceTypeList = InstanceType[];
@@ -2560,7 +2604,7 @@ declare namespace Imagebuilder {
      */
     requestId?: NonEmptyString;
     /**
-     * The list of image semantic versions.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: When you retrieve or reference a resource with a semantic version, you can use wildcards (x) to filter your results. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. For example, specifying "1.2.x", or "1.x.x" works to filter list results, but neither "1.x.2", nor "x.2.x" will work. You do not have to specify the build - Image Builder automatically uses a wildcard for that, if applicable. 
+     * The list of image semantic versions.  The semantic version has four nodes: &lt;major&gt;.&lt;minor&gt;.&lt;patch&gt;/&lt;build&gt;. You can assign values for the first three, and can filter on all of them.  Filtering: With semantic versioning, you have the flexibility to use wildcards (x) to specify the most recent versions or nodes when selecting the source image or components for your recipe. When you use a wildcard in any node, all nodes to the right of the first wildcard must also be wildcards. 
      */
     imageVersionList?: ImageVersionList;
     /**
@@ -2771,7 +2815,7 @@ declare namespace Imagebuilder {
   export type StringList = NonEmptyString[];
   export interface SystemsManagerAgent {
     /**
-     * Controls whether the SSM agent is removed from your final build image, prior to creating the new AMI. If this is set to true, then the agent is removed from the final image. If it's set to false, then the agent is left in, so that it is included in the new AMI. The default value is false.
+     * Controls whether the Systems Manager agent is removed from your final build image, prior to creating the new AMI. If this is set to true, then the agent is removed from the final image. If it's set to false, then the agent is left in, so that it is included in the new AMI. The default value is false.
      */
     uninstallAfterBuild?: NullableBoolean;
   }
@@ -2936,7 +2980,7 @@ declare namespace Imagebuilder {
      */
     logging?: Logging;
     /**
-     * The key pair of the infrastructure configuration. This can be used to log on to and debug the instance used to create your image.
+     * The key pair of the infrastructure configuration. You can use this to log on to and debug the instance used to create your image.
      */
     keyPair?: NonEmptyString;
     /**
@@ -2955,6 +2999,10 @@ declare namespace Imagebuilder {
      * The tags attached to the resource created by Image Builder.
      */
     resourceTags?: ResourceTagMap;
+    /**
+     * The instance metadata options that you can set for the HTTP requests that pipeline builds use to launch EC2 build and test instances. For more information about instance metadata options, see one of the following links:    Configure the instance metadata options in the  Amazon EC2 User Guide  for Linux instances.    Configure the instance metadata options in the  Amazon EC2 Windows Guide  for Windows instances.  
+     */
+    instanceMetadataOptions?: InstanceMetadataOptions;
   }
   export interface UpdateInfrastructureConfigurationResponse {
     /**

package/clients/iot.d.ts

@@ -1483,6 +1483,14 @@ declare class Iot extends Service {
    * Lists the Device Defender security profile violations discovered during the given time period. You can use filters to limit the results to those alerts issued for a particular security profile, behavior, or thing (device). Requires permission to access the ListViolationEvents action.
    */
   listViolationEvents(callback?: (err: AWSError, data: Iot.Types.ListViolationEventsResponse) => void): Request<Iot.Types.ListViolationEventsResponse, AWSError>;
+  /**
+   * Set a verification state and provide a description of that verification state on a violation (detect alarm).
+   */
+  putVerificationStateOnViolation(params: Iot.Types.PutVerificationStateOnViolationRequest, callback?: (err: AWSError, data: Iot.Types.PutVerificationStateOnViolationResponse) => void): Request<Iot.Types.PutVerificationStateOnViolationResponse, AWSError>;
+  /**
+   * Set a verification state and provide a description of that verification state on a violation (detect alarm).
+   */
+  putVerificationStateOnViolation(callback?: (err: AWSError, data: Iot.Types.PutVerificationStateOnViolationResponse) => void): Request<Iot.Types.PutVerificationStateOnViolationResponse, AWSError>;
   /**
    * Registers a CA certificate with IoT. This CA certificate can then be used to sign device certificates, which can be then registered with IoT. You can register up to 10 CA certificates per Amazon Web Services account that have the same subject field. This enables you to have up to 10 certificate authorities sign your device certificates. If you have more than one CA certificate registered, make sure you pass the CA certificate when you register your device certificates with the RegisterCertificate action. Requires permission to access the RegisterCACertificate action.
    */
@@ -1965,7 +1973,7 @@ declare namespace Iot {
      */
     cloudwatchLogs?: CloudwatchLogsAction;
     /**
-     * Write data to an Amazon Elasticsearch Service domain.  This action is deprecated. Use the OpenSearch action instead. 
+     * Write data to an Amazon OpenSearch Service domain.  The Elasticsearch action can only be used by existing rule actions. To create a new rule action or to update an existing rule action, use the OpenSearch rule action instead. For more information, see OpenSearchAction. 
      */
     elasticsearch?: ElasticsearchAction;
     /**
@@ -2032,6 +2040,14 @@ declare namespace Iot {
      *  The details of a violation event. 
      */
     violationEventAdditionalInfo?: ViolationEventAdditionalInfo;
+    /**
+     * The verification state of the violation (detect alarm).
+     */
+    verificationState?: VerificationState;
+    /**
+     * The description of the verification state of the violation.
+     */
+    verificationStateDescription?: VerificationStateDescription;
     /**
      * The time the most recent violation occurred.
      */
@@ -3192,7 +3208,7 @@ declare namespace Iot {
      */
     description?: AuditDescription;
     /**
-     *  The epoch timestamp in seconds at which this suppression expires. 
+     *  Each audit supression must have a unique client request token. If you try to create a new audit suppression with the same token as one that already exists, an exception occurs. If you omit this value, Amazon Web Services SDKs will automatically generate a unique client request. 
      */
     clientRequestToken: ClientRequestToken;
   }
@@ -5673,15 +5689,15 @@ declare namespace Iot {
   }
   export interface ElasticsearchAction {
     /**
-     * The IAM role ARN that has access to Elasticsearch.
+     * The IAM role ARN that has access to OpenSearch.
      */
     roleArn: AwsArn;
     /**
-     * The endpoint of your Elasticsearch domain.
+     * The endpoint of your OpenSearch domain.
      */
     endpoint: ElasticsearchEndpoint;
     /**
-     * The Elasticsearch index where you want to store your data.
+     * The index where you want to store your data.
      */
     index: ElasticsearchIndex;
     /**
@@ -6673,6 +6689,10 @@ declare namespace Iot {
      *  A list of all suppressed alerts. 
      */
     listSuppressedAlerts?: ListSuppressedAlerts;
+    /**
+     * The verification state of the violation (detect alarm).
+     */
+    verificationState?: VerificationState;
     /**
      * The token for the next set of results.
      */
@@ -8089,6 +8109,10 @@ declare namespace Iot {
      *  A list of all suppressed alerts. 
      */
     listSuppressedAlerts?: ListSuppressedAlerts;
+    /**
+     * The verification state of the violation (detect alarm).
+     */
+    verificationState?: VerificationState;
     /**
      * The token for the next set of results.
      */
@@ -8660,6 +8684,22 @@ declare namespace Iot {
      */
     tableName: TableName;
   }
+  export interface PutVerificationStateOnViolationRequest {
+    /**
+     * The violation ID.
+     */
+    violationId: ViolationId;
+    /**
+     * The verification state of the violation.
+     */
+    verificationState: VerificationState;
+    /**
+     * The description of the verification state of the violation (detect alarm).
+     */
+    verificationStateDescription?: VerificationStateDescription;
+  }
+  export interface PutVerificationStateOnViolationResponse {
+  }
   export type Qos = number;
   export type QueryMaxResults = number;
   export type QueryString = string;
@@ -10910,6 +10950,8 @@ declare namespace Iot {
   export type ValidationErrors = ValidationError[];
   export type Value = string;
   export type Variance = number;
+  export type VerificationState = "FALSE_POSITIVE"|"BENIGN_POSITIVE"|"TRUE_POSITIVE"|"UNKNOWN"|string;
+  export type VerificationStateDescription = string;
   export type Version = number;
   export type VersionNumber = number;
   export interface ViolationEvent {
@@ -10941,6 +10983,14 @@ declare namespace Iot {
      * The type of violation event.
      */
     violationEventType?: ViolationEventType;
+    /**
+     * The verification state of the violation (detect alarm).
+     */
+    verificationState?: VerificationState;
+    /**
+     * The description of the verification state of the violation.
+     */
+    verificationStateDescription?: VerificationStateDescription;
     /**
      * The time the violation event occurred.
      */