Cannot push publish to S3 buckets in the us-east-2 region

[swicken-dotcms]

Parent Issue

No response

Problem Statement

When you attempt to push publish to S3 buckets in us-east-2/eu-central-1 you get a return of '400 bad request'. This appears to occur in the deprecated function 'doesBucketExist'.

AWS logs show this as a malformed authorization header.

According to cloud this could be due to a couple of reasons

1. us-east-2/eu-central-1 is the only US region that supports Signature Version 4 only (does not support both Version 2 and Version 4), this seems the most likely cause since it's claiming our header is malformed.
2. We might not be using region specific endpoints

Steps to Reproduce

1. Create an S3 bucket in the us-east-2 region/eu-central-1
2. Configure PP to push to that bucket
3. Attempt to push to the bucket
4. Get a 400 bad request.

Acceptance Criteria

You should be able to push to buckets in all AWS regions. Let's test against:

• [x] eu-central-1
• [x] eu-west-1
• [x] us-east-1
• [x] us-east-2
• [x] us-west-1
• [x] us-west-2
• [x] ca-central-1

dotCMS Version

23.03, 23.01

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

Update the doesBucketExist call to use doesBucketExistV2

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[swicken-dotcms]

This is not stale

[wezell]

#22449 did not fix the issue?

[swicken-dotcms]

@wezell no it did not, I believe its because we did not update our call to doesBucketExist as I put in my acceptance criteria

https://dotcms.zendesk.com/agent/tickets/114366 ticket on 23.10.24

[dsolistorres]

Internal QA passed: bundle successfully was push published to S3 bucket in us-east-2 region

[bryanboza]

Fixed, tested on the last master and now it is working as expected