[jira] [Comment Edited] (NIFI-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849056#comment-17849056 ] Chien edited comment on NIFI-13191 at 5/23/24 5:57 PM: --- Hello [~exceptionfactory] It would be great if this processor can be restored? We are currently highly dependent on this processor, and it would be a major challenge to replace it with a secure alternative for invoking our gateway. Many thanks was (Author: chien): Hello [~exceptionfactory] [~exceptionfactory] It would be great if this processor can be restored? We are currently highly dependent on this processor, and it would be a major challenge to replace it with a secure alternative for invoking our gateway. Many thanks > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849056#comment-17849056 ] Chien edited comment on NIFI-13191 at 5/23/24 5:57 PM: --- Hello [~exceptionfactory] [~exceptionfactory] It would be great if this processor can be restored? We are currently highly dependent on this processor, and it would be a major challenge to replace it with a secure alternative for invoking our gateway. Many thanks was (Author: chien): Hello [~exceptionfactory] [~exceptionfactory] It would be great if this processor can be restored? We are currently highly dependent on this processor, and it would be a major challenge to replace it with a secure alternative for invoking our gateway. > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849056#comment-17849056 ] Chien commented on NIFI-13191: -- Hello [~exceptionfactory] [~exceptionfactory] It would be great if this processor can be restored? We are currently highly dependent on this processor, and it would be a major challenge to replace it with a secure alternative for invoking our gateway. > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847309#comment-17847309 ] Chien commented on NIFI-13191: -- [~exceptionfactory] Thank you for replying. There are two main reasons we are currently using InvokeAWSGatewayApi with IAM credentials: # To work around bug in the DynamoDB and SQS processors, we are forwarding via an API Gateway instead: [NIFI-12836] Connection pool shut down and SocketException for many AWS processors - ASF JIRA (apache.org) # We need to call the AWS SES service, for which there is not a NiFi processor available. > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13191) Deprecate InvokeAWSGatewayApi Processor
[ https://issues.apache.org/jira/browse/NIFI-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847218#comment-17847218 ] Chien commented on NIFI-13191: -- Hello [~jgresock] [~otto] We are currently using the InvokeAWSGatewayApi processor. What is the replacement/recommended way to invoke an AWS API Gateway with AWS credential provider (for IAM credentials) in the new version? > Deprecate InvokeAWSGatewayApi Processor > --- > > Key: NIFI-13191 > URL: https://issues.apache.org/jira/browse/NIFI-13191 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 1.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Similar to the other AWS client library upgrade issues, this targets the > InvokeAWSGatewayApi processor. > Note: After discussing with [~exceptionfactory] and [~otto], we agree that > this processor can be deprecated, and removed in NiFi 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12836) Connection pool shut down and SocketException for many AWS processors
[ https://issues.apache.org/jira/browse/NIFI-12836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820669#comment-17820669 ] Chien commented on NIFI-12836: -- Hello [~Lehel44], thank you for the update. This error happens after nifi is running for a few hours in a Kubernetes cluster but I am not sure of what triggers it. It seems to happen to all the processors at once. This has happened multiple times, all the AWS processors worked for a little while and then connection pool shutdown for a long time. Hope this helps a little bit. Thanks. > Connection pool shut down and SocketException for many AWS processors > - > > Key: NIFI-12836 > URL: https://issues.apache.org/jira/browse/NIFI-12836 > Project: Apache NiFi > Issue Type: Bug >Reporter: Lehel Boér >Priority: Major > > Reported encountering "Connection pool shut down" errors for the > PutDynamoDBRecord, DeleteDynamoDB, and PutSQS processors while running in a > NiFi cluster on version 2.0.0-M1. > * [Stack Trace reported on the mailing list|https://codefile.io/f/ZMXYzHt89X] > https://lists.apache.org/thread/5fbtwk68yr4bcxpp2h2mtzwy0566rfqz > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
