AWS bedrock documentation change
Summary
Updated API usage documentation: changed blueprint ARN submission limit from single to multiple per request and replaced 'job ID' with 'invocationArn' terminology
Security assessment
The changes reflect feature enhancements (multiple blueprint support) and terminology updates. No security vulnerabilities, mitigations, or security-specific configurations are mentioned. Permission error references are standard API documentation elements.
Diff
diff --git a/bedrock/latest/userguide/bda-using-api.md b/bedrock/latest/userguide/bda-using-api.md index c46332f13..0d352b468 100644 --- a//bedrock/latest/userguide/bda-using-api.md +++ b//bedrock/latest/userguide/bda-using-api.md @@ -58 +58 @@ Async -You have a project set up, you can start processing images using the [InvokeDataAutomationAsync](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_data-automation-runtime_InvokeDataAutomationAsync.html) operation. If using custom output, you can only submit a single blueprint ARN per request. +You have a project set up, you can start processing images using the [InvokeDataAutomationAsync](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_data-automation-runtime_InvokeDataAutomationAsync.html) operation. If using custom output, you can submit one or more blueprint ARNs per request. @@ -60 +60 @@ You have a project set up, you can start processing images using the [InvokeData -This API call initiates the asynchronous processing of your files in a specified S3 bucket. The API accepts the project ARN and the file to be processed, then starts the asynchronous processing job. A job ID is returned for tracking the process. Errors will be raised if the project doesn't exist, or if the caller doesn't have the necessary permissions, or if the input files aren't in a supported format. +This API call initiates the asynchronous processing of your files in a specified S3 bucket. The API accepts the project ARN and the file to be processed, then starts the asynchronous processing job. An `invocationArn` is returned for tracking the process. Errors will be raised if the project doesn't exist, or if the caller doesn't have the necessary permissions, or if the input files aren't in a supported format.