Skip to content
This repository was archived by the owner on Nov 9, 2022. It is now read-only.

Using Roxy Deployer with Amazon

Jump to bottom
Geert edited this page Jun 13, 2017 · 2 revisions

If you're running MarkLogic on Amazon's EC2, and you have direct access to the host, things ought to Just Work. However, if you're using an elastic load balancer, you may see an error with deploy commands returning an error off of the elastic load balancer as a bad request.

Using Batch commit: true
loading: /Users/poneill/Desktop/healthforum/trunk/schemas/instance1.xml => /instance1.xml
[PUT]      http://address.us-east-1.elb.amazonaws.com:8041/insert?uri=%2Finstance1.xml&perm=Eapp-user&perm=Rapp-user&tzoffset=-21600&dbname=hf-schemas&nocommit
ERROR: 400 "BAD_REQUEST"
ERROR:

If that happens, make sure the port is open to TCP traffic instead of HTTP. If one of the later error messages asks whether the port is an XCC server, that's likely to be the issue.

In addition you could receive 504 Gateway timeout messages. In that case consider using deploy modules --batch=false or deploy modules --incremental=yes.

Clone this wiki locally