I hope to be able to try it tomorrow.

> On Jun 16, 2021, at 09:01, Luca Giovannini <[email protected]> 
> wrote:
> 
>  
> Thank you Otto,
>  
> please let me know if you need any additional information to set up the 
> processor with my configuration!
>  
> Just an additional element: I cloned the flow in a different machine with 
> NiFi 1.11.4 on it and the same exact problem shows up (same error in logs, 
> same absence of the raw API call in the provenance data).
>  
> Thank you again for the help you might be able to provide me…I am really 
> stuck here! ☹
>  
> Luca
>  
>  
> Luca Giovannini
> Information Systems Analyst
> Dedagroup Public Services
> www.linkedin.com/in/lucagio/ <http://www.linkedin.com/in/lucagio/>
> T +39.051.278.928 | M +39.347.799.3183 | VoIP 951.128
> Dedagroup Public Services Srl – Sede di Casalecchio di Reno, Via del Lavoro 67
> www.dedagroup.it/public-services <http://www.dedagroup.it/public-services>
>  
> <image001.jpg> <http://www.dedagroup.it/home>
>  
> Da: Otto Fowler <[email protected]> 
> Inviato: martedì 15 giugno 2021 17:04
> A: [email protected]
> Oggetto: Re: How to access to an Amazon API?
>  
> That error means that we passed info into AWS api ( asked the region to find 
> the resource ) and it said nope, and tried to guess.
> I would have to try to setup the processor with your configuration ( enough 
> to try to parse, ok if it fails later because of cred or whatever ).
>  
> 
> 
> On Jun 15, 2021, at 06:26, Luca Giovannini <[email protected] 
> <mailto:[email protected]>> wrote:
>  
>  
> Thank you Otto,
>  
> I can confirm that the resource API is correct: I tested it successfully with 
> Postman by doing a GET on the request URL 
> (https://zsslnu1awf.execute-api.eu-west-1.amazonaws.com/prod/test 
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzsslnu1awf.execute-api.eu-west-1.amazonaws.com%2Fprod%2Ftest&data=04%7C01%7CLuca.Giovannini%40dedagroup.it%7Cd7c5327ecb2f4d502c3308d9300ecf9c%7Cbbf156d433fa4fee86f62cfcb1359ef0%7C0%7C0%7C637593662448072299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UgKYU8cuDkNR7KcUjOEJfmAOiYnlzxsltoQvACjWWBw%3D&reserved=0>)
>  and providing AccessKey, SecretKey and AWS Region in the “Authorization” tab 
> of the Postman client.
>  
> I also checked log/nifi-app.log and the only informative line that I found is:
> 2021-06-15 11:59:24,046 INFO [Timer-Driven Process Thread-8] 
> c.a.i.DefaultServiceEndpointBuilder {execute-api, eu-west-1} was not found in 
> region metadata, trying to construct an endpoint using the standard pattern 
> for this region: 'execute-api.eu-west-1.amazonaws.com 
> <https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fexecute-api.eu-west-1.amazonaws.com%2F&data=04%7C01%7CLuca.Giovannini%40dedagroup.it%7Cd7c5327ecb2f4d502c3308d9300ecf9c%7Cbbf156d433fa4fee86f62cfcb1359ef0%7C0%7C0%7C637593662448072299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6Snijmjgzpk3iXb0LAla0kUe%2FXOgu3iWRaSgQVoY3js%3D&reserved=0>'.
> Which seems to indicate that the processor is not using the endpoint I 
> provided as parameter 
> (https://zsslnu1awf.execute-api.eu-west-1.amazonaws.com/) 
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzsslnu1awf.execute-api.eu-west-1.amazonaws.com%2F)&data=04%7C01%7CLuca.Giovannini%40dedagroup.it%7Cd7c5327ecb2f4d502c3308d9300ecf9c%7Cbbf156d433fa4fee86f62cfcb1359ef0%7C0%7C0%7C637593662448082260%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ogBUugUkELwI5%2FictxdlybPHmONqCs5rxcBdSNoB6T4%3D&reserved=0>...
>  
> I also checked the provenance data (both from the “Provenance” button of the 
> output FlowFile listing and from the “Data Provenance” element of the main 
> menu) for records of the call, but I could not find any provenance data at 
> all for the processor InvokeAWSGatewayApi under scrutiny (my flow right now 
> is made up just by that processor alone and a LogMessage one).
>  
> Is this new information shedding any more light on the problem for you?
>  
> Thank you very much,
> Luca
>  
>  
> Luca Giovannini
> Information Systems Analyst
> Dedagroup Public Services
> www.linkedin.com/in/lucagio/ 
> <https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Flucagio%2F&data=04%7C01%7CLuca.Giovannini%40dedagroup.it%7Cd7c5327ecb2f4d502c3308d9300ecf9c%7Cbbf156d433fa4fee86f62cfcb1359ef0%7C0%7C0%7C637593662448082260%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lyA%2FBjtUB7jJ2GrhS5ddEnIi2dGAqlFGXRrX3v3WIiM%3D&reserved=0>
> T +39.051.278.928 | M +39.347.799.3183 | VoIP 951.128
> Dedagroup Public Services Srl – Sede di Casalecchio di Reno, Via del Lavoro 67
> www.dedagroup.it/public-services 
> <https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dedagroup.it%2Fpublic-services&data=04%7C01%7CLuca.Giovannini%40dedagroup.it%7Cd7c5327ecb2f4d502c3308d9300ecf9c%7Cbbf156d433fa4fee86f62cfcb1359ef0%7C0%7C0%7C637593662448092220%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UuwxvW8qUhkAf3jqfcLkzDTPz9F1KTUfkjOyQZc7NTw%3D&reserved=0>
>  
> <image001.jpg> 
> <https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dedagroup.it%2Fhome&data=04%7C01%7CLuca.Giovannini%40dedagroup.it%7Cd7c5327ecb2f4d502c3308d9300ecf9c%7Cbbf156d433fa4fee86f62cfcb1359ef0%7C0%7C0%7C637593662448092220%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aihREXQgrbO7ABUYMm1pbYCnmjtyVicBlWrNUnChY6U%3D&reserved=0>
>  
> Da: Otto Fowler <[email protected] <mailto:[email protected]>> 
> Inviato: lunedì 14 giugno 2021 19:48
> A: [email protected] <mailto:[email protected]>
> Oggetto: Re: How to access to an Amazon API?
>  
> **ATTENZIONE** Questo messaggio proviene da un ACCOUNT ESTERNO, presta 
> attenzione ad eventuali link o allegati al suo interno.
>  
> You should also confirm the resource api you are trying to call is correct.
>  
> On Jun 14, 2021, at 12:04, Luca Giovannini <[email protected] 
> <mailto:[email protected]>> wrote:
>  
>  
> Hello everybody!
>  
> I have no experience with Amazon services but I now have to access to an API 
> hosted on AWS.
> I have been given the following parameters:
> HTTP Method                                                  GET
> Amazon Region                                               eu-west-1
> Access Key ID                                                   **** (hidden 
> but known)
> Secret Access Key                                       **** (hidden but 
> known)
> Amazon Gateway Api ResourceName    /test
> Amazon Gateway Api Endpoint                 
> https://zsslnu1awf.execute-api.eu-west-1.amazonaws.com/xxxx 
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzsslnu1awf.execute-api.eu-west-1.amazonaws.com%2Fxxxx&data=04%7C01%7CLuca.Giovannini%40dedagroup.it%7Cd7c5327ecb2f4d502c3308d9300ecf9c%7Cbbf156d433fa4fee86f62cfcb1359ef0%7C0%7C0%7C637593662448102172%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=D5qKGcC7gbDWKK0enz7tyo6Gl1ESuDP%2FQy5o4Zt4%2Fds%3D&reserved=0>
>  (anonymized)
>  
> I have used the “InvokeAWSGatewayApi” and set the previous 6 parameters (and 
> only those), but I got {"message": "Internal server error"} as an answer.
> Maybe I did not format the ResourceName correctly (I see here [*] that the 
> ResourceName is usually much longer)?
> I am using NiFi 1.12.1.
>  
> Thank you very much for your help!
>  
> Luca Giovannini
>  
> [*] 
> https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html 
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.aws.amazon.com%2Fgeneral%2Flatest%2Fgr%2Faws-arns-and-namespaces.html&data=04%7C01%7CLuca.Giovannini%40dedagroup.it%7Cd7c5327ecb2f4d502c3308d9300ecf9c%7Cbbf156d433fa4fee86f62cfcb1359ef0%7C0%7C0%7C637593662448102172%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=n7e5ViSSWKg6GL6LGdw4s4eHM%2BWH4LCSOmmaj7XievQ%3D&reserved=0>
>  
>  
> Luca Giovannini
> Information Systems Analyst
> Dedagroup Public Services
> www.linkedin.com/in/lucagio/ 
> <https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Flucagio%2F&data=04%7C01%7CLuca.Giovannini%40dedagroup.it%7Cd7c5327ecb2f4d502c3308d9300ecf9c%7Cbbf156d433fa4fee86f62cfcb1359ef0%7C0%7C0%7C637593662448112140%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qewDlbmRgsHzlzCZXLMDvv%2BkaNIQHZl9hTf0nEOUqyM%3D&reserved=0>
> T +39.051.278.928 | M +39.347.799.3183 | VoIP 951.128
> Dedagroup Public Services Srl – Sede di Casalecchio di Reno, Via del Lavoro 67
> www.dedagroup.it/public-services 
> <https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dedagroup.it%2Fpublic-services&data=04%7C01%7CLuca.Giovannini%40dedagroup.it%7Cd7c5327ecb2f4d502c3308d9300ecf9c%7Cbbf156d433fa4fee86f62cfcb1359ef0%7C0%7C0%7C637593662448112140%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=EXugaNQfeHuBW6138%2FdE1fa8gEgA8HSNNMhbdoa3%2FPc%3D&reserved=0>
>  
> <image001.jpg> 
> <https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dedagroup.it%2Fhome&data=04%7C01%7CLuca.Giovannini%40dedagroup.it%7Cd7c5327ecb2f4d502c3308d9300ecf9c%7Cbbf156d433fa4fee86f62cfcb1359ef0%7C0%7C0%7C637593662448122093%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lAKo2LyzKlAFOVgqOK%2F650xSjw0FkMlhxQ4HdTG%2FafY%3D&reserved=0>
>  
> Le informazioni contenute in questo messaggio di posta elettronica sono 
> riservate e confidenziali e ne e' vietata la diffusione in qualsiasi modo o 
> forma. Qualora Lei non fosse la persona destinataria del presente messaggio, 
> La invitiamo a non diffonderlo e ad eliminarlo, dandone gentilmente 
> comunicazione al mittente. 
>  
> The information included in this e-mail and any attachments are confidential 
> and may also be privileged. If you are not the correct recipient, you are 
> kindly requested to notify the sender immediately, to cancel it and not to 
> disclose the contents to any other person.

Reply via email to