We are in the process of moving all of our QuotaGuard Support Documentation to 


https://quotaguard.github.io/qg-docs/


 Please Update Your Support Bookmarks


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.


Inbound Proxies are available on Micro plans and above. 


Warning : This should NOT be used as a replacement for a DNS entry resolving a custom domain for Heroku app. To access your Heroku app from a custom domain, please read the Heroku Custom Domains page.


Getting Started

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.

 

Custom domains


You can also map the domain that you own to the existing inbound proxy. To map custom domain click on "Add Custom Domain" and enter the domain name and optionally upload SSL certificate. 

For specific directions, please visit How to Add a Custom Domain. 


At the last step you will see details about necessary DNS record changes for the custom domain.

 

SSL setup

Our self-service automated setup on QuotaGuard Static supports SSL by default. 


For custom domains, you have to upload a 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 the certificate chain in PEM bundle format.

If you have questions, or if this solution doesn’t work or fit your use case, please reach out to us at Support so we can help figure it out with you.


Working with sensitive data, like HIPAA, Financial, or Personally Identifiable Information (PII)? 
    Then you will want to check out our QuotaGuard Shield solution, it's the same as QuotaGuard Static, but with stronger end to end security for your requests. We can also help migrate current Static customers to Shield for free, just reach out to us at Support to request assistance.