From f5b5741d89fe5e15c523c8336e10acc25c8a4586 Mon Sep 17 00:00:00 2001 From: Guillaume Jacquet Date: Fri, 13 Nov 2015 11:03:05 -0500 Subject: [PATCH] Fix AWS metadata url Fix URL. It was printing an error message on startup: ``` 2015/11/13 15:49:21 [ERR] fingerprint.env_aws: Error querying AWS Metadata URL, skipping ``` By the way is it safe to use latest? Is there a chance that Amazon decides to change the format of the metadata? It could be safer to use something like `http://169.254.169.254/2014-11-05/meta-data` --- client/fingerprint/env_aws.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/client/fingerprint/env_aws.go b/client/fingerprint/env_aws.go index f5e26e7cb..4192a44dc 100644 --- a/client/fingerprint/env_aws.go +++ b/client/fingerprint/env_aws.go @@ -17,7 +17,7 @@ import ( // This is where the AWS metadata server normally resides. We hardcode the // "instance" path as well since it's the only one we access here. -const DEFAULT_AWS_URL = "http//169.254.169.254/latest/meta-data/" +const DEFAULT_AWS_URL = "http://169.254.169.254/latest/meta-data/" // map of instance type to approximate speed, in Mbits/s // http://serverfault.com/questions/324883/aws-bandwidth-and-content-delivery/326797#326797