sensu/sensu-aws: plugins/elb/check-elb-health-fog/main.go; 3 LoC

Found a possible issue in [sensu/sensu-aws](https://www.github.com/sensu/sensu-aws) at [plugins/elb/check-elb-health-fog/main.go](https://github.com/sensu/sensu-aws/blob/74db29abe13d69389d8d27e65b7532fb561de5cb/plugins/elb/check-elb-health-fog/main.go#L67-L69)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> reference to instanceID was used in a composite literal at line 68

[Click here to see the code in its original context.](https://github.com/sensu/sensu-aws/blob/74db29abe13d69389d8d27e65b7532fb561de5cb/plugins/elb/check-elb-health-fog/main.go#L67-L69)

Click here to show the 3 line(s) of Go which triggered the analyzer.

```go
for _, instanceID := range instanceIdentifiers {
input.Instances = append(input.Instances, &elb.Instance{InstanceId: &instanceID})
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 74db29abe13d69389d8d27e65b7532fb561de5cb

Start with plugins/elb/check-elb-health-fog/main.go at lines 67-69 and inspect the range-loop pointer use in context. Compare the analyzer finding with the repository's Bug, Mitigated, and Desirable Behavior descriptions, then leave the corresponding reaction as the completed contribution.

Written by the indexing model from the issue text.