Title: Implementing Path-Level Routing for Domain Redirect to AWS EC2 Instance
Body:
I am encountering an issue with path-level routing during a domain redirection process and would appreciate guidance on potential solutions. Context: Primary Domain: www.dummyexample.us Developed using Google Sites. Hosted on Google's servers. Secondary Web Application: Backend: Spring Boot. Frontend: Angular. Hosted on an AWS EC2 instance.
Issue:
When users click the "Login" button on www.dummyexample.us, they are redirected to the secondary web application hosted on the AWS EC2 instance. Post-redirection, the URL displayed in the browser is that of the EC2 instance (e.g., ec2-xx-xx-xx-xx.compute-1.amazonaws.com). My objective is to retain the primary domain in the URL post-redirection, aiming for something like www.dummyexample.us/login.
Attempted Solutions:
Modified DNS records in Google Domains for www.dummyexample.us. Adjusted the DNS records in AWS Route 53. Unfortunately, neither approach yielded the desired outcome.
Constraints:
Utilizing a reverse proxy is not feasible as I lack access to the configuration file of the web server where www.dummyexample.us is hosted.
Request:
Could anyone suggest alternative methods or strategies to achieve this URL path-level routing? Any insights or recommendations would be greatly appreciated.