From 5778fb22370bf484375a64c9eb1dd83db4daf0ce Mon Sep 17 00:00:00 2001 From: Allen Gilliland <agilliland@gmail.com> Date: Wed, 18 May 2016 15:16:15 -0700 Subject: [PATCH] use proper download urls. --- .../operations-guide/running-metabase-on-elastic-beanstalk.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/operations-guide/running-metabase-on-elastic-beanstalk.md b/docs/operations-guide/running-metabase-on-elastic-beanstalk.md index 1c54171afeb..4ab871361f5 100644 --- a/docs/operations-guide/running-metabase-on-elastic-beanstalk.md +++ b/docs/operations-guide/running-metabase-on-elastic-beanstalk.md @@ -54,7 +54,7 @@ When your environment type settings look like the above then go ahead and click The application version describes the exact binary you wish to deploy to your Elastic Beanstalk application. Metabase provides a pre-built AWS Elastic Beanstalk application version which can be linked to directly. Simply enter the following url in the `S3 URL` textbox: -https://s3.amazonaws.com/downloads.metabase.com/v0.17.1/metabase-aws-eb.zip +http://downloads.metabase.com/v0.17.1/metabase-aws-eb.zip Leave all the settings under Deployment Limits on their defaults. These settings won't impact Metabase. @@ -187,7 +187,7 @@ Here's each step: 1. Go to Elastic Beanstalk and select your `Metabase` application * Click on `Application Versions` on the left nav (you can also choose `Application Versions` from the dropdown at the top of the page) * Download the latest Metabase Elastic Beanstalk deployment file - * https://s3.amazonaws.com/downloads.metabase.com/v0.17.1/metabase-aws-eb.zip + * http://downloads.metabase.com/v0.17.1/metabase-aws-eb.zip * Upload a new Application Version * Click the `Upload` button on the upper right side of the listing * Give the new version a name, ideally including the Metabase version number (e.g. v0.13.0) -- GitLab