AWS spend limits pause a project and can delete Bedrock custom model weights

Sources: primary, discussion
Summary: The documentation describes a per-project monthly ceiling that stops resources when reached, with optional early controls acting at about seven, five and four days before the limit: a service control policy blocks new resource launches, Compute Optimizer criteria pause idle EC2, RDS and SageMaker endpoints, and top cost drivers are paused by terminating EC2 instances after snapshotting attached EBS volumes and releasing Elastic IPs, disabling Lambda event source mappings, and deleting Bedrock provisioned throughput. Deleting provisioned throughput deletes custom fine-tuned model weights, because deletion is the only way to stop those charges. The minimum limit is the greater of $20 or an AWS conservative estimate, limits apply to at most 10 projects and exclude credits, project data is permanently deleted 90 days after a pause, and the page states the new experience is releasing to a limited number of customers.
Why it matters: This is the hard cap engineers have asked AWS for, and its enforcement is destructive, so the price of reaching the limit includes terminated instances and deleted fine-tuned weights.