21
US East (Virginia) Region
Anurag Goel
Render's Ohio region is already in early access. For customers moving over from Heroku and AWS, a Virginia region will help with the transition.
Log In
d
dataslug1
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
C
Chris Grigg
+1 more!
h
hamed
This is the only feature that is holding us back from completing a migration from Heroku. We have an AWS RDS database hosted in
us-east-1
so being able to deploy our app in the same region is critical.C
Cédric Foellmi
As discussed here: https://community.render.com/t/having-aws-s3-in-a-region-different-from-deployment/5578 I would also prefer having the
us-east-1
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.B
Ben Schwarz
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.
D
Dawson Botsford
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 🙏