大网数据广告活动
服务器运维问答

Security of SSL certs on AWS ELBs / SSL offloading

· 52CE 我爱测

I have some concerns about security and am wondering how AWS will store an SSL certificate deployed to an ELB. I have a wildcard SSL cert for my domain that I want to make sure doesn't persist anywhere where I don't know the step…

问题原文

原帖链接 · Tyler McCarthy · CC BY-SA 3.0

I have some concerns about security and am wondering how AWS will store an SSL certificate deployed to an ELB. I have a wildcard SSL cert for my domain that I want to make sure doesn't persist anywhere where I don't know the steps taken to secure it.

I'm trying to set up a really simple image server on AWS that serves over HTTPS. What I've done is create an nginx server on a T2-micro that proxies to an S3 bucket with my images and put it behind an ELB. Where does that certificate ultimately persist if I put it on the ELB?

As a sidenote, does AWS actually support SSL offloading to the instance an ELB points to? I found hints this is possible in some documentation but couldn't find anything else past that hint.

已采纳解答

原帖链接 · Michael - sqlbot · CC BY-SA 3.0

Where does that certificate ultimately persist if I put it on the ELB?

The certificates are stored in IAM.

They should be as secure, there, as your account credentials are, so this seems like a misplaced concern, to me, once you have this information.

The ELB instances fetch the cert, chain, and private key from IAM whenever they start up or scale up.

Note, of course, that securing your "certificate" is a silly concept. Your certificate, and the chain, are public. They are dutifully handed over to ever web browser that makes a connection. That's how SSL works. The part that needs to be secured is, of course, the private key. Without that, your cert can't be abused.

And IAM secures this. So much so, that not even you can get it back once you've stored it.

If you decided, for whatever reason, that you wanted to fetch your cert and its private key from IAM... well, you can't.

You can list them, overwrite them, and delete them from the IAM database, but not even the account owner can retrieve then. They're secured.

Arguably, on your instances, the accompanying private key would be less secure... but...

You can let ELB balance TCP connections to instances that are handling SSL for themselves, by simply configuring the ELB listener in TCP mode, rather than HTTP.

Of course this puts more work on your instances, and it isn't called "offloading" -- the terminology is reversed -- this configuration would be "not offloading." Offloading would be the normal mode -- an ELB in SSL mode is doing SSL offloading for the instance -- handling SSL instead of the instances, themselves, handling their own SSL.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-06-20)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。