/jira/browse/NIFI-8287
On Tue, Jan 14, 2025 at 3:22 PM Michael Sharpe <
michael.sha...@forefrontnow.com> wrote:
> I appreciate the feedback. What I did discover and I can't explain is
> that the PutSQS processor in 1.26.0 works with a standard endpoint override
> URL (
I appreciate the feedback. What I did discover and I can't explain is that
the PutSQS processor in 1.26.0 works with a standard endpoint override URL
(for example sqs.us.east-2.amazonaws.com).
However in order to get the PutSQS to work with 2.0.0M4 I had to add a VPC
endpoint (interface
?
Regards,
Peter Turcsanyi
On Fri, Jan 10, 2025 at 3:51 PM Michael Sharpe <
michael.sha...@forefrontnow.com> wrote:
> What changed with the PutSQS processor from 1.19.1 to 1.26.0?
>
> I upgraded to 1.26.0 and all my PutSQS processors started to get a
> connection timeout.
>
&g
What changed with the PutSQS processor from 1.19.1 to 1.26.0?
I upgraded to 1.26.0 and all my PutSQS processors started to get a
connection timeout.
I removed the related aws nar files for 1.26.0 and put the aws nar files
for 1.19.1 in the 1.26.0 cluster and the PutSQS works again.
Tested the
