Live data from Hacker News

Show HN: An API to provision custom hostnames with SSL

news.ycombinator.com

21–30 of 38 posts

Re: Show HN: An API to provision custom hostnames with SSL

#21
post #16
post #12

Earlier quoted context omitted.

Send me an email and I'll help (kurt@fly.io, or support@fly.io)! We've been working on improving the onboarding flow for new apps, but it's definitely complicated. Elastic Beanstalk and EC2 will work fine, and we can help you get setup. You can either run through ELB (if you already have that setup) or use our agent and let us handle all the load balancing: https://fly.io/docs/agents/ It should be obvious when and wh…

You don't need AWS keys at all. This enrollment flow flies in the face of best practices. Intead, you should be providing your users with instructions to create an IAM role for cross-account utilization. Ideally in addition to the instructions, you'd provide a minimal CloudFormation template defining such a role, with your minimum required permissions. Asking a customer to create a user and ship you a secret is askin…

DING DING DING

The problem is that a junior level of exposure may result in access+secrets being mistakenly given out.

Yeah - they should be looking into say, cloudability, or any number of thousands of offerings ding just this.

Re: Show HN: An API to provision custom hostnames with SSL

#22
post #11
post #9

Can you help me understand how this is different than Cloudflare's offering [1]? 1- https://www.cloudflare.com/lp/sector/saas/

It's superficially similar. The most obvious difference is that you need a CloudFlare Enterprise plan to do that stuff, and we have a free tier + easy metered pricing. You can probably do a complete Fly implementation in the time it takes to setup a call with one of their sales folks.

howto vid link?

Re: Show HN: An API to provision custom hostnames with SSL

#24
I found the same problem also exists for the end users who are sometimes using apps that don't support custom hostnames but they still want a brandable domain for it.

So I recently made https://www.ManagedAlias.com/ as an experiment to see if there is demand.

I avoided the bulk/business route because you essentially have to be a CDN to pull that off (since you are doing the TLS termination).

This is just geared towards non-technical people who need a pretty name for a site without fuss and they don't want to mess with anything technical.

Re: Show HN: An API to provision custom hostnames with SSL

#28
post #3
post #2

I'm not sure how this is easier than a wildcard certificate and a wildcard CNAME...

It's not, it's meant for cases where people need entirely different custom hostnames. Subdomains are quick and easy, but people have become quite a bit more demanding about how their stuff is branded, and tend to want it all on mydomain.com (instead of me.service.com). Actually I lied, it's probably a little easier than a wildcard cert. :D But not enough to matter. People who just need wildcard subdomains might want…

Actually when Let's Encrypt will provide free wildcard in early 2018 the later will be much more easier !

Re: Show HN: An API to provision custom hostnames with SSL

#29
> If you use Netlify and want to use Fly to broaden your application scope, perhaps hosting Netlify as your marketing site on your root domain, then something like a Heroku application at /app/, then you've come to the right place.

Oh this is cool, you've got me intrigued there.

> Google Auth -- ... Do you want to gate off a static page so that only your Google Org may see it? We make it easy!

So does it integrate with G Suite?

Post reply on HN