Hi,
I am in the mid stages of developing an Alexa Skill and the Lambda function must make an API request to a public server that only allows whitelisted IP addresses.
So here are my requirements:
- My Alexa Skill uses a Lambda function, and so it must be able to receive trigger requests from the
alexa-appkit.amazon.com service pricincipal (which uses the ARN of my Lambda function to send triggers).
- At the same time, if my lambda function makes a request to an API on the internet, it needs to come from a static public IP.
I have tried setting up a VPC, but I am struggling to understand how I am to attach my Lambda function to a VPC subnet to NAT out to a static public IP while also allowing it to be reachable to be triggered by the Alexa service principal. Is this even possible?
AWS 官方已更新 2 年前
I did something very similar, but the Alexa service could not reach my Lamda function anymore to trigger it. The way it works without a VPC is you just register your Lambda function ARN with the Alexa Service, but I don't see how the Alexa Service can reach it with an ARN if it is behind a NAT gateway now. Maybe I misconfigured something though.
Make sure you updated the route tables as explained in the article.
Wouldn't the Alexa Service now have to send triggers to the public IP address instead? Or would it still be able to send triggers via ARN?