From 4cd70a24671258243f002235f3f0260e8562e379 Mon Sep 17 00:00:00 2001 From: Justin Campbell Date: Fri, 11 Sep 2015 09:42:58 -0400 Subject: [PATCH] Fix Atlas /operations link --- .../source/intro/getting-started/remote-builds.html.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/intro/getting-started/remote-builds.html.markdown b/website/source/intro/getting-started/remote-builds.html.markdown index 6ddb4ece3..5dba242c4 100644 --- a/website/source/intro/getting-started/remote-builds.html.markdown +++ b/website/source/intro/getting-started/remote-builds.html.markdown @@ -72,8 +72,8 @@ Replace "ATLAS\_USERNAME" with your username, then run automatically starts the build. This build will fail since neither `aws_access_key` or `aws_secret_key` are set -in the Atlas environment. To set environment variables in Atlas, navigate to the -[operations tab](https://atlas.hashicorp.com/operations), click the +in the Atlas environment. To set environment variables in Atlas, navigate to +the [Builds tab](https://atlas.hashicorp.com/builds), click the "packer-tutorial" build configuration that was just created, and then click 'variables' in the left navigation. Set `aws_access_key` and `aws_secret_key` with their respective values. Now restart the Packer build by either clicking