Establishing and using a tunnel from an origin server in a distributed edge compute and routing service

A non-transitory machine-readable storage medium that provides instructions that, when executed by a processor, cause said processor to perform operations comprising:

• receiving, at a first one of a plurality of edge servers of a distributed edge compute and routing service from a first tunnel client residing on a first origin server, a first tunnel connection request that requests a first tunnel be established between the first one of the plurality of edge servers and the first tunnel client, wherein the first tunnel connection request identifies a hostname that is to be tunneled;
• assigning a first IP address for the first tunnel;
• causing a Domain Name System (DNS) record to be added or changed that associates the hostname with the assigned first IP address for the first tunnel;
• causing routing rules to be installed in the plurality of edge servers to reach the first one of the plurality of edge servers for the tunneled hostname;
• receiving, at the first one of the plurality of edge servers, a request for an action to be performed on a resource of the tunneled hostname handled by the first origin server, wherein the first one of the plurality of edge servers receives the request from a second one of the plurality of edge servers that received the request from a client network application, and wherein the second one of the plurality of edge servers is not connected to the first origin server for the tunneled hostname;
• and
• transmitting the request from the first one of the plurality of edge servers to the first origin server over the first tunnel.

An apparatus, comprising:

• a set of one or more processors;
• a non-transitory machine-readable storage medium that stores instructions that, when executed by the set of processors, is to perform operations including:
• receive, at a first one of a plurality of edge servers of a distributed edge compute and routing service from a first tunnel client residing on a first origin server, a first tunnel connection request that requests a first tunnel be established between the first one of the plurality of edge servers and the first tunnel client, wherein the first tunnel connection request is to identify a hostname that is to be tunneled;
• assign a first IP address for the first tunnel;
• cause a Domain Name System (DNS) record to be added or changed that associates the hostname with the assigned first IP address for the first tunnel;
• cause routing rules to be installed in the plurality of edge servers to reach the first one of the plurality of edge servers for the tunneled hostname;
• receive, at the first one of the plurality of edge servers, a request for an action to be performed on a resource of the tunneled hostname handled by the first origin server, wherein the first one of the plurality of edge servers is to receive the request from a second one of the plurality of edge servers that received the request from a client network application, and wherein the second one of the plurality of edge servers is not to be connected to the first origin server for the tunneled hostname;
• and
• transmit the request from the first one of the plurality of edge servers to the first origin server over the first tunnel.