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

Offboarding someone with EB ssh access

· 52CE 我爱测

Recently someone left our organization who had an SSH key for our production Amazon ElasticBeanstalk environment. How is this scenario typically handled? Is a new key-pair created and then distributed among the other people who h…

问题原文

原帖链接 · Eric W. · CC BY-SA 3.0

Recently someone left our organization who had an SSH key for our production Amazon ElasticBeanstalk environment. How is this scenario typically handled? Is a new key-pair created and then distributed among the other people who have access? Is there a best practice for managing EB ssh keys?

EDIT:

The trick we eventually went with was to store an authorized_keys file in a secure S3 bucket and to merge the contents with /home/ec2-user/.ssh/authorized_keys along the lines of the answers provided in this SO question. An important detail for people just coming up to speed on ElasticBeanstalk is that it's really just an abstraction over other AWS services, and it's got some gaps that you have to fill in yourself.

已采纳解答

原帖链接 · Jakuje · CC BY-SA 3.0

Best practice is not to share private keys (you don't share underwear either, don't you?). Everyone should have its public key copied to the machines where he has access and once he leaves, his public keys are removed. Simple as that. This should be handled centrally using SSO or at least some automation such as Ansible.

If you share the key that somebody out of company has, you should really change it by creating a new one(s).

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

资料来源与适用范围

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

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

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