How to run Amazon Echo inside a private network without AWS

Question

I am trying to use Amazon Echo for a utility project inside my company. I have a bunch of intranet sites that I am going to collect information and develop user skills to allow the user to request data. But the client bank (I use java) must be loaded into AWS to create the Lambda function, and only then can this user skill be used. This will not work, as my bank must consume web services from these intranet systems.

Is there a way to run Echo on a private network without using AWS? I tried to find any relevant information on the Internet / stackoverflow, but could not.

Answer 1

We have finished using secure tunneling to create a public URL for our internal web service. It worked like a charm. For this purpose we used ngrok: https://ngrok.com/

Answer 2

You can create a custom skill with an endpoint either in Lambda or on a public network. So you have a few options.

1) You can develop your lambda skill and open a (suitable) gateway in your corporate firewall to provide access to the intranet resources that you need.

2) Develop your skills as a web service (using Java, Python, node.js or another language) and place it on your corporate intranet. Then open the (suitable) gateway in your corporate firewall to make this endpoint public. Direct your skill at this.

2a) There are many complications that create a network endpoint that is associated with SSL certificates. The route that many people (including me) take is to create a proxy server in Lambda . Think about your skill in Lambda, and then specify Lambda in your web service.

Your success in this will depend on how closely you can work with corporate IT to open holes in your firewall. If you are in a large company, it can be difficult. But there is no way around this if you need real-time access to internal web services in real time.