You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2025/06/06 16:23:00 UTC

[jira] [Commented] (NIFI-14588) S3 processors fail with an Endpoint Override URL

    [ https://issues.apache.org/jira/browse/NIFI-14588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956636#comment-17956636 ] 

ASF subversion and git services commented on NIFI-14588:
--------------------------------------------------------

Commit 07d906653988eeda2e8d1740cfbc16b1feed01eb in nifi's branch refs/heads/main from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=07d9066539 ]

NIFI-14588 Fixed Endpoint Override URL handling in AWS S3 processors

Signed-off-by: Pierre Villard <pi...@gmail.com>

This closes #9991.


> S3 processors fail with an Endpoint Override URL
> ------------------------------------------------
>
>                 Key: NIFI-14588
>                 URL: https://issues.apache.org/jira/browse/NIFI-14588
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>         Environment: RHEL9 running on a cluster of three t3.medium EC2s on AWS.
>            Reporter: Tim Sloane
>            Assignee: Peter Turcsanyi
>            Priority: Minor
>              Labels: s3
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When I try to use ListS3, FetchS3Object, or PutS3Object with Endpoint Override URL set, NiFi fails with:
> {{AmazonS3Exception: The authorization header is malformed: the region 'us-west-2' is wrong; expecting '{_}<Endpoint Override URL region>{_}'}}
> I just migrated from NiFi 1.28.0 to 2.3, and this problem didn't exist in 1.28.0 (or any versions going back to 1.9 for that matter). The 2.0 documentation still indicates Endpoint Override URL should cause the selected Region to be ignored, but that seems to not be the case.
> I do have a workaround where I set Region to "Use 's3.region' Attribute" and set s3.region in a preceding UpdateAttribute.
> My guess is this is a bug introduced in 2.x.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)