S3 bucket create using profile parameter with other provider

[eliteaz]

Summary

with such a simple task:

- name: Create  S3 bucket
  delegate_to: localhost
  s3_bucket:
    name: "{{ item.name }}"
    endpoint_url: "https://s3.eu-central-1.wasabisys.com"
    profile: "wasabi"
    region: "{{ item.region }}"
  with_items: "{{ s3_bucket }}"

get an err Failed to check bucket presence: An error occurred (403) when calling the HeadBucket operation: Forbidden

after removing profile_name from
https://github.com/ansible-collections/amazon.aws/blob/main/plugins/modules/s3_bucket.py#L1160
bucket is created as well

seems like using profile parameter there is additional HEAD header checking.
otherwise than using module access_key and secret_key parameters

Issue Type

Bug Report

Component Name

s3_object, s3_bucket

Ansible Version

ansible [core 2.12.5]
  config file = None
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.8/dist-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.8.10 (default, Jun 22 2022, 20:18:18) [GCC 9.4.0]
  jinja version = 2.11.3
  libyaml = True

Collection Versions

$ ansible-galaxy collection list
amazon.aws           5.1.0
community.aws        5.0.0

AWS SDK versions

$ pip show boto boto3 botocore
Name: boto
Version: 2.49.0
Name: boto3
Version: 1.26.30
Name: botocore
Version: 1.29.30

Configuration

$ ansible-config dump --only-changed

OS / Environment

No response

Steps to Reproduce

- name: Create  S3 bucket
  delegate_to: localhost
  s3_bucket:
    name: "{{ item.name }}"
    endpoint_url: "https://s3.eu-central-1.wasabisys.com"
    profile: "wasabi"
    region: "{{ item.region }}"
  with_items: "{{ s3_bucket }}"

Expected Results

I expect bucket create using profile parameter

Actual Results

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibullbot]

Files identified in the description:

• [plugins/modules/s3_bucket.py](https://github.com/['ansible-collections/amazon.aws', 'ansible-collections/community.aws', 'ansible-collections/community.vmware']/blob/main/plugins/modules/s3_bucket.py)
• [plugins/modules/s3_object.py](https://github.com/['ansible-collections/amazon.aws', 'ansible-collections/community.aws', 'ansible-collections/community.vmware']/blob/main/plugins/modules/s3_object.py)

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @abikouo @alinabuzachis @jillr @lwade @s-hertel @tremble
click here for bot help

[tremble]

Thanks for taking the time to open this Issue.

This issue should be fixed by #1305 and should be available once we release 6.0.0, however there are a number of substantial changes to the S3 modules which are substantial enough that they're unlikely to be backported to 5.x, and as such the fix probably won't be available for a couple of months.