Added Formatting to aws.md

docs/aws.md

@@ -1,7 +1,11 @@
 # AMP AWS Instructions
 
-The following readme is a general summary on how to access and use AMP within an AWS hosted VPC. 
-It is assumed that a swarm manager has already been provisioned and is running on AWS. 
+The following readme is a general summary on how to access and use AMP within an AWS hosted VPC.
+It is assumed that a swarm manager has already been provisioned and is running on AWS.
+
+
+----------
+
 
 ##Prerequisites
 
@@ -20,6 +24,7 @@ This port is reserved for the `amplifier` service, which is responsible for all
 These ports are reserved for HTTP and HTTPS respectively. Application services that have been deployed can be reached via HTTP through these ports. In order to route traffic to internal containers, a public DNS entry should be created in order allow access to internal containers. As an example, a service named `pinger` could be reached via `pinger.engage.amp.appcelerator.io`, assuming a DNS entry exists for the subdomain `engage.amp.appcelerator.io`
 
 
+----------
 
 
 ## Using the CLI
@@ -29,31 +34,32 @@ In order to monitor and/or manage the AMP cluster the *server* option should be
 
 Full documentation on the CLI functionality can be found [here] (https://github.com/appcelerator/amp#cli)
 
-
 
-## TROUBLESHOOTING
+----------
 
-The current version of docker that is running in the swarm is `1.12.1`. In some cases, during the development cycle, it mght be necessary to manually manage the Docker installation, on the swarm host machine. Below are some useful commands to keep handy, when the situation arises.
 
+## TROUBLESHOOTING
 
-***NOTE***: You will need to be given access to the pem file containing the private SSH Key in order to execute the following commands. For example:
-`ssh -i ~/.ssh/amp-engage [email protected]`
+### Working around docker
 
+The current version of docker that is running in the swarm is `1.12.1`. In some cases, during the development cycle, it might be necessary to manually manage the Docker installation, on the swarm host machine. Below are some useful commands to keep handy, when the situation arises.
 
-### Delete All Services
-`docker service rm $(docker service ls -q) `
 
-### Remove All  Containers
-`docker rm -f $(docker ps -aq)`
+***NOTE***: You will need to be given access to the pem file containing the private SSH Key in order to execute the following commands. For example:
+`ssh -i ~/.ssh/amp-engage [email protected]`
 
-### Remove the Docker Networks
-`docker network rm $(docker network ls -q)`
+ - Delete All Services: `docker service rm $(docker service ls -q) `
+ - Remove All  Containers: `docker rm -f $(docker ps -aq)`
+ - Remove the Docker Networks: `docker network rm $(docker network ls -q)`
+ - Restart the Docker Daemon: `sudo service docker restart`
+ - Remove Docker Volumes: `docker volume rm $(docker volume ls -q)`
 
-### Restart the Docker Daemon
 
-`sudo service docker restart`
+### AMP cli known issues
 
-### Remove Docker Volumes
+#### Adding amp to Kaspersky antivirus scan exclusion list
+While working on an Axway workstation, you might face an issue where antivirus protection will prevent your amp client to successfully establish connection with external amp services (working locally will of course not cause any issue).
 
-`docker volume rm $(docker volume ls -q)`
+ - Find instructions to allow your amp client [here](https://axway.jiveon.com/docs/DOC-31691)
 
+ ***NOTE***: Make sure to disable network scan within trusted application for your amp client or VirtualBox environment.