[NIFI-5893] Wrong region id is being used for custom region in AbstractAWSProcessor

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8.0
• Fix Version/s: 1.9.0
• Component/s: Extensions
• Environment: RHEL
• Assignee: Sivaprasanna Sethuraman
• Reporter: Andrew Mcdonald
• Created: 12/Dec/18 13:39
• Updated: 27/Feb/24 12:37
• Resolved: 19/Dec/18 09:50

Description

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).

 

Issue Links

• is related to: NIFI-8662 Failed to parse AWS region from VPCE endpoint URL in AbstractAWSProcessor
• is related to: NIFI-12846 AWS Assume Role Credentials with VPCE Endpoint URL cannot handle the Region
• links to: GitHub Pull Request #3219