Feel free to contact me at [email protected] or tweet at me @statisticsftw
This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!
It assumes some knowledge of AWS.
| # for ISAKMP (handling of security associations) | |
| iptables -A INPUT -p udp --dport 500 --j ACCEPT | |
| # for NAT-T (handling of IPsec between natted devices) | |
| iptables -A INPUT -p udp --dport 4500 --j ACCEPT | |
| # for ESP payload (the encrypted data packets) | |
| iptables -A INPUT -p esp -j ACCEPT | |
| # for the routing of packets on the server | |
| iptables -t nat -A POSTROUTING -j SNAT --to-source %IP% -o eth0 | |
| # internet access | |
| iptables -t nat -A POSTROUTING -s 10.0.42.0/24 -o eth0 -m policy --dir out --pol ipsec -j ACCEPT |
Feel free to contact me at [email protected] or tweet at me @statisticsftw
This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!
It assumes some knowledge of AWS.
You can run this by doing the following:
Some notes:
I hereby claim:
To claim this, I am signing this object:
| ### Keybase proof | |
| I hereby claim: | |
| * I am sll on github. | |
| * I am sll (https://keybase.io/sll) on keybase. | |
| * I have a public key ASDJ8crYykTMlbE7oqAZuyV0ZDy8J_LYsLOiZq7rUZujhgo | |
| To claim this, I am signing this object: |