4 ms·
If you use this, your customers' data is now in cleartext between the ELB and your instance. Now, that may be fine, you're already trusting EC2 if you keep clea
by js2 16y ago
If you use this, your customers' data is now in cleartext between the ELB and your instance. Now, that may be fine, you're already trusting EC2 if you keep cleartext data on disk. But it's worth keeping in mind.
- mcodik 16y agoIs there a reason why you cant have one of these forward to an HTTPS port that's using a long-lived self-signed certificate? That way you'd keep things SSL'ed the whole way, but updating your certs becomes easier (upload a new one to the ELB vs distribute it to all your servers). I haven't tried this myself and the docs dont say if its (im)possible, but it seems like that'd be a good feature.
- cperciva 16y agoIs there a reason why you cant have one of these forward to an HTTPS port that's using a long-lived self-signed certificate? Much better: Forward via HTTPS to EC2 instances which are using short-lived certificates. When you boot a new instance to add to your load balancing cluster, have it generate an SSL key which ELB is told to trust. If a node is compromised, you just tell ELB to not trust that certificate any more. But that doesn't seem to be possible, and it still doesn't make up for the fact that putting SSL stacks and $BIGNUM SSL keys together is practically begging to be attacked.
- mcodik 16y agoI'm not a security expert by any means, but why is telling ELB "dont trust cert X" any better than removing the compromised instances from the ELB via the API (or just terminating the instance entirely)?
- pilif 16y agobecause in theory, the private key that was stored on that trusted instance could have been stolen ready to be used to impersonate that machine later on.
- nopal 16y agoIs that hop private?
- cperciva 16y agoNo more or less private than connections between EC2 nodes.
- nopal 16y agoSorry for my ignorance here, but is the connection between EC2 nodes isolated (per account), or is it shared amongst multiple accounts?
- cperciva 16y agoTheoretically traffic over the EC2 network is private. In practice, I wouldn't want to rely on the assumption that no packet ever ends up going somewhere it ought not to; nor would I want to rely on the assumption that information doesn't leak in other ways (e.g., timing side channels -- many routers leak information about recent source packet destination addresses due to the caching of routing table lookups).