# Change in behavior when accessing an S3 bucket with dots in the bucket name

**URL:** <https://forum.ansible.com/t/change-in-behavior-when-accessing-an-s3-bucket-with-dots-in-the-bucket-name/18039>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [April 21, 2015, 5:03pm UTC](https://forum.ansible.com/t/change-in-behavior-when-accessing-an-s3-bucket-with-dots-in-the-bucket-name/18039 "2015-04-21T17:03:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Baraa\_Basata1](https://avatars.discourse-cdn.com/v4/letter/b/848f3c/32.png) [@Baraa\_Basata1](https://forum.ansible.com/u/Baraa_Basata1)\
**Post date:** [April 21, 2015, 5:03pm UTC](https://forum.ansible.com/t/change-in-behavior-when-accessing-an-s3-bucket-with-dots-in-the-bucket-name/18039/1 "2015-04-21T17:03:30Z")

</div>

I’m seeing different behavior between Ansible 1.8 and the devel branch when using the s3 module, specifically when there is a dot (“.”) in the bucket name. More details in this closed issue: [https://github.com/ansible/ansible-modules-core/issues/1183](https://github.com/ansible/ansible-modules-core/issues/1183)

$ ansible -i ‘localhost,’ all -c local -m s3 -a “bucket=friendly.mouse mode=create”

The above example works with Ansible 1.8, and it produces an InvalidCertificateException with the devel branch. In both cases, I’m allowing the default behavior of “validate\_certs=yes”.

My understanding is that S3 operations can use [https://s3.amazonaws.com](https://s3.amazonaws.com) as the endpoint to avoid certificate issues with buckets with dots in the name. I think this can happen through boto’s OrdinaryCallingFormat, but I have not confirmed.

For comparison, here is partial output from an example in which I’m using aws-cli:

aws s3 mb s3://friendly.mice --debug # create a bucket

2015-04-21 13:00:08,821 - botocore.endpoint - DEBUG - Sending http request: \<PreparedRequest [PUT]\>  
2015-04-21 13:00:08,821 - botocore.vendored.requests.packages.urllib3.connectionpool - INFO - Starting new HTTPS connection (1): [s3.amazonaws.com](http://s3.amazonaws.com)  
2015-04-21 13:00:10,919 - botocore.vendored.requests.packages.urllib3.connectionpool - DEBUG - “PUT /friendly.mice HTTP/1.1” 200 0

I welcome any thoughts on what the correct behavior should be for the s3 module as well as any suggestions for how I can help to further isolate the difference in behavior.

-Baraa