Update to latest models

Author: aws-sdk-python-automation

.changes/next-release/api-change-bedrock-88595.json

@@ -0,0 +1,5 @@
+{
+  "type": "api-change",
+  "category": "``bedrock``",
+  "description": "You can now generate policy scenarios on demand using the new GENERATE POLICY SCENARIOS build workflow type. Scenarios will no longer be automatically generated during INGEST CONTENT, REFINE POLICY, and IMPORT POLICY workflows, resulting in faster completion times for these operations."
+}

.changes/next-release/api-change-bedrockagentcore-69448.json

@@ -0,0 +1,5 @@
+{
+  "type": "api-change",
+  "category": "``bedrock-agentcore``",
+  "description": "Provide support to perform deterministic operations on agent runtime through shell command executions via the new InvokeAgentRuntimeCommand API"
+}

.changes/next-release/api-change-bedrockagentcorecontrol-2803.json

@@ -0,0 +1,5 @@
+{
+  "type": "api-change",
+  "category": "``bedrock-agentcore-control``",
+  "description": "Supporting hosting of public ECR Container Images in AgentCore Runtime"
+}

.changes/next-release/api-change-ecs-81199.json

@@ -0,0 +1,5 @@
+{
+  "type": "api-change",
+  "category": "``ecs``",
+  "description": "Amazon ECS now supports configuring whether tags are propagated to the EC2 Instance Metadata Service (IMDS) for instances launched by the Managed Instances capacity provider. This gives customers control over tag visibility in IMDS when using ECS Managed Instances."
+}

awscli/botocore/data/bedrock-agentcore-control/2023-06-05/service-2.json

@@ -9420,7 +9420,7 @@
       "type":"string",
       "max":1024,
       "min":1,
-      "pattern":"([0-9]{12})\\.dkr\\.ecr\\.([a-z0-9-]+)\\.amazonaws\\.com/((?:[a-z0-9]+(?:[._-][a-z0-9]+)*/)*[a-z0-9]+(?:[._-][a-z0-9]+)*)(?::([^:@]{1,300}))?(?:@(.+))?"
+      "pattern":"(([0-9]{12})\\.dkr\\.ecr\\.([a-z0-9-]+)\\.amazonaws\\.com(\\.cn)?|public\\.ecr\\.aws)/((?:[a-z0-9]+(?:[._-][a-z0-9]+)*/)*[a-z0-9]+(?:[._-][a-z0-9]+)*)(?::([^:@]{1,300}))?(?:@(.+))?"
     },
     "RuntimeMetadataConfiguration":{
       "type":"structure",

awscli/botocore/data/bedrock-agentcore/2024-02-28/service-2.json

@@ -3126,7 +3126,8 @@
         "INGEST_CONTENT",
         "REFINE_POLICY",
         "IMPORT_POLICY",
-        "GENERATE_FIDELITY_REPORT"
+        "GENERATE_FIDELITY_REPORT",
+        "GENERATE_POLICY_SCENARIOS"
       ]
     },
     "AutomatedReasoningPolicyConflictedRuleIdList":{

awscli/botocore/data/bedrock/2023-04-20/service-2.json

@@ -4595,6 +4595,10 @@
           "shape":"CapacityOptionType",
           "documentation":"<p>The capacity option type. This determines whether Amazon ECS launches On-Demand, Spot or Capacity Reservation Instances for your managed instance capacity provider.</p> <p>Valid values are:</p> <ul> <li> <p> <code>ON_DEMAND</code> - Launches standard On-Demand Instances. On-Demand Instances provide predictable pricing and availability.</p> </li> <li> <p> <code>SPOT</code> - Launches Spot Instances that use spare Amazon EC2 capacity at reduced cost. Spot Instances can be interrupted by Amazon EC2 with a two-minute notification when the capacity is needed back.</p> </li> <li> <p> <code>RESERVED</code> - Launches Instances using Amazon EC2 Capacity Reservations. Capacity Reservations allow you to reserve compute capacity for Amazon EC2 instances in a specific Availability Zone.</p> </li> </ul> <p>The default is On-Demand</p> <p>For more information about Amazon EC2 capacity options, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-purchasing-options.html\">Instance purchasing options</a> in the <i>Amazon EC2 User Guide</i>.</p>"
         },
+        "instanceMetadataTagsPropagation":{
+          "shape":"BoxedBoolean",
+          "documentation":"<p>Determines whether tags are propagated to the instance metadata service (IMDS) for Amazon EC2 instances launched by the Managed Instances capacity provider. When enabled, all tags associated with the instance are available through the instance metadata service. When disabled, tags are not propagated to IMDS.</p> <p>Disable this setting if your tags contain characters that are not compatible with IMDS, such as <code>/</code>. IMDS requires tag keys to match the pattern <code>[0-9a-zA-Z\\-_+=,.@:]{1,255}</code>.</p> <p>The default value is <code>true</code>.</p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html#work-with-tags-in-IMDS\">Work with instance tags in instance metadata</a> in the <i>Amazon EC2 User Guide</i>.</p>"
+        },
         "instanceRequirements":{
           "shape":"InstanceRequirementsRequest",
           "documentation":"<p>The instance requirements. You can specify:</p> <ul> <li> <p>The instance types</p> </li> <li> <p>Instance requirements such as vCPU count, memory, network performance, and accelerator specifications</p> </li> </ul> <p>Amazon ECS automatically selects the instances that match the specified criteria.</p>"
@@ -4625,6 +4629,10 @@
           "shape":"ManagedInstancesStorageConfiguration",
           "documentation":"<p>The updated storage configuration for Amazon ECS Managed Instances. Changes to storage settings apply to new instances launched after the update.</p>"
         },
+        "instanceMetadataTagsPropagation":{
+          "shape":"BoxedBoolean",
+          "documentation":"<p>Determines whether tags are propagated to the instance metadata service (IMDS) for Amazon EC2 instances launched by the Managed Instances capacity provider. When enabled, all tags associated with the instance are available through the instance metadata service. When disabled, tags are not propagated to IMDS.</p> <p>Disable this setting if your tags contain characters that are not compatible with IMDS, such as <code>/</code>. IMDS requires tag keys to match the pattern <code>[0-9a-zA-Z\\-_+=,.@:]{1,255}</code>.</p> <p>The default value is <code>true</code>.</p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html#work-with-tags-in-IMDS\">Work with instance tags in instance metadata</a> in the <i>Amazon EC2 User Guide</i>.</p>"
+        },
         "monitoring":{
           "shape":"ManagedInstancesMonitoringOptions",
           "documentation":"<p>CloudWatch provides two categories of monitoring: basic monitoring and detailed monitoring. By default, your managed instance is configured for basic monitoring. You can optionally enable detailed monitoring to help you more quickly identify and act on operational issues. You can enable or turn off detailed monitoring at launch or when the managed instance is running or stopped. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/detailed-monitoring-managed-instances.html\">Detailed monitoring for Amazon ECS Managed Instances</a> in the Amazon ECS Developer Guide.</p>"