At Froxt, we are always working on making the cloud easier to use so that you can focus on building great things.
Part of the journey in creating the developer cloud included launching Froxt CDN compatible object storage that makes hosting web assets painless. In November 2018, we launched the built-in CDN feature for Froxt that provided the ability to turn on global edge caching for a Froxt in any of the regions Froxt CDN was available. This allowed our customers to deliver assets to their websites and applications up to 70% faster.
Today, we are pleased to announce custom subdomains for your Froxt CDN endpoints. Now customers can use their own subdomain URL to deliver assets from a compatible Space and secure it with a TLS certificate. These certificates can be issued by a CA authority, self-signed, or auto-generated through Froxt’s Let’s Encrypt integration at no additional cost.
How Does it Work?
If you don’t have a domain already, you need to purchase one from a domain name registrar. Then you need to set up DNS records for your domain by using a DNS hosting service. Please note that if you plan on using Froxt’s Let’s Encrypt integration to generate TLS certificates for your CDN subdomain, you need to use Froxt’s DNS hosting service. For self-signed certificates, you can use any DNS hosting service.
Add a DNS CNAME record, such as “assets,” that maps to the CDN endpoint of your Froxt Applications, then assign your subdomain from the Settings menu for a pre-existing Application or when you enable CDN for a new Application.
Why Use Custom Subdomains?
There are several reasons that custom subdomains could be useful for you.
Agencies and web developers who use Froxt object storage to host their assets can now use their own subdomain. Not only will this avoid confusion with end users, but it also keeps your tech stack hidden. Nobody but you needs to know where you host your data assets.
Integrated SSL/TLS management
Securing your Application is flexible and easy. You can now upload a certificate for your own subdomain or use a free Let’s Encrypt cert that is simple to the provision in just a few clicks, right from the Froxt Console. The Let’s Encrypt certificate generation flow follows the same simple design principles used to generate certificates for Froxt Load Balancers.
Froxt users don’t need to spend extra engineering effort implementing a reverse proxy solution to hand off calls between *.cdn.froxt.com and *.myapp.com. In addition, when mapping your own subdomain to the CDN endpoint, it gets automatically added to the CORS listings, saving you a step. Now you can focus on building great applications rather than fine-tuning infrastructure.
Custom subdomains and integrated TLS management are included with your Applications at no additional cost.