aws-amplify / aws-amplify/amplify-hosting
VPC Access for Amplify Static Applications
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
Research direction
Start by reviewing how Amplify Hosting static applications are deployed and how the reported ECS/EC2 microservices are isolated inside a VPC. Reproduce the Cypress test flow that sends an HTTP request to the auth microservice and confirm the timeout. Done means a documented or implemented way for Amplify applications to reach the intended VPC services in development environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, cypress
- Domain
- cloud, networking, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100