From a303b358e82a12b74570bfea5342c82c563b0096 Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Thu, 4 Sep 2014 21:43:04 +0100 Subject: [PATCH] s/AMZN/EC2/g --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0ecc4562..dce4c300 100644 --- a/README.md +++ b/README.md @@ -288,7 +288,7 @@ The same command will work from any application container. Weave can network containers hosted in different cloud providers / data centres. So, for example, one could run an application consisting -of containers on GCE, AMZN and a local data centres. +of containers on GCE, EC2 and a local data centres. To enable this, the network must be configured to permit TCP and UDP connections to port 6783 of the docker hosts. @@ -301,7 +301,7 @@ is able to route traffic between containers as long as there is at least one *path* of connected hosts between them. So, for example, if a docker host in a local data centre can connect -to hosts in GCE and AMZN, but the latter two cannot connect to each +to hosts in GCE and EC2, but the latter two cannot connect to each other, containers in the latter two can still communicate; weave will route the traffic via the local data centre.