This region is feature-complete with other regions and available to everyone. The early access period provides us an opportunity to address any one-off issues that might arise with spinning up a new region.

We'll leave this item's status as In Progress until the early access period completes.

If you enable this I would certainly start the process of migrating from Heroku in earnest. It would make the transition much easier.

I understood from Render support that AWS would currently apply transfer costs even if Render server region was the same as your AWS region, due to Render not having "Peering" between AWS and Render VPCs. They suggested that I upvote this topic if we want them to implement this to remove the transfer costs when in the same region: https://feedback.render.com/features/p/aws-vpc

+1 more!

This is the only feature that is holding us back from completing a migration from Heroku. We have an AWS RDS database hosted in so being able to deploy our app in the same region is critical.

As discussed here: https://community.render.com/t/having-aws-s3-in-a-region-different-from-deployment/5578 I would also prefer having the region available, since without it, I'll have to copy all my data buckets to the new region to avoid AWS inter-region I/O costs.

Anurag Goel, just want to +1 your thesis. Not having us-east-1 on render is actively preventing us from migrating services to render (from Heroku). We're assessing other non-render options because of this.

Would love to have this option. All my services are currently in Virginia and NYC except for Render. Would love to deploy to us-east-1 in-order to speed up my services 🙏