Using config/credential profiles with chef-provisioning-aws

Christine_Draper · January 29, 2015, 9:39pm

Hi,

Is there a way to tell chef-provisioning-aws driver to use a profile rather
than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn’t work.

Regards,
Christine

Tyler_Ball · January 29, 2015, 10:20pm

I am using environmental variables and when I specify CHEF_DRIVER=aws:test1 it uses my profile - does that work for you? If so, I'm guessing it is a bug with with_driver.

What version of chef-provisioning-aws are you using? The ChefDK?

-T

On Jan 29, 2015, at 1:39 PM, Christine Draper christine_draper@thirdwaveinsights.com wrote:

Hi,

Is there a way to tell chef-provisioning-aws driver to use a profile rather than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn't work.

Regards,
Christine

Scott_Ford · January 29, 2015, 10:27pm

This is not working on Master with chef-provisioning-aws last I checked.
You will need to clone down this branch to get that to work...

https://github.com/chef/chef-provisioning-aws/tree/profile_things

On Thu, Jan 29, 2015 at 1:39 PM, Christine Draper <
christine_draper@thirdwaveinsights.com> wrote:

Hi,

Is there a way to tell chef-provisioning-aws driver to use a profile
rather than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn't work.

Regards,
Christine

--

Scott Ford

Consulting Engineer

(415) 763-2270 – f lauck@opscode.com ords@getchef.com – *my: *Linkedin
http://www.linkedin.com/pub/scott-ford/15/47a/6ab/ Twitter
https://twitter.com/sford422

CHEF

GETCHEF.COM http://www.getchef.com/

TM

getchef.com http://www.getchef.com/ Blog
http://www.opscode.com/blog/ Facebook
https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef

Mark_Harrison · January 29, 2015, 10:35pm

Looks like the functionality was added to master here:

and it's in the latest version.

On Thu, Jan 29, 2015 at 5:27 PM, Scott Ford fords@getchef.com wrote:

This is not working on Master with chef-provisioning-aws last I checked.
You will need to clone down this branch to get that to work...

https://github.com/chef/chef-provisioning-aws/tree/profile_things

On Thu, Jan 29, 2015 at 1:39 PM, Christine Draper <
christine_draper@thirdwaveinsights.com> wrote:

Hi,

Is there a way to tell chef-provisioning-aws driver to use a profile
rather than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn't work.

Regards,
Christine

--

Scott Ford

Consulting Engineer

(415) 763-2270 <%28415%29%20763-2270> – f lauck@opscode.com
ords@getchef.com – *my: *Linkedin
http://www.linkedin.com/pub/scott-ford/15/47a/6ab/ Twitter
https://twitter.com/sford422

CHEF

GETCHEF.COM http://www.getchef.com/

TM

getchef.com http://www.getchef.com/ Blog
http://www.opscode.com/blog/ Facebook
https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef

Christine_Draper · January 29, 2015, 10:42pm

Hmm.. I must be doing something stupid somewhere. Doesnt work for me with
the env variable either.

I've tried with both the 0.1.3 version that's in ChefDK 0.3.6, and with
0.2.1 (because I needed subnets).

On Thu, Jan 29, 2015 at 4:20 PM, Tyler Ball tball@chef.io wrote:

I am using environmental variables and when I specify
CHEF_DRIVER=aws:test1 it uses my profile - does that work for you? If so,
I'm guessing it is a bug with with_driver.

What version of chef-provisioning-aws are you using? The ChefDK?

-T

On Jan 29, 2015, at 1:39 PM, Christine Draper <
christine_draper@thirdwaveinsights.com> wrote:

Hi,

Is there a way to tell chef-provisioning-aws driver to use a profile
rather than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn't work.

Regards,
Christine

Christine_Draper · January 30, 2015, 3:21am

It seems that there may be a bug in the profile support. Whatever profile
name I put in to the driver, it appears to be running with the credentials
of the first profile in the file.

On Thu, Jan 29, 2015 at 4:42 PM, Christine Draper <
christine_draper@thirdwaveinsights.com> wrote:

Hmm.. I must be doing something stupid somewhere. Doesnt work for me with
the env variable either.

I've tried with both the 0.1.3 version that's in ChefDK 0.3.6, and with
0.2.1 (because I needed subnets).

On Thu, Jan 29, 2015 at 4:20 PM, Tyler Ball tball@chef.io wrote:

I am using environmental variables and when I specify
CHEF_DRIVER=aws:test1 it uses my profile - does that work for you? If so,
I'm guessing it is a bug with with_driver.

What version of chef-provisioning-aws are you using? The ChefDK?

-T

On Jan 29, 2015, at 1:39 PM, Christine Draper <
christine_draper@thirdwaveinsights.com> wrote:

Hi,

Is there a way to tell chef-provisioning-aws driver to use a profile
rather than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn't work.

Regards,
Christine

Mark_Harrison · January 30, 2015, 3:59pm

Possibly stupid question: do the profiles other than the default one
start with 'profile' (e.g. '[profile test1]') in the credentials file
(the AWS credentials file is weird in that the default profile is just
[default], but others are [profile profilename])? Also, do your
alternate profiles with with the aws command line tools and the
--profile option or other non-chef-provisioning tools?

On Thu, Jan 29, 2015 at 10:21 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

It seems that there may be a bug in the profile support. Whatever profile
name I put in to the driver, it appears to be running with the credentials
of the first profile in the file.

On Thu, Jan 29, 2015 at 4:42 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hmm.. I must be doing something stupid somewhere. Doesnt work for me with
the env variable either.

I've tried with both the 0.1.3 version that's in ChefDK 0.3.6, and with
0.2.1 (because I needed subnets).

On Thu, Jan 29, 2015 at 4:20 PM, Tyler Ball tball@chef.io wrote:

I am using environmental variables and when I specify
CHEF_DRIVER=aws:test1 it uses my profile - does that work for you? If so,
I'm guessing it is a bug with with_driver.

What version of chef-provisioning-aws are you using? The ChefDK?

-T

On Jan 29, 2015, at 1:39 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hi,

Is there a way to tell chef-provisioning-aws driver to use a profile
rather than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn't work.

Regards,
Christine

Christine_Draper · January 30, 2015, 5:41pm

Hi,

There are no stupid questions. I am a relative AWS API and
chef-provisioning newbie, and quite willing to believe its my configuration
problem!.

I have [profile profilename] in .config, but I am using .credentials for
the keys where I understand the format is just [profilename] (the aws
commands dont work if I use [profile profilename] in .credentials). I
have verified that I can create a vpc using --profile with aws ec2
create_vpc (and it fails when I don't use --profile, as the default
credentials don't have authority).

I've also tried moving the credentials into .config, but that doesn't
help.

The most alarming behaviour is if I have no default in credentials, and put
the authorized users credentials first, that's what it uses.

Regards,
Christine

On Fri, Jan 30, 2015 at 9:59 AM, Mark Harrison mharrison@chef.io wrote:

Possibly stupid question: do the profiles other than the default one
start with 'profile' (e.g. '[profile test1]') in the credentials file
(the AWS credentials file is weird in that the default profile is just
[default], but others are [profile profilename])? Also, do your
alternate profiles with with the aws command line tools and the
--profile option or other non-chef-provisioning tools?

On Thu, Jan 29, 2015 at 10:21 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

It seems that there may be a bug in the profile support. Whatever
profile
name I put in to the driver, it appears to be running with the
credentials
of the first profile in the file.

On Thu, Jan 29, 2015 at 4:42 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hmm.. I must be doing something stupid somewhere. Doesnt work for me
with
the env variable either.

I've tried with both the 0.1.3 version that's in ChefDK 0.3.6, and with
0.2.1 (because I needed subnets).

On Thu, Jan 29, 2015 at 4:20 PM, Tyler Ball tball@chef.io wrote:

I am using environmental variables and when I specify
CHEF_DRIVER=aws:test1 it uses my profile - does that work for you? If
so,
I'm guessing it is a bug with with_driver.

What version of chef-provisioning-aws are you using? The ChefDK?

-T

On Jan 29, 2015, at 1:39 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hi,

Is there a way to tell chef-provisioning-aws driver to use a profile
rather than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn't work.

Regards,
Christine

Mark_Harrison · January 30, 2015, 6:42pm

Interesting. You're right about it being just profilename in the
credentials file vs config (today I learned...), and as far as I can
see in the code
(https://github.com/chef/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/credentials.rb#L37)
it does treat them correctly.

I think the behavior you're seeing about it picking the first set of
credentials if there is no default is caused by this:

github.com

chef-boneyard/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/credentials.rb#L22


      
            load_default
          end
          
          include Enumerable
          include Chef::Mixin::DeepMerge
          
          def default
            if @credentials.empty?
              raise "No credentials loaded!  Do you have a ~/.aws/config?"
            end
            @credentials[ENV["AWS_DEFAULT_PROFILE"] || "default"] || @credentials.first[1]
          end
          
          def keys
            @credentials.keys
          end
          
          def [](name)
            @credentials[name]
          end

but that's still implying that it isn't picking up your profilename.

Hopefully someone smarter than me can work out why that's happening.

On Fri, Jan 30, 2015 at 12:41 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hi,

There are no stupid questions. I am a relative AWS API and chef-provisioning
newbie, and quite willing to believe its my configuration problem!.

I have [profile profilename] in .config, but I am using .credentials for the
keys where I understand the format is just [profilename] (the aws commands
dont work if I use [profile profilename] in .credentials). I have verified
that I can create a vpc using --profile with aws ec2 create_vpc (and it
fails when I don't use --profile, as the default credentials don't have
authority).

I've also tried moving the credentials into .config, but that doesn't help.

The most alarming behaviour is if I have no default in credentials, and put
the authorized users credentials first, that's what it uses.

Regards,
Christine

On Fri, Jan 30, 2015 at 9:59 AM, Mark Harrison mharrison@chef.io wrote:

Possibly stupid question: do the profiles other than the default one
start with 'profile' (e.g. '[profile test1]') in the credentials file
(the AWS credentials file is weird in that the default profile is just
[default], but others are [profile profilename])? Also, do your
alternate profiles with with the aws command line tools and the
--profile option or other non-chef-provisioning tools?

On Thu, Jan 29, 2015 at 10:21 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

It seems that there may be a bug in the profile support. Whatever
profile
name I put in to the driver, it appears to be running with the
credentials
of the first profile in the file.

On Thu, Jan 29, 2015 at 4:42 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hmm.. I must be doing something stupid somewhere. Doesnt work for me
with
the env variable either.

I've tried with both the 0.1.3 version that's in ChefDK 0.3.6, and with
0.2.1 (because I needed subnets).

On Thu, Jan 29, 2015 at 4:20 PM, Tyler Ball tball@chef.io wrote:

I am using environmental variables and when I specify
CHEF_DRIVER=aws:test1 it uses my profile - does that work for you? If
so,
I'm guessing it is a bug with with_driver.

What version of chef-provisioning-aws are you using? The ChefDK?

-T

On Jan 29, 2015, at 1:39 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hi,

Is there a way to tell chef-provisioning-aws driver to use a profile
rather than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn't work.

Regards,
Christine

Christine_Draper · January 30, 2015, 7:47pm

My ruby's so-so, but doesnt:

github.com

chef-boneyard/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/credentials.rb#L49


      
            if credentials_ini_file
              @credentials = deep_merge!(@credentials,
                                         load_credentials_ini(credentials_ini_file))
            end
          end
          
          def load_config_ini(config_ini_file)
            inifile = IniFile.load(File.expand_path(config_ini_file))
            config = {}
            if inifile
              inifile.each_section do |section|
                next unless section =~ /^\s*profile\s+(.+)$/ || section =~ /^\s*(default)\s*/
                profile_name = Regexp.last_match(1).strip
                profile = inifile[section].each_with_object({}) do |pair, result|
                  result[pair[0].to_sym] = pair[1]
                end
                profile[:name] = profile_name
                config[profile_name] = profile
              end
            end
            config

mean its only looking for "profile profilename" or "default"?

I may try putting credentials back in .config - seems like that should
work. Maybe I did something wrong last time I tried that.

Christine

On Fri, Jan 30, 2015 at 12:42 PM, Mark Harrison mharrison@chef.io wrote:

Interesting. You're right about it being just profilename in the
credentials file vs config (today I learned...), and as far as I can
see in the code
(
https://github.com/chef/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/credentials.rb#L37
)
it does treat them correctly.

I think the behavior you're seeing about it picking the first set of
credentials if there is no default is caused by this:

https://github.com/chef/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/credentials.rb#L22
but that's still implying that it isn't picking up your profilename.

Hopefully someone smarter than me can work out why that's happening.

On Fri, Jan 30, 2015 at 12:41 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hi,

There are no stupid questions. I am a relative AWS API and
chef-provisioning
newbie, and quite willing to believe its my configuration problem!.

I have [profile profilename] in .config, but I am using .credentials for
the
keys where I understand the format is just [profilename] (the aws
commands
dont work if I use [profile profilename] in .credentials). I have
verified
that I can create a vpc using --profile with aws ec2 create_vpc (and it
fails when I don't use --profile, as the default credentials don't have
authority).

I've also tried moving the credentials into .config, but that doesn't
help.

The most alarming behaviour is if I have no default in credentials, and
put
the authorized users credentials first, that's what it uses.

Regards,
Christine

On Fri, Jan 30, 2015 at 9:59 AM, Mark Harrison mharrison@chef.io
wrote:

Possibly stupid question: do the profiles other than the default one
start with 'profile' (e.g. '[profile test1]') in the credentials file
(the AWS credentials file is weird in that the default profile is just
[default], but others are [profile profilename])? Also, do your
alternate profiles with with the aws command line tools and the
--profile option or other non-chef-provisioning tools?

On Thu, Jan 29, 2015 at 10:21 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

It seems that there may be a bug in the profile support. Whatever
profile
name I put in to the driver, it appears to be running with the
credentials
of the first profile in the file.

On Thu, Jan 29, 2015 at 4:42 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hmm.. I must be doing something stupid somewhere. Doesnt work for me
with
the env variable either.

I've tried with both the 0.1.3 version that's in ChefDK 0.3.6, and
with
0.2.1 (because I needed subnets).

On Thu, Jan 29, 2015 at 4:20 PM, Tyler Ball tball@chef.io wrote:

I am using environmental variables and when I specify
CHEF_DRIVER=aws:test1 it uses my profile - does that work for you?
If
so,
I'm guessing it is a bug with with_driver.

What version of chef-provisioning-aws are you using? The ChefDK?

-T

On Jan 29, 2015, at 1:39 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hi,

Is there a way to tell chef-provisioning-aws driver to use a
profile
rather than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn't work.

Regards,
Christine

Mark_Harrison · January 30, 2015, 7:58pm

Yes. However, there's another method below that one,
load_credentials_ini, that loads from ~/.aws/credentials, and that
appears to be looking for [profilename] directly. The load_inis method
(called by the load_default method towards the bottom) loads both the
contents of ~/.aws/config and ~/.aws/credentials using the two
load_config_ini and load_credentials_ini files, and then merges the
results.

On Fri, Jan 30, 2015 at 2:47 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

My ruby's so-so, but doesnt:
https://github.com/chef/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/credentials.rb#L49
mean its only looking for "profile profilename" or "default"?

I may try putting credentials back in .config - seems like that should work.
Maybe I did something wrong last time I tried that.

Christine

On Fri, Jan 30, 2015 at 12:42 PM, Mark Harrison mharrison@chef.io wrote:

Interesting. You're right about it being just profilename in the
credentials file vs config (today I learned...), and as far as I can
see in the code

(https://github.com/chef/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/credentials.rb#L37)
it does treat them correctly.

I think the behavior you're seeing about it picking the first set of
credentials if there is no default is caused by this:

https://github.com/chef/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/credentials.rb#L22
but that's still implying that it isn't picking up your profilename.

Hopefully someone smarter than me can work out why that's happening.

On Fri, Jan 30, 2015 at 12:41 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hi,

There are no stupid questions. I am a relative AWS API and
chef-provisioning
newbie, and quite willing to believe its my configuration problem!.

I have [profile profilename] in .config, but I am using .credentials for
the
keys where I understand the format is just [profilename] (the aws
commands
dont work if I use [profile profilename] in .credentials). I have
verified
that I can create a vpc using --profile with aws ec2 create_vpc (and it
fails when I don't use --profile, as the default credentials don't have
authority).

I've also tried moving the credentials into .config, but that doesn't
help.

The most alarming behaviour is if I have no default in credentials, and
put
the authorized users credentials first, that's what it uses.

Regards,
Christine

On Fri, Jan 30, 2015 at 9:59 AM, Mark Harrison mharrison@chef.io
wrote:

Possibly stupid question: do the profiles other than the default one
start with 'profile' (e.g. '[profile test1]') in the credentials file
(the AWS credentials file is weird in that the default profile is just
[default], but others are [profile profilename])? Also, do your
alternate profiles with with the aws command line tools and the
--profile option or other non-chef-provisioning tools?

On Thu, Jan 29, 2015 at 10:21 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

It seems that there may be a bug in the profile support. Whatever
profile
name I put in to the driver, it appears to be running with the
credentials
of the first profile in the file.

On Thu, Jan 29, 2015 at 4:42 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hmm.. I must be doing something stupid somewhere. Doesnt work for me
with
the env variable either.

I've tried with both the 0.1.3 version that's in ChefDK 0.3.6, and
with
0.2.1 (because I needed subnets).

On Thu, Jan 29, 2015 at 4:20 PM, Tyler Ball tball@chef.io wrote:

I am using environmental variables and when I specify
CHEF_DRIVER=aws:test1 it uses my profile - does that work for you?
If
so,
I'm guessing it is a bug with with_driver.

What version of chef-provisioning-aws are you using? The ChefDK?

-T

On Jan 29, 2015, at 1:39 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hi,

Is there a way to tell chef-provisioning-aws driver to use a
profile
rather than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn't work.

Regards,
Christine

Christine_Draper · January 31, 2015, 2:57am

Mystery partly solved. It seems to be specifically to do with the aws_vpc
resource (possibly with all of the aws-specific resources). It works OK for
machine. I stuck a breakpoint in aws_driver/driver and discovered the
relevant profile code gets called for machine but not for aws_vpc. I think
I've got as far as I could on this... hopefully its OK if I raise a bug.

Christine

On Fri, Jan 30, 2015 at 1:58 PM, Mark Harrison mharrison@chef.io wrote:

Yes. However, there's another method below that one,
load_credentials_ini, that loads from ~/.aws/credentials, and that
appears to be looking for [profilename] directly. The load_inis method
(called by the load_default method towards the bottom) loads both the
contents of ~/.aws/config and ~/.aws/credentials using the two
load_config_ini and load_credentials_ini files, and then merges the
results.

On Fri, Jan 30, 2015 at 2:47 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

My ruby's so-so, but doesnt:

https://github.com/chef/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/credentials.rb#L49

mean its only looking for "profile profilename" or "default"?

I may try putting credentials back in .config - seems like that should
work.
Maybe I did something wrong last time I tried that.

Christine

On Fri, Jan 30, 2015 at 12:42 PM, Mark Harrison mharrison@chef.io
wrote:

Interesting. You're right about it being just profilename in the
credentials file vs config (today I learned...), and as far as I can
see in the code

(
https://github.com/chef/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/credentials.rb#L37
)
it does treat them correctly.

I think the behavior you're seeing about it picking the first set of
credentials if there is no default is caused by this:

https://github.com/chef/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/credentials.rb#L22

but that's still implying that it isn't picking up your profilename.

Hopefully someone smarter than me can work out why that's happening.

On Fri, Jan 30, 2015 at 12:41 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hi,

There are no stupid questions. I am a relative AWS API and
chef-provisioning
newbie, and quite willing to believe its my configuration problem!.

I have [profile profilename] in .config, but I am using .credentials
for
the
keys where I understand the format is just [profilename] (the aws
commands
dont work if I use [profile profilename] in .credentials). I have
verified
that I can create a vpc using --profile with aws ec2 create_vpc (and
it
fails when I don't use --profile, as the default credentials don't
have
authority).

I've also tried moving the credentials into .config, but that doesn't
help.

The most alarming behaviour is if I have no default in credentials,
and
put
the authorized users credentials first, that's what it uses.

Regards,
Christine

On Fri, Jan 30, 2015 at 9:59 AM, Mark Harrison mharrison@chef.io
wrote:

Possibly stupid question: do the profiles other than the default one
start with 'profile' (e.g. '[profile test1]') in the credentials file
(the AWS credentials file is weird in that the default profile is
just
[default], but others are [profile profilename])? Also, do your
alternate profiles with with the aws command line tools and the
--profile option or other non-chef-provisioning tools?

On Thu, Jan 29, 2015 at 10:21 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

It seems that there may be a bug in the profile support. Whatever
profile
name I put in to the driver, it appears to be running with the
credentials
of the first profile in the file.

On Thu, Jan 29, 2015 at 4:42 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hmm.. I must be doing something stupid somewhere. Doesnt work for
me
with
the env variable either.

I've tried with both the 0.1.3 version that's in ChefDK 0.3.6, and
with
0.2.1 (because I needed subnets).

On Thu, Jan 29, 2015 at 4:20 PM, Tyler Ball tball@chef.io
wrote:

I am using environmental variables and when I specify
CHEF_DRIVER=aws:test1 it uses my profile - does that work for
you?
If
so,
I'm guessing it is a bug with with_driver.

What version of chef-provisioning-aws are you using? The ChefDK?

-T

On Jan 29, 2015, at 1:39 PM, Christine Draper
christine_draper@thirdwaveinsights.com wrote:

Hi,

Is there a way to tell chef-provisioning-aws driver to use a
profile
rather than the default from config/credentials files? I tried

with_driver aws:test1

where test1 is my profile, but that didn't work.

Regards,
Christine

Topic		Replies	Views
Credentials error in Chef Provisioning AWS Chef Infra (archive)	2	755	July 20, 2016
Test-kitchen/ec2 and user_data Chef Infra (archive)	0	1084	May 14, 2015
Kitchen EC2 instance profiles and assume role problem Chef Infra (archive)	0	803	December 19, 2019
RE: RE: Re: Using chef solo to aws distribute keys Chef Infra (archive)	0	262	February 14, 2015
Chef Server S3 Storage Chef Infra (archive)	0	474	October 23, 2019

Using config/credential profiles with chef-provisioning-aws

Related Topics