The Fly Runtime Environment
When a Fly application is running, various information about the runtime environment is made available to it.
Environment variables carry information that is generally applicable to the instance. The environment variables will also include any secrets that have been set for the application.
Request headers carry information that is specific to the incoming request and its path taken to the application. Request headers are added by the HTTP handler service.
Allocation ID: Each instance of an application running on Fly has a unique Allocation ID. This can be used, for example, to distinguish between instances running in the same region.
b996131a-5bae-215b-d0f1-2d75d1a8812b is an example of the Allocation ID's format.
IPv6 Address for Future Access: In the future, it will be possible to address instances directly using this IP address. Currently, the address will reject all attempts to open a connection to it. Contact firstname.lastname@example.org if this feature is of interest.
URL for the Redis Cache: Each application has access to a region local Redis cache. This is the URL, complete with key, that can be used to access it with any standard Redis driver. For more on Redis see the Redis page. An example of a typical Redis URL would be
Region name: The three letter name of the region the application instance is running in. Details of current regions are listed in the Regions page. As an example, "ams" is the region name for Amsterdam.
Client IP Address: The IP address Fly accepted a connection from. This will be the client making the initial request and as such, will also appear at the start of the
Original connection port: This header is always set by Fly and denotes the actual port that the client connected to the Fly edge node which is then forwarded to the application instance.
Edge Node Region: This header is a three letter region code which represents the region that the connection was accepted in and routed from. Not to be confused with the environment variable
FLY_REGION which is where the application is running.
Client and Proxy List: This is a comma separated list comprising of the client that originated the request and the proxy servers the request passed through. For example, "22.214.171.124, 126.96.36.199" contains the client and the one proxy it passed through.
MDN has full documentation for this header.
Original client protocol: The protocol which the client used to make the request. Either
Original connection port: This header may be set by client and should denote the port that the client set out to connect to.
SSL Status: This indicates if client connected over SSL. Its value can be either
Proxy Route: This header, added by proxies, shows the path taken, and protocols used, by the connection. MDN has full documentation for this header. For example, a connection through the Fly edge may show
2 fly.io in the field, denoting that version 2 of HTTP was used by the connection as it passed through the fly.io proxy.