It looks like the spend limits can't be applied to existing AWS Accounts but only to new Projects, that there is no migration path from AWS Account -> Project, that you can only have 10 projects with Spend Limits, and that Projects can't use any region other than one of three regions determined by your organizational contact address. Is the plan to get rid of these limitations or should we expect these limitations to stay?
My use case is that our company would like to empower our AI agents to do a lot of stuff autonomously that involves reprogramming and spinning up EC2 instances (which, for reasons of latency, often need to be in particular regions other than our company's home address), and also doing data science on large amounts of existing data in our S3 Glacier. We would like to just let the agents run continuously, including when we are all asleep (and there would be no one around to respond to a budget alert). But we are worried that these AI agents might make a mistake that very quickly spends too much money (e.g. spinning up orders of magnitude more instances than they should). Since the agents are autonomous, they might spend money in a way we haven't thought of, so fine-grained budget-based automation wouldn't always work, and account-level spend controls are needed.