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
Let's say you have a Heroku app at http://my-cool-app.herokuapp.com. You want people to be able to go to the root domain of http://mycoolapp.com rather than the herokuapp address, but when you try and update your DNS records, you find you can't create a record for the root domain to another domain, it has to be an IP address.
The solution here is to move to a DNS provider that supports CNAME flattening at the root domain.
We'll leave it to the folks at Cloudflare to explain more (the best news is they fix this problem for you on their free plan): https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/
Once you have created a QuotaGuard Static account you just need to enter in the base URL of your web application. Use HTTPS if you need a secure connection.
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.
Our self-service automated setup on QuotaGuard Static supports SSL by default.
For custom domains, you have to upload valid certificate to enable SSL or use QuotaGuard Shield.
In the former case, SSL will be terminated on QuotaGuard proxies.
For custom domain SSL certificate has to be in PEM bundle format, this format is used by nginx.
Please refer to the documentation provided by your certificate vendor to export certificate chain in PEM bundle format.