s3: Allow an arbitrary HTTP client to be used
aws.Auth: Check for AWS_CREDENTIAL_FILE env

The location of the credentials file was hardcoded
to ~/.aws/credentials.

see: http://docs.aws.amazon.com/IAM/latest/CLIReference/Options.html
autoscaling: Fix TerminationPolicies serialization
Add GoDoc badge
Merge pull request #105 from fatih/patch-1

Add GoDoc badge
Merge pull request #106 from tegioz/master

Extracting only one instance from DescribeLoadBalancersResponse when the load balancer has more than one
Merge pull request #104 from ambakshi/autoscaling/fix-termination-policies

autoscaling: Fix TerminationPolicies serialization
Merge pull request #103 from ambakshi/auth/check-credentials-env

aws.Auth: Check for AWS_CREDENTIAL_FILE env
- added support for AddTags and RemoveTags
Merge pull request #107 from savaki/master

Added support for AddTags and RemoveTags
Correct ASG tag types, names, and application

Ref http://docs.aws.amazon.com/AutoScaling/latest/APIReference/API_TagDescription.html.
More complete and correct LC and ASG handling

In particular:

* Add a few fields to structs to better reflect the complete AWS APIs.

* Adjust `member>` handling in XML tags to correctly parse multi-item
  elements (ref #97 for a similar case).
ec2: bump version to 2014-06-15
skip signing request if no auth secret is present
Merge pull request #111 from vito/s3-no-auth

skip signing request if no auth secret is present
autoscaling: Support passing the IAMInstanceProfile through to a launch configuration
implement http://goo.gl/DFySJY
Merge pull request #115 from burn-notice/DescribeInstanceStatus

implement http://goo.gl/DFySJY
Merge pull request #114 from grahamc/iam-instance-profile

autoscaling: Support passing the IAMInstanceProfile through to a launch configuration
elb: support Scheme on load balancer describe