Update to latest models

.changes/next-release/api-change-bedrockruntime-15994.json

@@ -0,0 +1,5 @@
+{
+  "type": "api-change",
+  "category": "``bedrock-runtime``",
+  "description": "Allow hyphens in tool name for Converse and ConverseStream APIs"
+}

.changes/next-release/api-change-detective-2187.json

@@ -0,0 +1,5 @@
+{
+  "type": "api-change",
+  "category": "``detective``",
+  "description": "Doc only update for Detective documentation."
+}

.changes/next-release/api-change-ec2-76117.json

@@ -0,0 +1,5 @@
+{
+  "type": "api-change",
+  "category": "``ec2``",
+  "description": "Release u7i-6tb.112xlarge, u7i-8tb.112xlarge, u7inh-32tb.480xlarge, p5e.48xlarge, p5en.48xlarge, f2.12xlarge, f2.48xlarge, trn2.48xlarge instance types."
+}

.changes/next-release/api-change-notifications-16338.json

@@ -0,0 +1,5 @@
+{
+  "type": "api-change",
+  "category": "``notifications``",
+  "description": "Added support for Managed Notifications, integration with AWS Organization and added aggregation summaries for Aggregate Notifications"
+}

.changes/next-release/api-change-sagemaker-15670.json

@@ -0,0 +1,5 @@
+{
+  "type": "api-change",
+  "category": "``sagemaker``",
+  "description": "Correction of docs for  \"Added support for ml.trn1.32xlarge instance type in Reserved Capacity Offering\""
+}

botocore/data/bedrock-runtime/2023-09-30/service-2.json

@@ -2744,7 +2744,7 @@
       "type":"string",
       "max":64,
       "min":1,
-      "pattern":"[a-zA-Z][a-zA-Z0-9_]*"
+      "pattern":"[a-zA-Z0-9_-]+"
     },
     "ToolResultBlock":{
       "type":"structure",

botocore/data/detective/2018-10-26/service-2.json

@@ -5,11 +5,13 @@
     "endpointPrefix":"api.detective",
     "jsonVersion":"1.1",
     "protocol":"rest-json",
+    "protocols":["rest-json"],
     "serviceFullName":"Amazon Detective",
     "serviceId":"Detective",
     "signatureVersion":"v4",
     "signingName":"detective",
-    "uid":"detective-2018-10-26"
+    "uid":"detective-2018-10-26",
+    "auth":["aws.auth#sigv4"]
   },
   "operations":{
     "AcceptInvitation":{
@@ -446,7 +448,7 @@
         {"shape":"ServiceQuotaExceededException"},
         {"shape":"ValidationException"}
       ],
-      "documentation":"<p>Starts a data source packages for the behavior graph.</p>"
+      "documentation":"<p>Starts a data source package for the Detective behavior graph.</p>"
     },
     "UpdateInvestigationState":{
       "name":"UpdateInvestigationState",
@@ -1154,7 +1156,7 @@
           "documentation":"<p>Contains details about related finding groups.</p>"
         }
       },
-      "documentation":"<p>Details about the indicators of compromise which are used to determine if a resource is involved in a security incident. An indicator of compromise (IOC) is an artifact observed in or on a network, system, or environment that can (with a high level of confidence) identify malicious activity or a security incident. For the list of indicators of compromise that are generated by Detective investigations, see <a href=\"https://docs.aws.amazon.com/detective/latest/userguide/detective-investigations.html\">Detective investigations</a>.</p>"
+      "documentation":"<p>Details about the indicators of compromise which are used to determine if a resource is involved in a security incident. An indicator of compromise (IOC) is an artifact observed in or on a network, system, or environment that can (with a high level of confidence) identify malicious activity or a security incident. For the list of indicators of compromise that are generated by Detective investigations, see <a href=\"https://docs.aws.amazon.com/detective/latest/userguide/detective-investigation-about.html\">Detective investigations</a>.</p>"
     },
     "IndicatorType":{
       "type":"string",
@@ -1314,7 +1316,7 @@
         },
         "IndicatorType":{
           "shape":"IndicatorType",
-          "documentation":"<p>For the list of indicators of compromise that are generated by Detective investigations, see <a href=\"https://docs.aws.amazon.com/detective/latest/userguide/detective-investigations.html\">Detective investigations</a>.</p>"
+          "documentation":"<p>For the list of indicators of compromise that are generated by Detective investigations, see <a href=\"https://docs.aws.amazon.com/detective/latest/userguide/detective-investigation-about.html\">Detective investigations</a>.</p>"
         },
         "NextToken":{
           "shape":"AiPaginationToken",
@@ -2047,7 +2049,7 @@
         },
         "DatasourcePackages":{
           "shape":"DatasourcePackageList",
-          "documentation":"<p>The data source package start for the behavior graph.</p>"
+          "documentation":"<p>The data source package to start for the behavior graph.</p>"
         }
       }
     },
@@ -2116,5 +2118,5 @@
       "value":{"shape":"DatasourcePackageUsageInfo"}
     }
   },
-  "documentation":"<p>Detective uses machine learning and purpose-built visualizations to help you to analyze and investigate security issues across your Amazon Web Services (Amazon Web Services) workloads. Detective automatically extracts time-based events such as login attempts, API calls, and network traffic from CloudTrail and Amazon Virtual Private Cloud (Amazon VPC) flow logs. It also extracts findings detected by Amazon GuardDuty.</p> <p>The Detective API primarily supports the creation and management of behavior graphs. A behavior graph contains the extracted data from a set of member accounts, and is created and managed by an administrator account.</p> <p>To add a member account to the behavior graph, the administrator account sends an invitation to the account. When the account accepts the invitation, it becomes a member account in the behavior graph.</p> <p>Detective is also integrated with Organizations. The organization management account designates the Detective administrator account for the organization. That account becomes the administrator account for the organization behavior graph. The Detective administrator account is also the delegated administrator account for Detective in Organizations.</p> <p>The Detective administrator account can enable any organization account as a member account in the organization behavior graph. The organization accounts do not receive invitations. The Detective administrator account can also invite other accounts to the organization behavior graph.</p> <p>Every behavior graph is specific to a Region. You can only use the API to manage behavior graphs that belong to the Region that is associated with the currently selected endpoint.</p> <p>The administrator account for a behavior graph can use the Detective API to do the following:</p> <ul> <li> <p>Enable and disable Detective. Enabling Detective creates a new behavior graph.</p> </li> <li> <p>View the list of member accounts in a behavior graph.</p> </li> <li> <p>Add member accounts to a behavior graph.</p> </li> <li> <p>Remove member accounts from a behavior graph.</p> </li> <li> <p>Apply tags to a behavior graph.</p> </li> </ul> <p>The organization management account can use the Detective API to select the delegated administrator for Detective.</p> <p>The Detective administrator account for an organization can use the Detective API to do the following:</p> <ul> <li> <p>Perform all of the functions of an administrator account.</p> </li> <li> <p>Determine whether to automatically enable new organization accounts as member accounts in the organization behavior graph.</p> </li> </ul> <p>An invited member account can use the Detective API to do the following:</p> <ul> <li> <p>View the list of behavior graphs that they are invited to.</p> </li> <li> <p>Accept an invitation to contribute to a behavior graph.</p> </li> <li> <p>Decline an invitation to contribute to a behavior graph.</p> </li> <li> <p>Remove their account from a behavior graph.</p> </li> </ul> <p>All API actions are logged as CloudTrail events. See <a href=\"https://docs.aws.amazon.com/detective/latest/adminguide/logging-using-cloudtrail.html\">Logging Detective API Calls with CloudTrail</a>.</p> <note> <p>We replaced the term \"master account\" with the term \"administrator account\". An administrator account is used to centrally manage multiple accounts. In the case of Detective, the administrator account manages the accounts in their behavior graph.</p> </note>"
+  "documentation":"<p>Detective uses machine learning and purpose-built visualizations to help you to analyze and investigate security issues across your Amazon Web Services (Amazon Web Services) workloads. Detective automatically extracts time-based events such as login attempts, API calls, and network traffic from CloudTrail and Amazon Virtual Private Cloud (Amazon VPC) flow logs. It also extracts findings detected by Amazon GuardDuty.</p> <p>The Detective API primarily supports the creation and management of behavior graphs. A behavior graph contains the extracted data from a set of member accounts, and is created and managed by an administrator account.</p> <p>To add a member account to the behavior graph, the administrator account sends an invitation to the account. When the account accepts the invitation, it becomes a member account in the behavior graph.</p> <p>Detective is also integrated with Organizations. The organization management account designates the Detective administrator account for the organization. That account becomes the administrator account for the organization behavior graph. The Detective administrator account is also the delegated administrator account for Detective in Organizations.</p> <p>The Detective administrator account can enable any organization account as a member account in the organization behavior graph. The organization accounts do not receive invitations. The Detective administrator account can also invite other accounts to the organization behavior graph.</p> <p>Every behavior graph is specific to a Region. You can only use the API to manage behavior graphs that belong to the Region that is associated with the currently selected endpoint.</p> <p>The administrator account for a behavior graph can use the Detective API to do the following:</p> <ul> <li> <p>Enable and disable Detective. Enabling Detective creates a new behavior graph.</p> </li> <li> <p>View the list of member accounts in a behavior graph.</p> </li> <li> <p>Add member accounts to a behavior graph.</p> </li> <li> <p>Remove member accounts from a behavior graph.</p> </li> <li> <p>Apply tags to a behavior graph.</p> </li> </ul> <p>The organization management account can use the Detective API to select the delegated administrator for Detective.</p> <p>The Detective administrator account for an organization can use the Detective API to do the following:</p> <ul> <li> <p>Perform all of the functions of an administrator account.</p> </li> <li> <p>Determine whether to automatically enable new organization accounts as member accounts in the organization behavior graph.</p> </li> </ul> <p>An invited member account can use the Detective API to do the following:</p> <ul> <li> <p>View the list of behavior graphs that they are invited to.</p> </li> <li> <p>Accept an invitation to contribute to a behavior graph.</p> </li> <li> <p>Decline an invitation to contribute to a behavior graph.</p> </li> <li> <p>Remove their account from a behavior graph.</p> </li> </ul> <p>All API actions are logged as CloudTrail events. See <a href=\"https://docs.aws.amazon.com/detective/latest/userguide/logging-using-cloudtrail.html\">Logging Detective API Calls with CloudTrail</a>.</p> <note> <p>We replaced the term \"master account\" with the term \"administrator account\". An administrator account is used to centrally manage multiple accounts. In the case of Detective, the administrator account manages the accounts in their behavior graph.</p> </note>"
 }