-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws_ssm plugin is always using non regional S3 url #307
Comments
I observed the same but with new pull request added ansible_aws_ssm_region to the s3 bucket url and it worked fine. Awaiting merge of the pull request. The parameter aws_s3_region: eu-west-3 won't be recognized and passed to the boto client during the creation of S3 URLs. So with the new pull request from the above bug, boto3 client uses ansible_aws_ssm_region for the S3 constructed URLs. |
@jonormann, can you please give a try to @ramvalleru's PR? #352 |
@goneri: how could I install the version? |
For testing purpose, you could try to replace aws_ssm.py file in ~/.ansible/collections/ansible_collections/community/aws/plugins/connection. For example, if your collections are installed in root, /root/.ansible/collections/ansible_collections/community/aws/plugins/connection. Then try executing the playbook with out "aws_s3_region: eu-west-3".
|
for me it doesn't do it. still without the ansible_aws_ssm_region: EXEC curl 'https://.s3.amazonaws.com |
Ansible_aws_ssm_region is must if the AWS region is other than us-east-1. aws_s3_region is not necessary now but instead ansible_aws_ssm_region should be used. |
Closing now #352 is merged. Thank you @ramvalleru. |
How does this work if the EC2 instance is in a different region, or is the intent of this change for you to have a separate bucket for every region? |
SUMMARY
aws_ssm plugin is using the bucketname.s3.amazonaws.com URL instead of the regional url like bucketname.s3.regionname.amazonaws.com.
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
STEPS TO REPRODUCE
EXPECTED RESULTS
because ansible_aws_ssm_region is set to the correct region the S3 URL for PUT and GET command should use the regional url.
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: