AWS EC2 多租户无法扩展：哪种是最简单的实现方法？
需求：我的团队成员并不是特别精通技术，但我们仍然希望他们能够访问托管 ec2< 中的 jupyter 笔记本/code> 实例（可以访问 AWS 中的各种资源）。并非所有人都一直使用此实例，但有理由相信该实例将被一个人或另一个人全天连续使用（并且我们没有预算来按需扩展）。
解决方案：以多租户方式使用单个中型实例，以便基本上每个用户都可以链接到它，并且随着更多用户连接，资源会重新分配-分布式（意味着已经存在的用户将见证RAM和CPU的容量减少 - 由于CPU数量有限而达到极限），并且当他们断开连接时，情况相反发生。
问题&问题：我看到有一些非常强大/复杂的基础设施设计。 我的问题是：满足这种需求的最简单（=维护解决方案最不复杂/最昂贵）的架构是什么？
ps关于安全性：所有用户都是平等的，不存在比其他用户拥有更多权限的用户，只需通过密码即可访问实例，不需要ID管理。
ps 关于缓存会话：一段时间不活动后（或者在这种情况下关闭浏览器），会话将自行终止。不需要使用会话缓存
the need: I have a team of people who are not particularly tech savvy but we still want them to be able to access a jupyter notebook in a hosted ec2 instance (which has got access to a variety of resources in AWS). Not all of the people use this instance all the time but it's reasonable to believe that that the instance will be used continuosly by one person or the other throughout the day ( and we do not have budget to scale up things on demand).
the solution: to use a single medium sized instance in a multi-tenant fashion so that basically every user could link up to it and, as more users connect, resources are re-distributed (meaning the already present users will witness reduced capacity in RAM and CPU - up to a limit as CPUs are finite in number) and, as they disconnect, the opposite happens.
the problem & question: I saw there are some pretty beefy/complicated infrastructure designs for this. my question is: what's the simplest (=least complicated/expensive to maintain solution) architecture to cater such need?
p.s. on security: all users are equal, there are not users who have got more rights than others, instance will be accessible just via a pwd, no ID management is required.
p.s. on caching sessions: after a certain period of inactivity (or you close down the browser in this case), session will be terminated on its own. no session caching needs to be employed
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论