Open DanielNetzeriAm opened 4 years ago
+1
+1
Please add this feature
+1
+10000000
Guys any updates on this ?
+1
Commenting to keep the thread alive
For over 3 years, I've been puzzled by the AWS Amplify team's inability to address the private RDS connection issue for Next.js code operating outside the VPC.
Curious to know why it's taking so much time to add that feature :-)
+1 On This. Seems the only way to make it viable for production apps or need to use Vercel?
+1 On This. Seems the only way to make it viable for production apps or need to use Vercel?
I recommend going for https://sst.dev @sst
Commenting to keep the thread alive
+1 on this.
+1
Commenting to keep the thread alive
also facing the issue of having to expose the RDS to the public in order to operate from a Nextjs app in Amplify
Any updates on this open feature?
Commenting to keep the thread alive
+1
+1
+1
Are there any news on this feature?
@nadetastic i see u added deploy tag a year back, does that hold any significance ?
+1
+1
any updates?
Cfbr
??? Any updates on this issue?
Any updates
Any updates
Come on, at least give an update on all people that is interested on this topic
I think this blocks any Amplify app from satisfying SOC2 compliance rules?
+1
+1
Please fix this
We are using ECS to deploy ec2 instances as backend api's/microservices, all of those are inside a VPC in our QA and DEV account.
When we try to run Cypress unit tests the application makes http requests to those microservices resulting in timeout as the applications isn't part of the VPC.
a scenario for example: App Startup -> User Unauthorized -> Send Http Request to Auth Microservice -> Timeout. Tests fail.
Would be happy if there's a way to add Amplify applications into a VPC in general so we can control the access on the development environments.