Skip to content

Commit 28fa900

Browse files
Merging v1.4.106 release
2 parents d08b78e + e0ec1b2 commit 28fa900

16 files changed

Lines changed: 14512 additions & 904 deletions

CHANGELOG.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,24 @@
11
# Changelog
22

3+
## [1.4.106] - 06/17/2025
4+
5+
### Features
6+
* (**accessanalyzer**) We are launching a new analyzer type, internal access analyzer. The new analyzer will generate internal access findings, which help customers understand who within their AWS organization or AWS Account has access to their critical AWS resources.
7+
* (**acm**) Adds support for Exportable Public Certificates
8+
* (**backup**) AWS Backup is adding support for integration of its logically air-gapped vaults with the AWS Organizations Multi-party approval capability.
9+
* (**databasemigrationservice**) Add "Virtual" field to Data Provider as well as "S3Path" and "S3AccessRoleArn" fields to DataProvider settings
10+
* (**guardduty**) Adding support for extended threat detection for EKS Audit Logs and EKS Runtime Monitoring.
11+
* (**inspector2**) Add Code Repository Scanning as part of AWS InspectorV2
12+
* (**mpa**) This release enables customers to create Multi-party approval teams and approval requests to protect supported operations.
13+
* (**networkfirewall**) Release of Active Threat Defense in Network Firewall
14+
* (**organizations**) Add support for policy operations on the SECURITYHUB_POLICY policy type.
15+
* (**securityhub**) Adds operations, structures, and exceptions required for public preview release of Security Hub V2.
16+
* (**sts**) The AWS Security Token Service APIs AssumeRoleWithSAML and AssumeRoleWithWebIdentity can now be invoked without pre-configured AWS credentials in the SDK configuration.
17+
* (**wafv2**) AWS WAF can now suggest protection packs for you based on the application information you provide when you create a webACL.
18+
19+
### Documentation
20+
* (**bedrock**) This release of the SDK has the API and documentation for the createcustommodel API. This feature lets you copy a trained model into Amazon Bedrock for inference.
21+
322
## [1.4.105] - 06/16/2025
423

524
### Features

codegen/sdk/aws-models/accessanalyzer.json

Lines changed: 518 additions & 230 deletions
Large diffs are not rendered by default.

codegen/sdk/aws-models/acm.json

Lines changed: 217 additions & 111 deletions
Large diffs are not rendered by default.

codegen/sdk/aws-models/backup.json

Lines changed: 632 additions & 10 deletions
Large diffs are not rendered by default.

codegen/sdk/aws-models/bedrock.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1282,7 +1282,7 @@
12821282
}
12831283
],
12841284
"traits": {
1285-
"smithy.api#documentation": "<p>Creates a new custom model in Amazon Bedrock from an existing SageMaker AI-trained Amazon Nova model stored in an Amazon-managed Amazon S3 bucket. After the model is active, you can use it for inference.</p> <p>To use the model for inference, you must purchase Provisioned Throughput for it. You can't use On-demand inference with these custom models. For more information about Provisioned Throughput, see <a href=\"https://docs.aws.amazon.com/bedrock/latest/userguide/prov-throughput.html\">Provisioned Throughput</a>.</p> <p>The model appears in <code>ListCustomModels</code> with a <code>customizationType</code> of <code>imported</code>. To track the status of the new model, you use the <code>GetCustomModel</code> API operation. The model can be in the following states:</p> <ul> <li> <p> <code>Creating</code> - Initial state during validation and registration</p> </li> <li> <p> <code>Active</code> - Model is ready for use in inference</p> </li> <li> <p> <code>Failed</code> - Creation process encountered an error</p> </li> </ul> <p>For more information about creating custom models, including specific model requirements, see <a href=\"https://docs.aws.amazon.com/bedrock/latest/userguide/create-custom-model-from-existing.html\">Import a SageMaker AI-trained Amazon Nova model</a> in the Amazon Bedrock User Guide. </p> <note> <p>You use the <code>CreateCustomModel</code> API to import only SageMaker AI-trained Amazon Nova models. To import open-source models, you use the <a href=\"https://docs.aws.amazon.com/bedrock/latest/APIReference/API_CreateModelImportJob.html\">CreateModelImportJob</a>. </p> </note> <p> <b>Related APIs</b> </p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/bedrock/latest/APIReference/API_GetCustomModel.html\">GetCustomModel</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/bedrock/latest/APIReference/API_ListCustomModels.html\">ListCustomModels</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/bedrock/latest/APIReference/API_DeleteCustomModel.html\">DeleteCustomModel</a> </p> </li> </ul>",
1285+
"smithy.api#documentation": "<p>Creates a new custom model in Amazon Bedrock. After the model is active, you can use it for inference.</p> <p>To use the model for inference, you must purchase Provisioned Throughput for it. You can't use On-demand inference with these custom models. For more information about Provisioned Throughput, see <a href=\"https://docs.aws.amazon.com/bedrock/latest/userguide/prov-throughput.html\">Provisioned Throughput</a>.</p> <p>The model appears in <code>ListCustomModels</code> with a <code>customizationType</code> of <code>imported</code>. To track the status of the new model, you use the <code>GetCustomModel</code> API operation. The model can be in the following states:</p> <ul> <li> <p> <code>Creating</code> - Initial state during validation and registration</p> </li> <li> <p> <code>Active</code> - Model is ready for use in inference</p> </li> <li> <p> <code>Failed</code> - Creation process encountered an error</p> </li> </ul> <p> <b>Related APIs</b> </p> <ul> <li> <p> <a href=\"https://docs.aws.amazon.com/bedrock/latest/APIReference/API_GetCustomModel.html\">GetCustomModel</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/bedrock/latest/APIReference/API_ListCustomModels.html\">ListCustomModels</a> </p> </li> <li> <p> <a href=\"https://docs.aws.amazon.com/bedrock/latest/APIReference/API_DeleteCustomModel.html\">DeleteCustomModel</a> </p> </li> </ul>",
12861286
"smithy.api#examples": [
12871287
{
12881288
"title": "Successful CreateCustomModel API call",
@@ -1332,7 +1332,7 @@
13321332
"modelSourceConfig": {
13331333
"target": "com.amazonaws.bedrock#ModelDataSource",
13341334
"traits": {
1335-
"smithy.api#documentation": "<p>The data source for the model. The Amazon S3 URI in the model source must be for the Amazon-managed Amazon S3 bucket containing your model artifacts. SageMaker AI creates this bucket when you run your first SageMaker AI training job.</p>",
1335+
"smithy.api#documentation": "<p>The data source for the model. The Amazon S3 URI in the model source must be for the Amazon-managed Amazon S3 bucket containing your model artifacts.</p>",
13361336
"smithy.api#required": {}
13371337
}
13381338
},
@@ -12910,7 +12910,7 @@
1291012910
}
1291112911
},
1291212912
"traits": {
12913-
"smithy.api#documentation": "<p>The Amazon S3 data source of the model to import. For the <a href=\"https://docs.aws.amazon.com/bedrock/latest/APIReference/API_CreateCustomModel.html\">CreateCustomModel</a> API operation, you must specify the Amazon S3 URI for the Amazon-managed Amazon S3 bucket containing your model artifacts. SageMaker AI creates this bucket when you run your first SageMaker AI training job.</p>"
12913+
"smithy.api#documentation": "<p>The Amazon S3 data source of the model to import. </p>"
1291412914
}
1291512915
},
1291612916
"com.amazonaws.bedrock#S3InputFormat": {

0 commit comments

Comments
 (0)