Static IPs, whitelisting

Right now I’m using firewall rules on my AWS RDS db and external Redis db to only allow incoming connections from my droplets. Switching to the App Platform, how can this be handled? Since there doesn’t seem to be an option to assign a static IP (or a set of IPs) to the containers that are spun up, I would have to update the list of allowed IPs each time in an after deploy job I guess? Is that the recommended approach? If so, how can I access the container’s IP in the job? I don’t see a env var for this…

Show comments

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Accepted Answer

App Platform apps do not have a static-IPs. We’ve heard requests for static IPs as an add-on feature and are considering it. In the mean time, we recommend using TLS encryption and strong authentication to secure connections to external resources.

Facing the same issue. I need to redirect the non-www to www domain using the App platform of digital ocean. I had to migrate because of this reason of static Ip’s. Can DO team share when it will be published for end-users?

Please add this feature DO. I’m working with a client that has simplistic needs, but on a registrar that doesn’t support CNAME flattening. They won’t move, and the convenience of auto-deployment from a main branch in GitHub is -exactly- what I need.

Configuring the same functionality myself on a VPS doesn’t make sense with the size of project, but I would pay for an upgraded App instance forever just for the IP.

If you feel strong about this, please go vote for this feature here: