Prevent CF Deployment Template from spinning up container in unsupported region

I launched an instance and spent the better part of the day troubleshooting just to find out that Cloudflare spun up the container instance in Hong Kong which is blocked by Anthropic.

Ideally the deployment would be smart enough to avoid this pitfall, does { "placement": { "region":"aws-us-east-1" } } in this situation?