1 Answer
- Newest
- Most votes
- Most comments
0
Hi hrrstuart,
The price shown for provisioned throughput with a 1-month commitment is calculated as if the resource is running 24/7. With a 1-month commitment, you're essentially reserving that throughput capacity for the entire month, meaning you’re billed for the full duration, regardless of actual usage. Unfortunately, you cannot toggle it on/off to reduce costs during periods of inactivity; the commitment ensures that capacity is always available when you need it, but it also means you're paying for it continuously, even if you're not using it.
I'm here to help.
Relevant content
- asked a year ago
- asked 2 years ago

Hi thank you for the response, I was reading and did discover that the no commitment option would be the equivalent of the situation I'm talking about, right? Like you'd be billed for your actual usage? And this is a viable option if I fine-tune my own model using Amazon Bedrock? (i.e. if I fine-tuned a llama model it says you'd have to purchase provisioned throughput but if I just purchase the no-commitment it should be $0 until I start using it)
Yes, you’re correct that a no-commitment option would allow you to be billed only for your actual usage, making it suitable if you only need the model intermittently. When fine-tuning models like Llama on Amazon Bedrock, provisioned throughput is required during the customization process.
For more details, I recommend reading this AWS blog post.