5 ms·

> Mapping X subdomain to Y port on Z machine should take a couple clicks from a web interface. route53 can work like that, it also has a cli version. (But you

> Mapping X subdomain to Y port on Z machine should take a couple clicks from a web interface. route53 can work like that, it also has a cli version. (But you can't get the domain there).

anderspitman 6y ago
Can it tunnel to local devices like a RPi or just AWS VMs?
- Aperocky 6y ago
  You have to own the IP, and map the RPi to the standard ports (80/443, likely have to set that up from router). Alternatively just do x.com:yyyy if you don't mind (though you probably do for an external facing website).
- duskwuff 6y ago
  No, it's just DNS. It doesn't provide any additional routing.
an_opabinia 6y ago
> (But you can't get the domain there) There's Amazon Domains now. Additionally, https://github.com/crazy-max/ddns-route53 https://github.com/crazy-max/ddns-route53 works well as a dynamic DNS configurator for Route 53. For most home users, a Docker-supporting server is the best option. Traefik has ACME and labels-based configuration for Docker hosts. It is a good choice for multiplexing HTTPS services by subdomain names. In my opinion the biggest limitation is that there is no universal API for network routing appliances, whether it is your $30 home combo WiFi/router or your $20,000 Cisco device. An access-key-authorized version of UPnP would be sufficient for the vast majority of users. Or even iptables commands over public key authenticated SSH. But giant corporations - Google, Microsoft, Apple, Amazon, Facebook - they are in the cloud business, Microsoft doesn't ship a home server technology really anymore. The most popular home server software, like Plex, is really purposefully disruptive to giant software and media companies. By contrast you're going to have a bad time running your own Dropbox competitor from home, because that sort of technology is engineered around cloud computing.

5 ms·

> Mapping X subdomain to Y port on Z machine should take a couple clicks from a web interface. route53 can work like that, it also has a cli version. (But you

by Aperocky 6y ago

> Mapping X subdomain to Y port on Z machine should take a couple clicks from a web interface. route53 can work like that, it also has a cli version. (But you can't get the domain there).

anderspitman 6y ago
Can it tunnel to local devices like a RPi or just AWS VMs?
- Aperocky 6y ago
  You have to own the IP, and map the RPi to the standard ports (80/443, likely have to set that up from router). Alternatively just do x.com:yyyy if you don't mind (though you probably do for an external facing website).
- duskwuff 6y ago
  No, it's just DNS. It doesn't provide any additional routing.
an_opabinia 6y ago
> (But you can't get the domain there) There's Amazon Domains now. Additionally, https://github.com/crazy-max/ddns-route53 https://github.com/crazy-max/ddns-route53 works well as a dynamic DNS configurator for Route 53. For most home users, a Docker-supporting server is the best option. Traefik has ACME and labels-based configuration for Docker hosts. It is a good choice for multiplexing HTTPS services by subdomain names. In my opinion the biggest limitation is that there is no universal API for network routing appliances, whether it is your $30 home combo WiFi/router or your $20,000 Cisco device. An access-key-authorized version of UPnP would be sufficient for the vast majority of users. Or even iptables commands over public key authenticated SSH. But giant corporations - Google, Microsoft, Apple, Amazon, Facebook - they are in the cloud business, Microsoft doesn't ship a home server technology really anymore. The most popular home server software, like Plex, is really purposefully disruptive to giant software and media companies. By contrast you're going to have a bad time running your own Dropbox competitor from home, because that sort of technology is engineered around cloud computing.