# PR for ec2.py not using full set of AWS credential mechanisms since bc0c169

**URL:** <https://forum.ansible.com/t/pr-for-ec2-py-not-using-full-set-of-aws-credential-mechanisms-since-bc0c169/18148>\
**Category:** Ansible Developer\
**Tags:** aws\
**Created:** [May 2, 2015, 4:16pm UTC](https://forum.ansible.com/t/pr-for-ec2-py-not-using-full-set-of-aws-credential-mechanisms-since-bc0c169/18148 "2015-05-02T16:16:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![andy2](https://avatars.discourse-cdn.com/v4/letter/a/b9bd4f/32.png) [@andy2](https://forum.ansible.com/u/andy2)\
**Post date:** [May 2, 2015, 4:16pm UTC](https://forum.ansible.com/t/pr-for-ec2-py-not-using-full-set-of-aws-credential-mechanisms-since-bc0c169/18148/1 "2015-05-02T16:16:18Z")

</div>

Hi,

I’ve just submitted PR #1243 to ansible-modules-core

This fixes an issue introduced with the update to only match group names in this VPC.

The connection to boto.vpc in that commit only references aws\_access\_key and aws\_secret\_key, which removed the ability to supply a boto profile name or use env variables for the credentials.

The fix I used was to re-use get\_aws\_connection\_info instead of get\_ec2\_creds, so that the vpc connect call has the same parameters as the ec2 one.

Hopefully someone can get to this soon, as I suspect it is blocking a lot of people using AWS from moving past the 1.8.4 release.

Andy