Why Use an Inbound Proxy?
Cloud deployment environments such as Heroku, IBM Cloud, Microsoft Azure, and Pivotal Web Services allow you to horizontally scale your web application by creating multiple instances running on different servers and load balancing requests between them. This is a problem if you need to access your web application via a specific IP address, for example if your corporate firewall can only allow traffic through to known IP addresses, as the IP address of your application may change at any time.
With our Inbound Proxy you just define what URL you want traffic forwarded to and we give you a unique domain linked to a static IP address that forwards all traffic to your web application.
When not to use an Inbound Proxy
Don't use it as a way to create a DNS A record resolving to your own domain
Once you have created a QuotaGuard Static account you just need to enter in the base URL of your web application.
We then create for you a unique URL that you can use to access your web application: e.g. a62b1d0b4983db763450411fd393b3ce-eu-west-1.getstatica.com
This corresponds to a DNS A name record that resolves to two QuotaGuard Static IPs. You should include both IP addresses in any firewall rules or whitelists as we may swap between IP addresses at any time.
Open this URL in your browser and you should see your own web application.
In your firewall you can now just open access to the two QuotaGuard Static IPs in order to work with your cloud app.
You can also map domain that you own to the existing inbound proxy. To map custom domain click on "Add Custom Domain" and enter domain name and optionally upload SSL certificate. At the last step you will see details about necessary DNS record changes for the custom domain.