As of version 1.9 Tyk no longer requires NginX and the Tyk Host Manager to work However, the Tyk host manager is still bundled with Tyk Dashboard and Tyk will continue to work with the host manager, but requires manual installation and configuration.
An example configuration is shown below:
The only difference to a standard NGinX setup is the upstream
tyk section, here we enumerate a list of running Tyk
instances, Tyk can be started on a different port by simply using the
You can then use the
sites-enabled folder to set up your API / Gateway server:
The above configuration will accept requests to
gateway.myserver.com, then rewrite any of the requests coming in to
listen_path set up for this specific api in it’s API Definition, and forward the request upstream to your load-balanced
This should ensure that you can present a clean API front-end to your users, without having to worry about API ID’s, listen paths or
ugly gateway URL’s, if you wanted to, you could plumb Tyk into your existing architecture without changing your current endpoints
(assuming you are using NGinX, of course).