Imported Google Group message.
Date:Friday, 15 May 2015 10:11:43 UTC+1.
The quickstart really isn't appropriate for an EC2 instance deployment, it configures things quite specifically for a local set up (hence the host file changes).
I would suggest you get docker installed on your local machine (if you are running OSX then get yourself Kitematic - just make sure you modify your hosts file appropriately)
To get set up on an EC2 instance you will need ot set up a domain, ideally a wildcard for subdomains and point it at your ec2 instance, you'd then need to change the templates in the tyk_nginx docker to use your new domain, and then it might work. I'd strongly suggest getting things up and running locally so you can get familiar with the system and how it's structured before attempting a deployment.
The authorisation error is absolutely nothing to worry about because that is the tyk gateway responding to what it thinks is an upstream API request and is blocking it, because your routing is misconfigured it is:
- Sending requests to the gateway
- The gatewway can;t identify the API ID it is meant to route to and so errors
- It reports an empty key because the whole request is invalid
This is untested, and a longhot, but you could try this:
Get a domain and assign the wildcard subdomain to point at your ec2 instance.
In th quickstart.sh, modify this line:
echo "Setting up NginX and Host Manager"
docker run -d --name tyk_nginx -p 8888:80 --link tyk_gateway:tyk_gateway --link tyk_dashboard:tyk_dashboard --link tyk_mongo:tyk_mongo --link tyk_redis:tyk_redis -e DOMAINALIAS=tyk.docker tykio/tyk-host-manager
And replace DOMAINALIAS=tyk.docker with DOMAINALIAS=YOUR_DOMAIN_NAME
(You could also just kill the tyk_nginx container (docker stop tyk_nginx && docker rm tyk_nginx) and run the above command manually, what it will do is set the environment variable DOMAINALIAS to the doain of your EC2 instance, when the host manager container starts up, it fixes the nginx templates to use your new domain name.
- show quoted text -