Mapping an Ultra Task to AWS API Gateway
Has anyone successfully mapped a pipeline exposed via an Ultra Task to an AWS API Gateway API? I feel like I’m doing everything right, but I’m getting an inexplicable 500 error. Wondering if anyone h...
Forum Discussion
Thanks Sriram. I’ve followed these directions, but we’re still getting a 500 error. On the test page, it says: Execution failed due to configuration error: Invalid endpoint address. Will be following up with our AWS SMEs for deeper logging insights into the problem. I’m certain I’m using the correct endpoint address.
I am also facing same issue . Any update ? Have you solved it ?
Yes, we did solve it. The problem was that API Gateway resides in the public VPC portion of our AWS account, but the SnapLogic call was happening over our private direct connect tunnel into our local environment. We were able to solve the problem by enabling the endpoints as VPC link resources, and setting up a network load balancer that points to the internal SnapLogic URL.
Can you please show me the steps ? I am getting 500 error code in the aws API gateway .
These are the rough steps we took. The Network Load Balancer needs set up as a private IP address target group, pointing to your SnapLogic server by IP address:
Then you create a VPC Link in API Gateway, which is basically giving it a name and associating it to your NLB:
Once your VPC Link is set up, your Integration Request will look something like this:
