amplify-hosting
amplify-hosting copied to clipboard
aws-amplify
VPC Access for Amplify Static Applications
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.
Hi @DanielNetzeriAm,
I believe we don't support hosting in VPC at the moment. I have added it to our feature backlog.
is there an update on where this stands in terms of priority? with SPA apps testing in non-production environments becomes a challenge with not being able to deploy apps within a VPC
Hi - is there any update to this please? It would be great to use Amplify to deploy internal applications rather than just externally facing ones. Thanks :)
Is there a timeline on when this might be coming, if not is there any support guide on how we can add amplify apps to our VPC?
Any updates here? Blocks my use case of accessing Elasticsearch cluster inside my VPC --- big deal breaker
+1 on this issue. This is currently creating us issues as we necessarily need to open our RDS to the Internet in order to have our Next backend connect to it.
It's been nearly 3 years since this was added to the backlog. Is there legitimately no progress to report on it? It does seem pretty insane that the recommendation is to just open RDS or other resources to the public facing internet just to deploy a Next.js site. Please allow configurable VPC access via amplify.yml or some other configuration panel in the Amplify Console. The convenience of Amplify is not worth the security implications if it cannot communicate with my data sources hosted within AWS as well.
^ I cant open up my database to the internet thats behind a VPC with many services containing sensitive data. As it stands, it isn't worth it in the slightest. This is a dealbreaker for me; I'd love to see some progress on this
This would be ideal, if not I need to move a project off Amplify and into EC2 to access our VPC peering connection.
+1 on the above. Can we get a status update please? This is also a dealbreaker for my use-case.
+1 On all of the above. Not even just from a security standpoint, but in terms of ease of setup, all the "high level abstraction" that AWS Amplify adds is quickly negated by the fact that you have to go through extra hurdles just to be able to connect an ElastiCache instance for example.
+1
This has been three years, so is this actually on your roadmap? Amplify would be a great solution if so, otherwise this product is useless to many, especially those of us needing SOC 2 compliance since the database being open is huge gap and is not a solution for production apps.
