meep wrote:
>
>
> What I'd like to do is get a basic proxy implementation up and running,
> then focus on the skill enhancement so I can get something into the wild
> for people to play with. Then, I can come back on focus on enhanced
> security such as encryption, certs etc.
>
> Thanks again
meep wrote:
>
> The purpose of the proxy is to validate that inbound requests come from
> the Alexa skill and that the userID supplied matches that stored in the
> plug-in. Only traffic that meets these criteria will be passed along to
> LMS.
>
>
> The proxy runs on a user specified port (not
Great work meep! Kinda wish I'd come back to these forums earlier,
actually, as...
...separately, I've hacked together most of a(nother) Alexa ->
Squeezebox integration, more of a "PoC with encouraging results"
currently and not as advanced as this.
Interesting to see how different people have
snoopy86 wrote:
> Great work!! Cant wait to try this.
>
> As for security, we know what ip-s is amazon using and on router you can
> allow only this ip-s to connect to open port.
I'm pretty sure this isn't feasible: AIUI, Lambda doesn't make any
guarantees about where in the AWS estate it
Finally got round to blogging about my DIY take on the Alexa <->
Squeezebox integration, with a few (very amateur) demo videos:
'squeeze-alexa demos'
(http://declension.net/posts/2017-01-03-squeeze-alexa-demos/)
Hopefully will find some time to make it useful to others.
