Question
Reverse Proxy from Droplet to App Platform
- Posted on September 10, 2021
- NginxDigitalOcean Droplets
Asked by thecertnginx
Hello,
In my project I have a constraint where I have to whitelist some IP for a reverse proxy to a specific url /system However I wanted to have the root path be on the App Platform so I can make use of Zero Downtime Deploys and CD, high availability etc. So on the droplet I made a reverse proxy from nginx to the URL generated from the App platform. Everything is working fine, but still I wanted to ask if this is something I could do? Can this have drawbacks in the future? I realise that I will be billed based on the bandwidth on the app platform and not the droplet and that is ok.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Get our newsletter
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Hi there,
Quick update here, you can now add dedicated egress IP addresses to your apps on App Platform. Dedicated egress IP addresses allow your app to connect to resources outside of DigitalOcean using a publicly available static IP address.
Dedicated egress IP addresses are a paid feature that allows your app to connect to resources outside of DigitalOcean using a static IP address and allow you to restrict external resources to receive only outgoing traffic from your app. Dedicated egress IP addresses persist through redeployments but are removed from the app if you disable the feature or the app is destroyed.
You can add a dedicated egress IPs to your app after you deploy the app. To do so, in the DigitalOcean Control Panel, go to the Apps page and click your app. Click the Settings tab, scroll to the Dedicated Egress IP Addresses section, and then click the Edit button beside the section.
In the Edit menu, click the Add Dedicated Egress IP button. This assigns two IP addresses to your app and triggers a redeployment.
To remove a dedicated egress IP address, in the same Edit menu, click Release Dedicated Egress IPs. This removes the IP addresses from the app and triggers a redeployment. Once IP addresses have been released, the same addresses cannot be re-added to the app.
Hope that this helps!
Best,
Bobby
👋 @thecertnginx
Seems reasonable to me. Dedicated egress IPs are something that we have on the roadmap though it’s a ton of work and will take some time.
As for downsides, I guess there may be a tiny bit of added latency. The biggest drawback will be maintaining that Nginx proxy.
Hope this helps!