Closed roman-parkhunovskyi closed 8 years ago
Confirmed: I have also experienced this behavior. Correct behavior is achieved when AWS_PROFILE is set in the environment. None of '--profile', '--profile-name', or '--profile_name' appear to work as expected.
We may just need to do better work on integrating the new code into the DSL. Unfortunately, I don't have much bandwidth to tackle this before I leave for vacation. https://github.com/bazaarvoice/it-security-scripts/blob/master/deploy/nexpose-engine.rb#L42 is where my working example comes from.
Also possibly relevant: I believe there's something weird about the required format of ~/.aws/config
and ~/.aws/credentials
.
Basically, it appears:
[profile *name*]
[*name*]
Turned out to be an upstream issue: v2.4.1 works, newer ones don't. Published a new version (1.2.2) with it pinned in the Gemfile; we should remove the constraint once the upstream issue is resolved.
Suppose assumed roles are used as follows:
With the provided access configuration in either ~/.aws/credentials or ~/.aws/config it not possible to create a stack via cloudformation-ruby-dsl v1.2.1, aws-sdk-ruby 2.4.2 and ruby 2.3.0: