Route53 boto error "Profile not found" when using IAM Role with AWS config #68711
Labels
affects_2.9
This issue/PR affects Ansible v2.9
aws
bug
This issue/PR relates to a bug.
cloud
module
This issue/PR relates to a module.
python3
support:community
This issue/PR relates to code supported by the Ansible community.
traceback
This issue/PR includes a traceback.
SUMMARY
When using
route53
module using Assumed Role based authentication, module will fail with an error like:May be related to #41185, but this is a Bug not a Feature Request as this method of authentication with Boto is available and works fine with other modules.
ISSUE TYPE
COMPONENT NAME
route53
moduleANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
Using AWS config defining a profile
route53-role-profile
assuming a Role such as:With task such as:
Will cause mentionned error.
Same result when using
AWS_PROFILE
environment variable instead ofprofile:
But using the profile on which access keys are configured directly will work:
Using AWS CLI to perform similar actions with such config works fine.
EXPECTED RESULTS
route53
module to useboto
and properly assume configured role to execute task.ACTUAL RESULTS
Module fail with error:
The text was updated successfully, but these errors were encountered: