- Newest
- Most votes
- Most comments
Based on the information available, you should be able to purchase no-commitment Provisioned Throughput for your custom Amazon Titan Text Express model. Multiple sources confirm that the "No commitment" option is available for custom models in Amazon Bedrock, including fine-tuned models like yours.
Here's how to purchase no-commitment Provisioned Throughput for your custom model:
- On the Amazon Bedrock console, navigate to "Custom models" in the navigation pane
- Select your custom model and choose "Purchase provisioned throughput"
- Enter a name for your Provisioned Throughput
- Ensure the correct custom model is selected
- Under "Commitment term & model units", select "No commitment" and set 1 model unit (or the amount you need)
- Review the estimated cost and confirm the purchase
Alternatively, you can use the AWS CLI with this command:
aws bedrock create-provisioned-model-throughput \
--model-id [Your-Custom-Model-ARN] \
--provisioned-model-name [Your-Provisioned-Model-Name] \
--model-units 1
After purchasing, allow some time for the Provisioned Throughput to be created. You can check its status using:
aws bedrock get-provisioned-model-throughput \
--provisioned-model-id [provisioned-model-arn]
When the status shows "InService", you can run inference with your custom model.
The error you're encountering is unexpected since the documentation specifically mentions that a flexible "No commitment" option is available for custom models. If you continue to experience this issue, you might want to contact AWS Support to help troubleshoot the specific error you're encountering.
Sources
Code samples for model customization - Amazon Bedrock
Fine-tune and deploy language models with Amazon SageMaker Canvas and Amazon Bedrock | AWS Machine Learning Blog
Fine-tune LLMs with synthetic data for context-based Q&A using Amazon Bedrock | AWS Machine Learning Blog
Security best practices to consider while fine-tuning models in Amazon Bedrock | AWS Machine Learning Blog
answered a year ago
Relevant content
asked 3 years ago
asked 3 years ago
asked 2 years ago

I tried the Agent's suggestion from the console and from aws cli. I still see the same error.