You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Sivaprasanna Sethuraman (JIRA)" <ji...@apache.org> on 2018/12/12 14:52:00 UTC
[jira] [Updated] (NIFI-5893) Wrong region id is being used for
custom region in AbstractAWSProcessor
[ https://issues.apache.org/jira/browse/NIFI-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sivaprasanna Sethuraman updated NIFI-5893:
------------------------------------------
Component/s: (was: Core Framework)
Extensions
> Wrong region id is being used for custom region in AbstractAWSProcessor
> -----------------------------------------------------------------------
>
> Key: NIFI-5893
> URL: https://issues.apache.org/jira/browse/NIFI-5893
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.8.0
> Environment: RHEL
> Reporter: Andrew Mcdonald
> Assignee: Sivaprasanna Sethuraman
> Priority: Major
>
> The Jira https://issues.apache.org/jira/browse/NIFI-5456 fixed the vpc but for the simpler case of a custom region it is using the default region id and fails with a similar error message.
> Failed to receive messages from Amazon SQS due to com.amazonaws.services.sqs.model.AmazonSQSException: Credential should be scoped to a valid region, not 'us-east-1'. (Service: AmazonSQS; Status Code: 403; Error Code: SignatureDoesNotMatch; Request ID: xxxxx-xxxx-xxxx-xxxx-xxxxxxxx).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)