I would like to ask you about connection using AWS API gateway (as trigger for my program built in Lambda).
Here are some reasons why I want to do that instead of using Alexa Skills Kit as trigger (directly with arn). I have some different roles for AWS account but only a Lambda function of one of them (let say Pub) can be accessed from outside (internet).
By using this Pub role and Alexa Skills Kit as trigger I have successfully made nice Alexa Voice Service for my App. But now I want to deploy Alexa also on other roles such as Dev role whose Lambda function can not be accessed from Internet. But unfortunately Amazon gadgets (for instance Echo Dot) can not start the skill.
I did read about some method to access these role and one of them is using API Gateway:
- API gateway as trigger in Lambda side (it works well when I tested POST with request body as intent in json format)
- HTTPS with URL endpoint provided by API gateway in Alexa Simulator side
From here there are so many problems with authentication because Alexa Simulator can only send body as request (in json format) which is automatically generated.
How can I ignore this header (sound crazy) and just send body request through API gateway or config somehow with proxy to get it done?
I found almost no complete solution or instruction in internet for this issue and would like to ask your help.