Hi Michael, I still cannot replicate your issue in my environment.
What was changed between 1.19.1 and 1.26.0 is that we upgraded the AWS client SDK from 1.x to 2.x (NIFI-8287 [1]). That might have introduced the issue, however the processors work for me as before. I'm trying to find out if you have any special settings I have not tested. Could you please share more details on your configuration? In which AWS region is your SQS queue located? What is the Region property on your processor? What kind of proxy are you using? etc Regards, Peter Turcsanyi [1] - https://issues.apache.org/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 (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 type) and add that as the endpoint override URL. > > We have other processors for AWS such as ListS3 which work just fine with > a standard endpoint (s3.us-east-1.amazonaws.com). > > We do sit behind a proxy. > > Thanks, > Mike > > On Tue, Jan 14, 2025 at 9:11 AM Peter Turcsanyi <turcsa...@apache.org> > wrote: > >> Hi Michael, >> >> I did not manage to replicate the issue. Both 1.26.0 and 2.0.0-M3 work >> fine running on AWS EC2 VM and using instance profile. Also tested with >> 2.1.0. >> >> Are you sure it is not an environment issue on your end? Do you have any >> special settings on the processor or the controller service? >> >> 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. >>> >>> 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 PutSQS in a 2.0.0M3 cluster with same connection time out. I >>> tried to increase the Communications timeout but that did not make a >>> difference. >>> >>> I would like to get this working in 2.0.0M3. I'm using an instance role >>> and I can send an SQS message to a queue using the AWS cli. >>> >>> Trimmed error message in 2.0.0M3 (Java 21.0.3. Linux OS) >>> >>> "Failed to send messages to Amazon SQS; routing to failure >>> software.amazon.awssdk.core.exception.SdkClientException: Unable to >>> execute HTTP request: >>> >>> connection timed out" >>> >>> Thanks for any input. >>> >>
