AWS bedrock documentation change
Summary
Added new error codes (BadCScoreException, FTUFormNotFilled, AWS Marketplace Agreement errors) and expanded troubleshooting guidance for multiple exceptions including IAM permissions, signature validation, and marketplace subscription processes
Security assessment
Changes add documentation about authorization requirements (BadCScoreException), IAM permission checks, and temporary credential validation which are security-related best practices. However, there is no evidence these changes address a specific disclosed vulnerability or security incident.
Diff
diff --git a/bedrock/latest/userguide/troubleshooting-api-error-codes.md b/bedrock/latest/userguide/troubleshooting-api-error-codes.md index ea3b34b73..52bccbef6 100644 --- a//bedrock/latest/userguide/troubleshooting-api-error-codes.md +++ b//bedrock/latest/userguide/troubleshooting-api-error-codes.md @@ -5 +5 @@ -AccessDeniedExceptionIncompleteSignatureInternalFailureInvalidActionInvalidClientTokenIdNotAuthorizedRequestExpiredServiceUnavailableThrottlingExceptionValidationErrorResourceNotFound +AccessDeniedExceptionBadCScoreExceptionFTUFormNotFilledIncompleteSignatureInternalFailureInvalidActionInvalidClientTokenIdAWS Marketplace Agreement Failed within 15 minutesAWS Marketplace Agreement Pending after 15 minutesMPAgreementBeingCreatedNotAuthorizedRequestExpiredServiceUnavailableThrottlingExceptionValidationErrorResourceNotFound @@ -13 +13,9 @@ This section provides detailed information about the common errors you might enc -**HTTP Status Code:** 400 +**HTTP Status Code:** 403 + +**Cause:** You do not have sufficient permissions to perform the requested action. + +**Solution:** + + * Verify that your IAM user or role has the necessary permissions for the action you are attempting. + + * If you are using temporary security credentials, ensure they haven't expired. @@ -15 +23,8 @@ This section provides detailed information about the common errors you might enc -**Cause:** You do not have sufficient permissions to perform the requested action + + + +## BadCScoreException + +**HTTP Status Code:** 403 + +**Cause:** Your account is not authorized to access this model @@ -19 +34 @@ This section provides detailed information about the common errors you might enc - * Verify that your IAM user or role has the necessary permissions for the action you are attempting + * Contact AWS Support for further details @@ -21 +36,12 @@ This section provides detailed information about the common errors you might enc - * If you are using temporary security credentials, ensure they haven't expired + + + +## FTUFormNotFilled + +**HTTP Status Code:** 404 + +**Cause:** Model use case details have not been submitted for this account + +**Solution:** + + * Fill out the Anthropic use case details form before using the model @@ -30 +56 @@ This section provides detailed information about the common errors you might enc -**Cause:** The request signature does not conform to AWS standards +**Cause:** The request signature does not conform to AWS standards. @@ -34 +60 @@ This section provides detailed information about the common errors you might enc - * Ensure you are using an AWS SDK version that supports Amazon Bedrock + * Ensure you are using an AWS SDK version that supports Amazon Bedrock. @@ -36 +62 @@ This section provides detailed information about the common errors you might enc - * Verify that your AWS access key ID and secret key are correctly configured + * Verify that your AWS access key ID and secret key are correctly configured. @@ -38 +64 @@ This section provides detailed information about the common errors you might enc - * If you are manually signing requests, we suggest double-checking your signature calculation process + * If you are manually signing requests, we suggest double-checking your signature calculation process. @@ -66 +92 @@ This section provides detailed information about the common errors you might enc - * We suggest double-checking the spelling and formatting of the action name in your request + * We suggest double-checking the spelling and formatting of the action name in your request. @@ -68 +94 @@ This section provides detailed information about the common errors you might enc - * Verify that the action calling is supported by Amazon Bedrock and is correctly documented as shown in [Amazon Bedrock API Reference](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_Operations.html) + * Verify that the action calling is supported by Amazon Bedrock and is correctly documented as shown in [Amazon Bedrock API Reference.](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_Operations.html) @@ -70 +96 @@ This section provides detailed information about the common errors you might enc - * Ensure you are using the most up-to-date version of the AWS SDK or CLI + * Ensure you are using the most up-to-date version of the AWS SDK or CLI. @@ -79 +105,16 @@ This section provides detailed information about the common errors you might enc -**Cause:** The X.509 certificate or AWS access key ID provided does not exist in our records +**Cause:** The X.509 certificate or AWS access key ID provided does not exist in our records. + +**Solution:** + + * Verify that you are using the correct AWS access key ID. + + * If you recently created new access keys, ensure you are using the new credentials and not the old ones. + + + + +## AWS Marketplace Agreement Failed within 15 minutes + +**HTTP Status Code:** 403 + +**Cause:** The AWS Marketplace Agreement failed due to an underlying issue. @@ -83 +124,3 @@ This section provides detailed information about the common errors you might enc - * Verify that you are using the correct AWS access key ID + * Review the error message and remediate the underlying issue. Common underlying issues are invalid payment error and restricted geo-location. + + * For invalid payment error, please review [Restriction on credit and debit card purchases for AISPL customers using AWS Marketplace](https://aws-blogs-prod.amazon.com/awsmarketplace/restriction-on-credit-and-debit-card-purchases-for-aispl-customers-using-aws-marketplace/) and [INVALID_PAYMENT_INSTRUMENT after requesting model access in Amazon Bedrock.](https://repost.aws/questions/QU0UOsutrWSSS4nOqgHcIUJg/invalid-payment-instrument-after-requesting-model-access-in-amazon-bedrock). @@ -85 +128,25 @@ This section provides detailed information about the common errors you might enc - * If you recently created new access keys, ensure you are using the new credentials and not the old ones + + + +## AWS Marketplace Agreement Pending after 15 minutes + +**HTTP Status Code:** 403 + +**Cause:** The AWS Marketplace Agreement has not succeeded and it has been 15 minutes since the request was made. + +**Solution:** + + * Try the request again every 15 minutes. If the issue persists, please contact [AWS Support Center](https://aws.amazon.com/support) and provide details about your request and the error you are encountering. + + + + +## MPAgreementBeingCreated + +**HTTP Status Code:** 403 + +**Cause:** Your account is not authorized to access this model. Your AWS Marketplace subscription for this model is still being processed + +**Solution:** + + * Try again after 15 minutes @@ -94 +161 @@ This section provides detailed information about the common errors you might enc -**Cause:** You do not have permission to perform this action +**Cause:** You do not have permission to perform this action. @@ -98 +165 @@ This section provides detailed information about the common errors you might enc - * Review your IAM permissions and ensure you have the necessary rights to perform the requested action on Amazon Bedrock resources + * Review your IAM permissions and ensure you have the necessary rights to perform the requested action on Amazon Bedrock resources. @@ -100 +167 @@ This section provides detailed information about the common errors you might enc - * If you are using an IAM role, verify that the role has the appropriate permissions and trust relationships + * If you are using an IAM role, verify that the role has the appropriate permissions and trust relationships. @@ -102 +169 @@ This section provides detailed information about the common errors you might enc - * Check for any organizational policies or service control policies that might be restricting your access + * Check for any organizational policies or service control policies that might be restricting your access. @@ -111 +178 @@ This section provides detailed information about the common errors you might enc -**Cause:** The request is no longer valid due to expired timestamps +**Cause:** The request is no longer valid due to expired timestamps. @@ -115 +182 @@ This section provides detailed information about the common errors you might enc - * Ensure your system clock is correctly synchronized with a reliable time source + * Ensure your system clock is correctly synchronized with a reliable time source. @@ -117 +184 @@ This section provides detailed information about the common errors you might enc - * If you are making requests from different time zones, be aware of potential timestamp discrepancies + * If you are making requests from different time zones, be aware of potential timestamp discrepancies. @@ -130 +197 @@ This section provides detailed information about the common errors you might enc - * We suggest employing AWS recommended approach of using [retries with exponential backoff](https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/retry-backoff.html) and random [jitter](https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/) for improved reliability + * We suggest employing AWS recommended approach of using [retries with exponential backoff](https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/retry-backoff.html) and random [jitter](https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/) for improved reliability. @@ -132 +199 @@ This section provides detailed information about the common errors you might enc - * Consider switching to a different AWS Region if the issue persists in your current Region. Different Regions may have varying levels of load and availability + * Consider switching to a different AWS Region if the issue persists in your current Region. Different Regions may have varying levels of load and availability. @@ -134 +201 @@ This section provides detailed information about the common errors you might enc - * [Use Cross-Region inference](https://docs.aws.amazon.com/bedrock/latest/userguide/cross-region-inference.html) to seamlessly manage unplanned traffic bursts by utilizing compute across different AWS Regions + * [Use Cross-Region inference](https://docs.aws.amazon.com/bedrock/latest/userguide/cross-region-inference.html) to seamlessly manage unplanned traffic bursts by utilizing compute across different AWS Regions. @@ -136 +203 @@ This section provides detailed information about the common errors you might enc - * If you have high throughput requirements, we suggest exploring [Provisioned Throughput](https://docs.aws.amazon.com/bedrock/latest/userguide/prov-throughput.html) for your use case + * If you have high throughput requirements, we suggest exploring [Provisioned Throughput](https://docs.aws.amazon.com/bedrock/latest/userguide/prov-throughput.html) for your use case. @@ -143 +210 @@ This section provides detailed information about the common errors you might enc - * Ensure your application can handle 503 status codes appropriately in your error handling and retry logic + * Ensure your application can handle 503 status codes appropriately in your error handling and retry logic. @@ -150 +217 @@ This section provides detailed information about the common errors you might enc -If you experience frequent 503 errors or if they significantly impact your operations, please contact [AWS Support](https://aws.amazon.com/support)for further assistance and guidance tailored to your specific use case +If you experience frequent 503 errors or if they significantly impact your operations, please contact [AWS Support](https://aws.amazon.com/support)for further assistance and guidance tailored to your specific use case. @@ -156 +223 @@ If you experience frequent 503 errors or if they significantly impact your opera -**Cause:** The request was denied due to exceeding the account quotas for Amazon Bedrock. 429 errors can be specifically due to Token Burndowns. +**Cause:** The request was denied due to exceeding the account quotas for Amazon Bedrock. @@ -160 +227 @@ If you experience frequent 503 errors or if they significantly impact your opera - * Check the Amazon Bedrock service quotas in the [Amazon Bedrock service quotas](https://docs.aws.amazon.com/general/latest/gr/bedrock.html#limits_bedrock) console to learn about the limits allotted to your account + * Check the Amazon Bedrock service quotas in the [Amazon Bedrock service quotas](https://docs.aws.amazon.com/general/latest/gr/bedrock.html#limits_bedrock) console to learn about the limits allotted to your account. @@ -162 +229 @@ If you experience frequent 503 errors or if they significantly impact your opera - * We suggest employing AWS recommended approach of using [retries with exponential backoff](https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/retry-backoff.html) and random [jitter](https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/) for improved reliability + * We suggest employing AWS recommended approach of using [retries with exponential backoff.](https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/retry-backoff.html) and random [jitter](https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/) for improved reliability. @@ -164 +231 @@ If you experience frequent 503 errors or if they significantly impact your opera - * If you have high throughput requirements, we suggest exploring [Provisioned Throughput](https://docs.aws.amazon.com/bedrock/latest/userguide/prov-throughput.html) for your use case + * If you have high throughput requirements, we suggest exploring [Provisioned Throughput](https://docs.aws.amazon.com/bedrock/latest/userguide/prov-throughput.html) for your use case. @@ -166 +233 @@ If you experience frequent 503 errors or if they significantly impact your opera - * Request for quota increase by contacting your account manager or [AWS Support](https://aws.amazon.com/support) if your workload traffic exceeds your account quotas + * Request for quota increase by contacting your account manager or [AWS Support](https://aws.amazon.com/support) if your workload traffic exceeds your account quotas. @@ -179 +246 @@ If you experience frequent 503 errors or if they significantly impact your opera - * Review the API documentation to ensure all required parameters are included and formatted correctly + * Review the API documentation to ensure all required parameters are included and formatted correctly. @@ -181 +248 @@ If you experience frequent 503 errors or if they significantly impact your opera - * Check that your input values are within the allowed ranges or conform to the expected patterns + * Check that your input values are within the allowed ranges or conform to the expected patterns. @@ -183 +250 @@ If you experience frequent 503 errors or if they significantly impact your opera - * We suggest paying attention to any specific validation rules mentioned in the API reference for the action you are using + * We suggest paying attention to any specific validation rules mentioned in the API reference for the action you are using. @@ -192 +259 @@ If you experience frequent 503 errors or if they significantly impact your opera -**Cause:** The requested resource could not be found +**Cause:** The requested resource could not be found. @@ -196 +263 @@ If you experience frequent 503 errors or if they significantly impact your opera - * Verify the correctness of model ID, endpoint name, or other resource identifiers in your request + * Verify the correctness of model ID, endpoint name, or other resource identifiers in your request. @@ -198 +265 @@ If you experience frequent 503 errors or if they significantly impact your opera - * Please implement a fallback mechanism to use alternative models or endpoints when a primary resource is not found + * Please implement a fallback mechanism to use alternative models or endpoints when a primary resource is not found. @@ -205 +272 @@ If you experience frequent 503 errors or if they significantly impact your opera - * Use [ListFoundationModels](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_ListFoundationModels.html) to learn about the available Amazon Bedrock foundation models that you can use + * Use [ListFoundationModels](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_ListFoundationModels.html) to learn about the available Amazon Bedrock foundation models that you can use. @@ -207 +274 @@ If you experience frequent 503 errors or if they significantly impact your opera - * We suggest implementing a periodic synchronization process to update your local resource catalog + * We suggest implementing a periodic synchronization process to update your local resource catalog. @@ -212 +279 @@ If you experience frequent 503 errors or if they significantly impact your opera -If you continue to experience issues after trying these solutions, contact [AWS Support](https://aws.amazon.com/support)for further assistance and guidance tailored to your specific use case +If you continue to experience issues after trying these solutions, contact [AWS Support](https://aws.amazon.com/support)for further assistance and guidance tailored to your specific use case.