Fall back to IAM policy

[lllama]

Boto on an EC2 instance can grab its credentials from AWS directly, rather than from environment variables.

Would it be possible to allow for this? I've monkey patched my local version to just ignore the env vars, but it's not a great solution.

[Photonios]

I've just pushed a commit that makes this possible :)

b3badb5

[Photonios]

Please let me know if this works for you. If so, I'll publish a new version on PyPi.

[lllama]

I think that setting the access key and secret to "None" in the aws config dict will stop boto from authenticating (well it tries to auth with "None" and "None").

I'll try the commit to confirm though. Will try to get to it asap.

[Photonios]

That's pretty much what happens now. If you don't supply the environment variables, it will use None, which will cause Boto to fall back to other methods, such as reading the ~/.aws/credentials file.

[lllama]

So this seems to work, though I have errors about the describe_regions call, but that's because my IAM profile doesn't have those permissions.

[dexterous]

Has this been pushed out to PyPi?

[dexterous]

Simply removing the check for mandatory existence of the AWS_CLOUDWATCH_ACCESS_KEY and AWS_CLOUDWATCH_SECRET_KEY should do the job, the dummy call to ec2.describe_regions() is unnecessary. It could alternatively be replaced with a call to logs.describe_log_groups() instead.