# SPIKE on infrastructure

moved to https://github.com/Holo-Host/infrastructure/blob/master/amazon/kong-zato/README.md

# Kong / Zato Infrastructure

These are the goals as per the date of the commit for this change.

## Kong

* Dockerize kong using https://hub.docker.com/_/kong
* nixos on docker server
* separate VM for Kong DB (nixos with hydra)
* script the updating of kong (turn off server, snapshot db, deploy container, import config)
* create automated DB backup for kong
* envars for config
* terraform to capture architecture state

## Zato

* Dockerize the zato server cluster
* nixos on docker server
* vm instance for redis (nixos with hydra)
* vm instance for postgresql (nixos with hydra)
* vm instance haproxy (nixos)
* Zato instance has to communicate with its other required pieces
* terraform to capture architecture state

## Both

* setup communication from Zato to Kong as per Sam's article/diagram (private aws networks).