From e0d5e184507f091955cf770617240268d5e2d56f Mon Sep 17 00:00:00 2001 From: Maciej Skierkowski Date: Fri, 8 Dec 2017 15:57:39 -0800 Subject: [PATCH] Calling out AWS CLI dependencies --- .../guides/packer-on-cicd/uploading-images-to-artifact.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/guides/packer-on-cicd/uploading-images-to-artifact.html.md b/website/source/guides/packer-on-cicd/uploading-images-to-artifact.html.md index 3ea0ece15..d981a8b81 100644 --- a/website/source/guides/packer-on-cicd/uploading-images-to-artifact.html.md +++ b/website/source/guides/packer-on-cicd/uploading-images-to-artifact.html.md @@ -14,7 +14,7 @@ The following example uses TeamCity and Amazon S3. ## Example: Uploading to S3 in a TeamCity Build -On the agent machine responsible for building images, install the [AWS Command Line Tool](https://aws.amazon.com/cli/). Since this is a one-time operation, this can be incorporated into the initial agent provisioning step when installing other dependencies. +On the agent machine responsible for building images, install the [AWS Command Line Tool](https://aws.amazon.com/cli/). Since this is a one-time operation, this can be incorporated into the initial agent provisioning step when installing other dependencies. The AWS Command Line tool may require installing additional [dependencies](http://docs.aws.amazon.com/cli/latest/userguide/installing.html) prior. ```shell pip install awscli