Remove incorrect endpoint tests

Remove incorrect endpoint tests
Doc-only updates for Incident Manager Contacts August 2025
The default application in a stream group can now be changed at any time using UpdateStreamGroup to update the DefaultApplicationIdentifier.
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
This is a documentation only release that adds additional information for the update-service request parameters.
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove Pattern trait from email field
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Added support for preprocessing queries in Data Quality operations through new DataQualityGlueTable structure.
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests
Remove incorrect endpoint tests

Author: aws-sdk-cpp-automation

VERSION

@@ -1 +1 @@
-1.11.631
+1.11.632

generated/src/aws-cpp-sdk-apigatewaymanagementapi/source/ApiGatewayManagementApiEndpointRules.cpp

@@ -89,13 +89,20 @@ namespace Model
      * can't be used to place tasks. If you specify multiple capacity providers in a
      * strategy that all have a weight of <code>0</code>, any <code>RunTask</code> or
      * <code>CreateService</code> actions using the capacity provider strategy will
-     * fail.</p> <p>An example scenario for using weights is defining a strategy that
-     * contains two capacity providers and both have a weight of <code>1</code>, then
-     * when the <code>base</code> is satisfied, the tasks will be split evenly across
-     * the two capacity providers. Using that same logic, if you specify a weight of
-     * <code>1</code> for <i>capacityProviderA</i> and a weight of <code>4</code> for
-     * <i>capacityProviderB</i>, then for every one task that's run using
-     * <i>capacityProviderA</i>, four tasks would use <i>capacityProviderB</i>.</p>
+     * fail.</p> <p>Weight value characteristics:</p> <ul> <li> <p>Weight is considered
+     * after the base value is satisfied</p> </li> <li> <p>Default value is
+     * <code>0</code> if not specified</p> </li> <li> <p>Valid range: 0 to 1,000</p>
+     * </li> <li> <p>At least one capacity provider must have a weight greater than
+     * zero</p> </li> <li> <p>Capacity providers with weight of <code>0</code> cannot
+     * place tasks</p> </li> </ul> <p>Task distribution logic:</p> <ol> <li> <p>Base
+     * satisfaction: The minimum number of tasks specified by the base value are placed
+     * on that capacity provider</p> </li> <li> <p>Weight distribution: After base
+     * requirements are met, additional tasks are distributed according to weight
+     * ratios</p> </li> </ol> <p>Examples:</p> <p>Equal Distribution: Two capacity
+     * providers both with weight <code>1</code> will split tasks evenly after base
+     * requirements are met.</p> <p>Weighted Distribution: If capacityProviderA has
+     * weight <code>1</code> and capacityProviderB has weight <code>4</code>, then for
+     * every 1 task on A, 4 tasks will run on B.</p>
      */
     inline int GetWeight() const { return m_weight; }
     inline bool WeightHasBeenSet() const { return m_weightHasBeenSet; }
@@ -106,9 +113,13 @@ namespace Model
     ///@{
     /**
      * <p>The <i>base</i> value designates how many tasks, at a minimum, to run on the
-     * specified capacity provider. Only one capacity provider in a capacity provider
-     * strategy can have a <i>base</i> defined. If no value is specified, the default
-     * value of <code>0</code> is used.</p>
+     * specified capacity provider for each service. Only one capacity provider in a
+     * capacity provider strategy can have a <i>base</i> defined. If no value is
+     * specified, the default value of <code>0</code> is used.</p> <p>Base value
+     * characteristics:</p> <ul> <li> <p>Only one capacity provider in a strategy can
+     * have a base defined</p> </li> <li> <p>Default value is <code>0</code> if not
+     * specified</p> </li> <li> <p>Valid range: 0 to 100,000</p> </li> <li> <p>Base
+     * requirements are satisfied first before weight distribution</p> </li> </ul>
      */
     inline int GetBase() const { return m_base; }
     inline bool BaseHasBeenSet() const { return m_baseHasBeenSet; }

generated/src/aws-cpp-sdk-appfabric/source/AppFabricEndpointRules.cpp

@@ -150,7 +150,7 @@ namespace Model
     /**
      * <p>The number of services that are running on the cluster in an
      * <code>ACTIVE</code> state. You can view these services with <a
-     * href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html">PListServices</a>.</p>
+     * href="https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html">ListServices</a>.</p>
      */
     inline int GetActiveServicesCount() const { return m_activeServicesCount; }
     inline bool ActiveServicesCountHasBeenSet() const { return m_activeServicesCountHasBeenSet; }

generated/src/aws-cpp-sdk-backup-gateway/source/BackupGatewayEndpointRules.cpp

@@ -40,8 +40,7 @@ namespace Model
     /**
      * <p>The short name or full Amazon Resource Name (ARN) of the cluster that hosts
      * the task or tasks to describe. If you do not specify a cluster, the default
-     * cluster is assumed. If you do not specify a value, the <code>default</code>
-     * cluster is used.</p>
+     * cluster is assumed.</p>
      */
     inline const Aws::String& GetCluster() const { return m_cluster; }
     inline bool ClusterHasBeenSet() const { return m_clusterHasBeenSet; }

generated/src/aws-cpp-sdk-cloudhsm/source/CloudHSMEndpointRules.cpp

@@ -190,7 +190,7 @@ namespace Model
      * <code>logConfiguration</code> as <code>blocking</code>.</p> </li> <li> <p>Set
      * the <code>defaultLogDriverMode</code> account setting to
      * <code>blocking</code>.</p> </li> </ul>  </dd> <dt>max-buffer-size</dt>
-     * <dd> <p>Required: No</p> <p>Default value: <code>1m</code> </p> <p>When
+     * <dd> <p>Required: No</p> <p>Default value: <code>10m</code> </p> <p>When
      * <code>non-blocking</code> mode is used, the <code>max-buffer-size</code> log
      * option controls the size of the buffer that's used for intermediate message
      * storage. Make sure to specify an adequate buffer size based on your application.