Update models from aws-sdk-go-v2 1cc8d0492d3ef65c275f5d0759ee2a2d5c91…

…12da

Package.swift

@@ -113,6 +113,7 @@ let package = Package(
         .library(name: "SotoDataExchange", targets: ["SotoDataExchange"]),
         .library(name: "SotoDataPipeline", targets: ["SotoDataPipeline"]),
         .library(name: "SotoDataSync", targets: ["SotoDataSync"]),
+        .library(name: "SotoDataZone", targets: ["SotoDataZone"]),
         .library(name: "SotoDatabaseMigrationService", targets: ["SotoDatabaseMigrationService"]),
         .library(name: "SotoDetective", targets: ["SotoDetective"]),
         .library(name: "SotoDevOpsGuru", targets: ["SotoDevOpsGuru"]),
@@ -475,6 +476,7 @@ let package = Package(
         .target(name: "SotoDataExchange", dependencies: [.product(name: "SotoCore", package: "soto-core")], path: "./Sources/Soto/Services/DataExchange"),
         .target(name: "SotoDataPipeline", dependencies: [.product(name: "SotoCore", package: "soto-core")], path: "./Sources/Soto/Services/DataPipeline"),
         .target(name: "SotoDataSync", dependencies: [.product(name: "SotoCore", package: "soto-core")], path: "./Sources/Soto/Services/DataSync"),
+        .target(name: "SotoDataZone", dependencies: [.product(name: "SotoCore", package: "soto-core")], path: "./Sources/Soto/Services/DataZone"),
         .target(name: "SotoDatabaseMigrationService", dependencies: [.product(name: "SotoCore", package: "soto-core")], path: "./Sources/Soto/Services/DatabaseMigrationService"),
         .target(name: "SotoDetective", dependencies: [.product(name: "SotoCore", package: "soto-core")], path: "./Sources/Soto/Services/Detective"),
         .target(name: "SotoDevOpsGuru", dependencies: [.product(name: "SotoCore", package: "soto-core")], path: "./Sources/Soto/Services/DevOpsGuru"),

Sources/Soto/Services/AuditManager/AuditManager_shapes.swift

@@ -3993,6 +3993,8 @@ extension AuditManager {
             try self.awsAccounts?.forEach {
                 try $0.validate(name: "\(name).awsAccounts[]")
             }
+            try self.validate(self.awsAccounts, name: "awsAccounts", parent: name, max: 200)
+            try self.validate(self.awsAccounts, name: "awsAccounts", parent: name, min: 1)
             try self.awsServices?.forEach {
                 try $0.validate(name: "\(name).awsServices[]")
             }

Sources/Soto/Services/AutoScaling/AutoScaling_api+async.swift

@@ -395,6 +395,28 @@ extension AutoScaling {
         )
     }
 
+    /// Gets information about the instance refreshes for the specified Auto Scaling group. This operation is part of the instance refresh feature in Amazon EC2 Auto Scaling, which helps you update instances in your Auto Scaling group after you make configuration changes. To help you determine the status of an instance refresh, Amazon EC2 Auto Scaling returns information about the instance refreshes you previously initiated, including their status, start time, end time, the percentage of the instance refresh that is complete, and the number of instances remaining to update before the instance refresh is complete. If a rollback is initiated while an instance refresh is in progress, Amazon EC2 Auto Scaling also returns information about the rollback of the instance refresh.
+    /// Return PaginatorSequence for operation.
+    ///
+    /// - Parameters:
+    ///   - input: Input for request
+    ///   - logger: Logger used flot logging
+    ///   - eventLoop: EventLoop to run this process on
+    public func describeInstanceRefreshesPaginator(
+        _ input: DescribeInstanceRefreshesType,
+        logger: Logger = AWSClient.loggingDisabled,
+        on eventLoop: EventLoop? = nil
+    ) -> AWSClient.PaginatorSequence<DescribeInstanceRefreshesType, DescribeInstanceRefreshesAnswer> {
+        return .init(
+            input: input,
+            command: self.describeInstanceRefreshes,
+            inputKey: \DescribeInstanceRefreshesType.nextToken,
+            outputKey: \DescribeInstanceRefreshesAnswer.nextToken,
+            logger: logger,
+            on: eventLoop
+        )
+    }
+
     /// Gets information about the launch configurations in the account and Region.
     /// Return PaginatorSequence for operation.
     ///
@@ -417,6 +439,50 @@ extension AutoScaling {
         )
     }
 
+    ///  This API operation is superseded by DescribeTrafficSources, which can describe multiple traffic sources types. We recommend using DetachTrafficSources to simplify how you manage traffic sources. However, we continue to support DescribeLoadBalancerTargetGroups. You can use both the original DescribeLoadBalancerTargetGroups API operation and DescribeTrafficSources on the same Auto Scaling group.  Gets information about the Elastic Load Balancing target groups for the specified Auto Scaling group. To determine the attachment status of the target group, use the State element in the response. When you attach a target group to an Auto Scaling group, the initial State value is Adding. The state transitions to Added after all Auto Scaling instances are registered with the target group. If Elastic Load Balancing health checks are enabled for the Auto Scaling group, the state transitions to InService after at least one Auto Scaling instance passes the health check. When the target group is in the InService state, Amazon EC2 Auto Scaling can terminate and replace any instances that are reported as unhealthy. If no registered instances pass the health checks, the target group doesn't enter the InService state.  Target groups also have an InService state if you attach them in the CreateAutoScalingGroup API call. If your target group state is InService, but it is not working properly, check the scaling activities by calling DescribeScalingActivities and take any corrective actions necessary. For help with failed health checks, see Troubleshooting Amazon EC2 Auto Scaling: Health checks in the Amazon EC2 Auto Scaling User Guide. For more information, see Use Elastic Load Balancing to distribute traffic across the instances in your Auto Scaling group in the Amazon EC2 Auto Scaling User Guide.   You can use this operation to describe target groups that were attached by using AttachLoadBalancerTargetGroups, but not for target groups that were attached by using AttachTrafficSources.
+    /// Return PaginatorSequence for operation.
+    ///
+    /// - Parameters:
+    ///   - input: Input for request
+    ///   - logger: Logger used flot logging
+    ///   - eventLoop: EventLoop to run this process on
+    public func describeLoadBalancerTargetGroupsPaginator(
+        _ input: DescribeLoadBalancerTargetGroupsRequest,
+        logger: Logger = AWSClient.loggingDisabled,
+        on eventLoop: EventLoop? = nil
+    ) -> AWSClient.PaginatorSequence<DescribeLoadBalancerTargetGroupsRequest, DescribeLoadBalancerTargetGroupsResponse> {
+        return .init(
+            input: input,
+            command: self.describeLoadBalancerTargetGroups,
+            inputKey: \DescribeLoadBalancerTargetGroupsRequest.nextToken,
+            outputKey: \DescribeLoadBalancerTargetGroupsResponse.nextToken,
+            logger: logger,
+            on: eventLoop
+        )
+    }
+
+    ///  This API operation is superseded by DescribeTrafficSources, which can describe multiple traffic sources types. We recommend using DescribeTrafficSources to simplify how you manage traffic sources. However, we continue to support DescribeLoadBalancers. You can use both the original DescribeLoadBalancers API operation and DescribeTrafficSources on the same Auto Scaling group.  Gets information about the load balancers for the specified Auto Scaling group. This operation describes only Classic Load Balancers. If you have Application Load Balancers, Network Load Balancers, or Gateway Load Balancers, use the DescribeLoadBalancerTargetGroups API instead. To determine the attachment status of the load balancer, use the State element in the response. When you attach a load balancer to an Auto Scaling group, the initial State value is Adding. The state transitions to Added after all Auto Scaling instances are registered with the load balancer. If Elastic Load Balancing health checks are enabled for the Auto Scaling group, the state transitions to InService after at least one Auto Scaling instance passes the health check. When the load balancer is in the InService state, Amazon EC2 Auto Scaling can terminate and replace any instances that are reported as unhealthy. If no registered instances pass the health checks, the load balancer doesn't enter the InService state.  Load balancers also have an InService state if you attach them in the CreateAutoScalingGroup API call. If your load balancer state is InService, but it is not working properly, check the scaling activities by calling DescribeScalingActivities and take any corrective actions necessary. For help with failed health checks, see Troubleshooting Amazon EC2 Auto Scaling: Health checks in the Amazon EC2 Auto Scaling User Guide. For more information, see Use Elastic Load Balancing to distribute traffic across the instances in your Auto Scaling group in the Amazon EC2 Auto Scaling User Guide.
+    /// Return PaginatorSequence for operation.
+    ///
+    /// - Parameters:
+    ///   - input: Input for request
+    ///   - logger: Logger used flot logging
+    ///   - eventLoop: EventLoop to run this process on
+    public func describeLoadBalancersPaginator(
+        _ input: DescribeLoadBalancersRequest,
+        logger: Logger = AWSClient.loggingDisabled,
+        on eventLoop: EventLoop? = nil
+    ) -> AWSClient.PaginatorSequence<DescribeLoadBalancersRequest, DescribeLoadBalancersResponse> {
+        return .init(
+            input: input,
+            command: self.describeLoadBalancers,
+            inputKey: \DescribeLoadBalancersRequest.nextToken,
+            outputKey: \DescribeLoadBalancersResponse.nextToken,
+            logger: logger,
+            on: eventLoop
+        )
+    }
+
     /// Gets information about the Amazon SNS notifications that are configured for one or more Auto Scaling groups.
     /// Return PaginatorSequence for operation.
     ///