Hacker News Reader

This should help you: https://gist.github.com/reggi/dc5f2620b7b4f515e68e46255ac042...

Once you have your lambda running inside a VPC, you can assign an elastic IP to the VPC. You don't need an EC2 instance, but you will need a NAT gateway, which is billed at similar levels to a small EC2 instance anyway.

View on HN

Hrmmm perhaps I'll just have to develop something with single packet encrypted port knocking perhaps. ~$36 a month is out of mine price range for something that is like 100k bytes a month (say having an Echo skill that can control Home Assistant)...

Can’t you open up a SSH-tunnel from the lambda? I think there are Python clients if OpenSSH isn’t available in lambda instances (anyone know which binaries are available? I suppose it’s a quite barebone Linux container)

I guess I don't want a socket listening. If AWS would publish their subnets maybe I could limit it to those addresses. It sure seems like they could keep their subnets dynamic and accommodate something like this but I guess not.

They do [1]. In JSON.

[1] https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges....

Nice! Okay hrmmm

Reply on news.ycombinator.com