It also means that NLB is transparent. When you put targets behind an NLB, those targets still see the original source IP/port of the client. That means no need to use X-Forwarded-For, or Proxy Protocol, or to reconfigure your logging or on-host security rules.
-
Show this thread
-
This is the "insane magic". You can kind of see how it's possible at the network layer; just route the packets around, rewrite the destination, but leave the source alone. People have been doing this with ordinary routers for some time, yeah yeah.
2 replies 1 retweet 6 likesShow this thread -
But actually what we do is far better than that. We use AWS HyperPlane, an internal service, that tracks the state of billions of connections. It means we can keep connections going to the same target for months, years, no breakage. It's what we use for Elastic File System!
1 reply 5 retweets 28 likesShow this thread -
And now, because we're tracking state, we can actually insert a dedicated secure platform that terminates (and also reinitiates) TLS/SSL, and *still* keep the Network Load Balancer transparent and easy to use. This is doubly insane magic.
4 replies 2 retweets 13 likesShow this thread -
Now with this feature, you can make your front-end world-facing TLS/SSL security our mission, rather than yours. Here are just some of things we do that can be hard to replicate:
1 reply 0 retweets 4 likesShow this thread -
1. NLB uses our
@AWSOpen Open Source implementation of TLS/SSL - Amazon s2n. https://github.com/awslabs/s2n is small and fast and we pour over it for security issues and formally verify more and more of it every year.1 reply 7 retweets 17 likesShow this thread -
2. If/when there are any issues; we take care of the updates and handling, you don't need to drop everything to suddenly upgrade.
1 reply 1 retweet 4 likesShow this thread -
3. We run our TLS/SSL termination on a bastion-like environment. We minimize the surface area, we minimize the number of people who have any kind of access, including access to commit code running on the platform.
2 replies 1 retweet 4 likesShow this thread -
Replying to @colmmacc
I would love to know how you limit commit access and what kind of review process you have for high security code.
1 reply 0 retweets 1 like -
Replying to @GrahamJenson
1/ Since it's open source, you can see our first-level code reviews for s2n on GitHub: https://github.com/awslabs/s2n . We have quite a bit of CI security testing too: https://github.com/awslabs/s2n/tree/master/tests … . We also do another CR before pulling in-house.
1 reply 0 retweets 1 like
2/ For limited commit access: it's mostly the default at AWS that only teams can commit to their own stuff, as well as deploy it. Other contributors are welcome, but they can't merge.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.