Added default_x86_64 and default_arm64 as values to the instanceTypes field.

Customer managed keys now available for volume encryption of SageMaker HyperPod clusters.
Amazon Connect Service Feature: Add support to enable multi-user in-app, web, and video calling.
Billing and Cost Management Dashboards enables users to create dashboards that combine multiple visualizations of cost and usage data. Users can create, manage, and share dashboards. Tags are also available for dashboards.
Adds support for Compute checksum functionality in Amazon S3 Batch Operations. You can now calculate checksums for a list of objects using supported algorithms in Amazon S3, without requiring a restore or download
Amazon Connect Service Feature: Add support to enable multi-user in-app, web, and video calling.

Author: aws-sdk-cpp-automation

VERSION

@@ -1 +1 @@
-1.11.628
+1.11.629

generated/smoke-tests/bcm-dashboards/BCMDashboardsSmokeTests.cpp

@@ -0,0 +1,46 @@
+/**
+ * Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+ * SPDX-License-Identifier: Apache-2.0.
+ */
+#include <algorithm>
+#include <aws/core/auth/AWSCredentialsProviderChain.h>
+#include <aws/core/client/AsyncCallerContext.h>
+#include <aws/core/client/ClientConfiguration.h>
+#include <aws/core/client/CoreErrors.h>
+#include <aws/core/http/HttpTypes.h>
+#include <aws/core/utils/Outcome.h>
+#include <aws/core/utils/UnreferencedParam.h>
+#include <aws/core/utils/logging/LogMacros.h>
+#include <aws/core/utils/memory/AWSMemory.h>
+#include <utility>
+#include <aws/testing/AwsCppSdkGTestSuite.h>
+#include <aws/testing/AwsTestHelpers.h>
+#include <aws/bcm-dashboards/BCMDashboardsClient.h>
+#include <aws/bcm-dashboards/model/ListDashboardsRequest.h>
+
+namespace BCMDashboardsSmokeTest{
+using namespace Aws::Auth;
+using namespace Aws::Http;
+using namespace Aws::Client;
+
+using namespace Aws::BCMDashboards;
+using namespace Aws::BCMDashboards::Model;
+class BCMDashboardsSmokeTestSuite : public Aws::Testing::AwsCppSdkGTestSuite {
+    public:
+    static const char ALLOCATION_TAG[];
+};
+const char BCMDashboardsSmokeTestSuite::ALLOCATION_TAG[] = "BCMDashboardsSmokeTest";
+TEST_F(BCMDashboardsSmokeTestSuite, ListDashboardsSuccess )
+{
+    Aws::BCMDashboards::BCMDashboardsClientConfiguration clientConfiguration;
+    clientConfiguration.region = "us-east-1";
+    clientConfiguration.useFIPS = false;
+    clientConfiguration.useDualStack = false;
+    auto clientSp = Aws::MakeShared<BCMDashboardsClient>(ALLOCATION_TAG, clientConfiguration);
+    //populate input params
+    
+    ListDashboardsRequest input;
+    auto outcome = clientSp->ListDashboards(input);
+    EXPECT_TRUE( outcome.IsSuccess());
+}
+}

generated/smoke-tests/bcm-dashboards/CMakeLists.txt

@@ -0,0 +1,41 @@
+add_project(bcm-dashboards-smoke-tests
+"Tests for the AWS BCM-DASHBOARDS C++ SDK"
+testing-resources
+aws-cpp-sdk-bcm-dashboards
+aws-cpp-sdk-core
+)
+file(GLOB AWS_BCM-DASHBOARDS_GENERATED_SMOKE_TEST_SRC
+"${CMAKE_CURRENT_SOURCE_DIR}/../RunTests.cpp"
+"${CMAKE_CURRENT_SOURCE_DIR}/*.cpp"
+)
+if(MSVC AND BUILD_SHARED_LIBS)
+    add_definitions(-DGTEST_LINKED_AS_SHARED_LIBRARY=1)
+endif()
+
+if (CMAKE_CROSSCOMPILING)
+    set(AUTORUN_UNIT_TESTS OFF)
+endif()
+
+if (AUTORUN_UNIT_TESTS)
+    enable_testing()
+endif()
+
+if(PLATFORM_ANDROID AND BUILD_SHARED_LIBS)
+    add_library(${PROJECT_NAME} "${AWS_BCM-DASHBOARDS_GENERATED_SMOKE_TEST_SRC}")
+else()
+    add_executable(${PROJECT_NAME} "${AWS_BCM-DASHBOARDS_GENERATED_SMOKE_TEST_SRC}")
+endif()
+
+set_compiler_flags(${PROJECT_NAME})
+set_compiler_warnings(${PROJECT_NAME})
+
+target_include_directories(${PROJECT_NAME} PUBLIC
+    ${CMAKE_CURRENT_SOURCE_DIR}/../../src/aws-cpp-sdk-bcm-dashboards/include)
+
+target_link_libraries(${PROJECT_NAME}
+    ${PROJECT_LIBS})
+
+if(NOT CMAKE_CROSSCOMPILING)
+    SET_TARGET_PROPERTIES(${PROJECT_NAME} PROPERTIES OUTPUT_NAME ${PROJECT_NAME})
+endif()
+

generated/src/aws-cpp-sdk-batch/include/aws/batch/model/ComputeResource.h

@@ -161,17 +161,47 @@ namespace Model
      * <p>The instances types that can be launched. You can specify instance families
      * to launch any instance type within those families (for example, <code>c5</code>
      * or <code>p3</code>), or you can specify specific sizes within a family (such as
-     * <code>c5.8xlarge</code>). You can also choose <code>optimal</code> to select
-     * instance types (from the C4, M4, and R4 instance families) that match the demand
-     * of your job queues.</p>  <p>This parameter isn't applicable to jobs that
-     * are running on Fargate resources. Don't specify it.</p>   <p>When
-     * you create a compute environment, the instance types that you select for the
-     * compute environment must share the same architecture. For example, you can't mix
-     * x86 and ARM instances in the same compute environment.</p>  
-     * <p>Currently, <code>optimal</code> uses instance types from the C4, M4, and R4
-     * instance families. In Regions that don't have instance types from those instance
-     * families, instance types from the C5, M5, and R5 instance families are used.</p>
-     * 
+     * <code>c5.8xlarge</code>). </p> <p>Batch can select the instance type for you if
+     * you choose one of the following:</p> <ul> <li> <p> <code>optimal</code> to
+     * select instance types (from the <code>c4</code>, <code>m4</code>,
+     * <code>r4</code>, <code>c5</code>, <code>m5</code>, and <code>r5</code> instance
+     * families) that match the demand of your job queues. </p> </li> <li> <p>
+     * <code>default_x86_64</code> to choose x86 based instance types (from the
+     * <code>m6i</code>, <code>c6i</code>, <code>r6i</code>, and <code>c7i</code>
+     * instance families) that matches the resource demands of the job queue.</p> </li>
+     * <li> <p> <code>default_arm64</code> to choose x86 based instance types (from the
+     * <code>m6g</code>, <code>c6g</code>, <code>r6g</code>, and <code>c7g</code>
+     * instance families) that matches the resource demands of the job queue.</p> </li>
+     * </ul>  <p>Starting on 11/01/2025 the behavior of <code>optimal</code> is
+     * going to be changed to match <code>default_x86_64</code>. During the change your
+     * instance families could be updated to a newer generation. You do not need to
+     * perform any actions for the upgrade to happen. For more information about
+     * change, see <a
+     * href="https://docs.aws.amazon.com/batch/latest/userguide/optimal-default-instance-troubleshooting.html">Optimal
+     * instance type configuration to receive automatic instance family
+     * updates</a>.</p>   <p>Instance family availability varies by Amazon
+     * Web Services Region. For example, some Amazon Web Services Regions may not have
+     * any fourth generation instance families but have fifth and sixth generation
+     * instance families.</p> <p>When using <code>default_x86_64</code> or
+     * <code>default_arm64</code> instance bundles, Batch selects instance families
+     * based on a balance of cost-effectiveness and performance. While newer generation
+     * instances often provide better price-performance, Batch may choose an earlier
+     * generation instance family if it provides the optimal combination of
+     * availability, cost, and performance for your workload. For example, in an Amazon
+     * Web Services Region where both c6i and c7i instances are available, Batch might
+     * select c6i instances if they offer better cost-effectiveness for your specific
+     * job requirements. For more information on Batch instance types and Amazon Web
+     * Services Region availability, see <a
+     * href="https://docs.aws.amazon.com/batch/latest/userguide/instance-type-compute-table.html">Instance
+     * type compute table</a> in the <i>Batch User Guide</i>.</p> <p>Batch periodically
+     * updates your instances in default bundles to newer, more cost-effective options.
+     * Updates happen automatically without requiring any action from you. Your
+     * workloads continue running during updates with no interruption </p> 
+     *  <p>This parameter isn't applicable to jobs that are running on Fargate
+     * resources. Don't specify it.</p>   <p>When you create a compute
+     * environment, the instance types that you select for the compute environment must
+     * share the same architecture. For example, you can't mix x86 and ARM instances in
+     * the same compute environment.</p> 
      */
     inline const Aws::Vector<Aws::String>& GetInstanceTypes() const { return m_instanceTypes; }
     inline bool InstanceTypesHasBeenSet() const { return m_instanceTypesHasBeenSet; }

generated/src/aws-cpp-sdk-batch/include/aws/batch/model/ComputeResourceUpdate.h

@@ -205,21 +205,47 @@ namespace Model
      * <p>The instances types that can be launched. You can specify instance families
      * to launch any instance type within those families (for example, <code>c5</code>
      * or <code>p3</code>), or you can specify specific sizes within a family (such as
-     * <code>c5.8xlarge</code>). You can also choose <code>optimal</code> to select
-     * instance types (from the C4, M4, and R4 instance families) that match the demand
-     * of your job queues.</p> <p>When updating a compute environment, changing this
-     * setting requires an infrastructure update of the compute environment. For more
-     * information, see <a
-     * href="https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html">Updating
-     * compute environments</a> in the <i>Batch User Guide</i>.</p>  <p>This
-     * parameter isn't applicable to jobs that are running on Fargate resources. Don't
-     * specify it.</p>   <p>When you create a compute environment, the
-     * instance types that you select for the compute environment must share the same
-     * architecture. For example, you can't mix x86 and ARM instances in the same
-     * compute environment.</p>   <p>Currently, <code>optimal</code> uses
-     * instance types from the C4, M4, and R4 instance families. In Regions that don't
-     * have instance types from those instance families, instance types from the C5,
-     * M5, and R5 instance families are used.</p> 
+     * <code>c5.8xlarge</code>). </p> <p>Batch can select the instance type for you if
+     * you choose one of the following:</p> <ul> <li> <p> <code>optimal</code> to
+     * select instance types (from the <code>c4</code>, <code>m4</code>,
+     * <code>r4</code>, <code>c5</code>, <code>m5</code>, and <code>r5</code> instance
+     * families) that match the demand of your job queues. </p> </li> <li> <p>
+     * <code>default_x86_64</code> to choose x86 based instance types (from the
+     * <code>m6i</code>, <code>c6i</code>, <code>r6i</code>, and <code>c7i</code>
+     * instance families) that matches the resource demands of the job queue.</p> </li>
+     * <li> <p> <code>default_arm64</code> to choose x86 based instance types (from the
+     * <code>m6g</code>, <code>c6g</code>, <code>r6g</code>, and <code>c7g</code>
+     * instance families) that matches the resource demands of the job queue.</p> </li>
+     * </ul>  <p>Starting on 11/01/2025 the behavior of <code>optimal</code> is
+     * going to be changed to match <code>default_x86_64</code>. During the change your
+     * instance families could be updated to a newer generation. You do not need to
+     * perform any actions for the upgrade to happen. For more information about
+     * change, see <a
+     * href="https://docs.aws.amazon.com/batch/latest/userguide/optimal-default-instance-troubleshooting.html">Optimal
+     * instance type configuration to receive automatic instance family
+     * updates</a>.</p>   <p>Instance family availability varies by Amazon
+     * Web Services Region. For example, some Amazon Web Services Regions may not have
+     * any fourth generation instance families but have fifth and sixth generation
+     * instance families.</p> <p>When using <code>default_x86_64</code> or
+     * <code>default_arm64</code> instance bundles, Batch selects instance families
+     * based on a balance of cost-effectiveness and performance. While newer generation
+     * instances often provide better price-performance, Batch may choose an earlier
+     * generation instance family if it provides the optimal combination of
+     * availability, cost, and performance for your workload. For example, in an Amazon
+     * Web Services Region where both c6i and c7i instances are available, Batch might
+     * select c6i instances if they offer better cost-effectiveness for your specific
+     * job requirements. For more information on Batch instance types and Amazon Web
+     * Services Region availability, see <a
+     * href="https://docs.aws.amazon.com/batch/latest/userguide/instance-type-compute-table.html">Instance
+     * type compute table</a> in the <i>Batch User Guide</i>.</p> <p>Batch periodically
+     * updates your instances in default bundles to newer, more cost-effective options.
+     * Updates happen automatically without requiring any action from you. Your
+     * workloads continue running during updates with no interruption </p> 
+     *  <p>This parameter isn't applicable to jobs that are running on Fargate
+     * resources. Don't specify it.</p>   <p>When you create a compute
+     * environment, the instance types that you select for the compute environment must
+     * share the same architecture. For example, you can't mix x86 and ARM instances in
+     * the same compute environment.</p> 
      */
     inline const Aws::Vector<Aws::String>& GetInstanceTypes() const { return m_instanceTypes; }
     inline bool InstanceTypesHasBeenSet() const { return m_instanceTypesHasBeenSet; }

generated/src/aws-cpp-sdk-batch/include/aws/batch/model/LaunchTemplateSpecificationOverride.h

@@ -114,9 +114,10 @@ namespace Model
      * applied to.</p> <p>This parameter is required when defining a launch template
      * override.</p> <p>Information included in this parameter must meet the following
      * requirements:</p> <ul> <li> <p>Must be a valid Amazon EC2 instance type or
-     * family.</p> </li> <li> <p> <code>optimal</code> isn't allowed.</p> </li> <li>
-     * <p> <code>targetInstanceTypes</code> can target only instance types and families
-     * that are included within the <a
+     * family.</p> </li> <li> <p>The following Batch <code>InstanceTypes</code> are not
+     * allowed: <code>optimal</code>, <code>default_x86_64</code>, and
+     * <code>default_arm64</code>.</p> </li> <li> <p> <code>targetInstanceTypes</code>
+     * can target only instance types and families that are included within the <a
      * href="https://docs.aws.amazon.com/batch/latest/APIReference/API_ComputeResource.html#Batch-Type-ComputeResource-instanceTypes">
      * <code>ComputeResource.instanceTypes</code> </a> set.
      * <code>targetInstanceTypes</code> doesn't need to include all of the instances

generated/src/aws-cpp-sdk-batch/include/aws/batch/model/ListServiceJobsRequest.h

@@ -94,13 +94,24 @@ namespace Model
 
     ///@{
     /**
-     * <p>The filters to apply to the service job list query. The filter names and
-     * values can be:</p> <ul> <li> <p>name: <code>JOB_STATUS</code> </p> <p>values:
-     * <code>SUBMITTED | PENDING | RUNNABLE | STARTING | RUNNING | SUCCEEDED | FAILED |
-     * SCHEDULED</code> </p> </li> <li> <p>name: <code>JOB_NAME</code> </p> <p>values:
-     * case-insensitive matches for the job name. If a filter value ends with an
-     * asterisk (*), it matches any job name that begins with the string before the
-     * '*'.</p> </li> </ul>
+     * <p>The filter to apply to the query. Only one filter can be used at a time. When
+     * the filter is used, <code>jobStatus</code> is ignored. The results are sorted by
+     * the <code>createdAt</code> field, with the most recent jobs being first.</p>
+     * <dl> <dt>JOB_NAME</dt> <dd> <p>The value of the filter is a case-insensitive
+     * match for the job name. If the value ends with an asterisk (*), the filter
+     * matches any job name that begins with the string before the '*'. This
+     * corresponds to the <code>jobName</code> value. For example, <code>test1</code>
+     * matches both <code>Test1</code> and <code>test1</code>, and <code>test1*</code>
+     * matches both <code>test1</code> and <code>Test10</code>. When the
+     * <code>JOB_NAME</code> filter is used, the results are grouped by the job name
+     * and version.</p> </dd> <dt>BEFORE_CREATED_AT</dt> <dd> <p>The value for the
+     * filter is the time that's before the job was created. This corresponds to the
+     * <code>createdAt</code> value. The value is a string representation of the number
+     * of milliseconds since 00:00:00 UTC (midnight) on January 1, 1970.</p> </dd>
+     * <dt>AFTER_CREATED_AT</dt> <dd> <p>The value for the filter is the time that's
+     * after the job was created. This corresponds to the <code>createdAt</code> value.
+     * The value is a string representation of the number of milliseconds since
+     * 00:00:00 UTC (midnight) on January 1, 1970.</p> </dd> </dl>
      */
     inline const Aws::Vector<KeyValuesPair>& GetFilters() const { return m_filters; }
     inline bool FiltersHasBeenSet() const { return m_filtersHasBeenSet; }

generated/src/aws-cpp-sdk-batch/include/aws/batch/model/UpdateConsumableResourceRequest.h

@@ -80,9 +80,8 @@ namespace Model
     /**
      * <p>If this parameter is specified and two update requests with identical
      * payloads and <code>clientToken</code>s are received, these requests are
-     * considered the same request and the second request is rejected. A
-     * <code>clientToken</code> is valid for 8 hours or until one hour after the
-     * consumable resource is deleted, whichever is less.</p>
+     * considered the same request. Both requests will succeed, but the update will
+     * only happen once. A <code>clientToken</code> is valid for 8 hours.</p>
      */
     inline const Aws::String& GetClientToken() const { return m_clientToken; }
     inline bool ClientTokenHasBeenSet() const { return m_clientTokenHasBeenSet; }

generated/src/aws-cpp-sdk-bcm-dashboards/CMakeLists.txt

@@ -0,0 +1,76 @@
+add_project(aws-cpp-sdk-bcm-dashboards "C++ SDK for the AWS bcm-dashboards service" aws-cpp-sdk-core)
+
+file(GLOB AWS_BCM-DASHBOARDS_HEADERS
+    "include/aws/bcm-dashboards/*.h"
+)
+
+file(GLOB AWS_BCM-DASHBOARDS_MODEL_HEADERS
+    "include/aws/bcm-dashboards/model/*.h"
+)
+
+file(GLOB AWS_BCM-DASHBOARDS_SOURCE
+    "source/*.cpp"
+)
+
+file(GLOB AWS_BCM-DASHBOARDS_MODEL_SOURCE
+    "source/model/*.cpp"
+)
+
+file(GLOB BCM-DASHBOARDS_UNIFIED_HEADERS
+    ${AWS_BCM-DASHBOARDS_HEADERS}
+    ${AWS_BCM-DASHBOARDS_MODEL_HEADERS}
+)
+
+file(GLOB BCM-DASHBOARDS_UNITY_SRC
+    ${AWS_BCM-DASHBOARDS_SOURCE}
+    ${AWS_BCM-DASHBOARDS_MODEL_SOURCE}
+)
+
+if(ENABLE_UNITY_BUILD)
+    enable_unity_build("BCM-DASHBOARDS" BCM-DASHBOARDS_UNITY_SRC)
+endif()
+
+file(GLOB BCM-DASHBOARDS_SRC
+    ${BCM-DASHBOARDS_UNIFIED_HEADERS}
+    ${BCM-DASHBOARDS_UNITY_SRC}
+)
+
+if(WIN32)
+    #if we are compiling for visual studio, create a sane directory tree.
+    if(MSVC)
+        source_group("Header Files\\aws\\bcm-dashboards" FILES ${AWS_BCM-DASHBOARDS_HEADERS})
+        source_group("Header Files\\aws\\bcm-dashboards\\model" FILES ${AWS_BCM-DASHBOARDS_MODEL_HEADERS})
+        source_group("Source Files" FILES ${AWS_BCM-DASHBOARDS_SOURCE})
+        source_group("Source Files\\model" FILES ${AWS_BCM-DASHBOARDS_MODEL_SOURCE})
+    endif(MSVC)
+endif()
+
+set(BCM-DASHBOARDS_INCLUDES
+    "${CMAKE_CURRENT_SOURCE_DIR}/include/"
+)
+
+add_library(${PROJECT_NAME} ${BCM-DASHBOARDS_SRC})
+add_library(AWS::${PROJECT_NAME} ALIAS ${PROJECT_NAME})
+
+set_compiler_flags(${PROJECT_NAME})
+set_compiler_warnings(${PROJECT_NAME})
+
+if(USE_WINDOWS_DLL_SEMANTICS AND BUILD_SHARED_LIBS)
+    target_compile_definitions(${PROJECT_NAME} PRIVATE "AWS_BCMDASHBOARDS_EXPORTS")
+endif()
+
+target_include_directories(${PROJECT_NAME} PUBLIC
+    $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/include>
+    $<INSTALL_INTERFACE:include>)
+
+target_link_libraries(${PROJECT_NAME} PRIVATE ${PLATFORM_DEP_LIBS} ${PROJECT_LIBS})
+
+
+setup_install()
+
+install (FILES ${AWS_BCM-DASHBOARDS_HEADERS} DESTINATION ${INCLUDE_DIRECTORY}/aws/bcm-dashboards)
+install (FILES ${AWS_BCM-DASHBOARDS_MODEL_HEADERS} DESTINATION ${INCLUDE_DIRECTORY}/aws/bcm-dashboards/model)
+
+do_packaging()
+
+