1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
2
As you mentioned, API destinations does not support private destinations. To overcome this you can set the target of the rule to a Lambda function that is attached to the VPC and it will invoke the ALB. This is not optimal of course as it adds latency and cost, but this is the only support way of doing it now.
You could also take a different route and use SQS. The rule will send the messages to an SQS queue and the application in the VPC will poll the queue for the messages. ALB will not be required in this case. This is a much bigger change of course.
Yea, neither of those options are really a good thing, and actually we are already using a Lambda to trigger these webhooks. I was just hoping that API Destination would simplify our architecture. Maybe at some point in the future it will be able to attach to a VPC and operate on internal resources.
Thanks for your reply.