Bug: can not specify port number in http invoke task endpoint

Question

You can not specify a port number in the http invoke task as it fails with a runtime exception.
Two problems I saw here:
- even though a runtime exception is thrown it does not go into the catch task I added for the http task.
- the http task fails with a runtime exception for all given ports

e.g. https://playground.com:4001/webhook

will fail and not go into the catch task.
This information is also not mentioned in the docs.

Thanks for the help :)

Sanath_M · Accepted Answer

Hello,

Step Functions does not support configuring a port number for "ApiEndpoint" parameter when configuring "arn:aws:states:::http:invoke" resource. I understand that the ability to configure a custom port number is indeed a useful feature

Thank you for providing your valuable feedback on the service. I have raised a feature request with the service team on your behalf. While I am unable to comment on if/when this feature may get released, I request you to keep an eye on our What's New and Blog pages for any new feature announcements.

https://aws.amazon.com/new/
https://aws.amazon.com/blogs/aws/

In order to catch the error, have you tried using States.ALL in the catch block?

The workaround here is to use a Lambda function which will send the HTTP request to required endpoint with port.

Siggi · Answer

Thanks Sanath for your reply!
Sadly, it is a States.Runtime error and apparently there is no way to catch those according to the docs?

Bug: can not specify port number in http invoke task endpoint

Relevant content