Deploy S4L Lite on AWS - DevOps

[esraneufeld]

DevOps:

• Cloud is set up (done, osparc.io is used)
• Audit / Review the cloud w.r.t. security, maintainability and bringing all potential deprecated practices up-to-date
• resource limitations: set the correct VRAM number on the ec2 nodes
• Study ability to bill another account than the NIH one
• AppArmor (to prevent using scripting for malicious outcomes)
• New license server with light features (requires env var)
• STUN/TURN for 5G Video Streaming
• Mailserver
• s4l-web-lite Statuspage and E-Mail Alert / Notification channel for scheduled downtimes

Not strictly DevOps, but relevant for roll-out:

• Projected costs and upper limits are agreed upon
• Monitoring / alerts w.r.t. monthly costs need to be adjusted
• Strict resource limits are in place (see control, provide, and track resources #576, personalizable resource limits #618)

[esraneufeld]

@mrnicegyu11 please fill this case

[pcrespov]

@mguidon Following up PM2 discussion: Please do not forget to enumerate what config you want for this product for instance

• invitations?
• trial accounts?
• 2FA?
• manuals?
• issue tracker?
• email template? support email?
• url?

As example just check TIP's settings. It is important we setup this ASAP. thx

[mguidon]

Very good point. Thanks

[Surfict]

Goal for sprint Katherine Switzer

• Study ability to bill another account than the NIH one
• Plan cost for the two different solutions
• Documentation about creating an entire stack in AWS
• Redirect sim4life.io to osparc.io sim4life (and check name)
• Discuss with POs on above points

[mguidon]

Planned for sprint Zefram Cochrane

• STUN/TURN (on-site and then AWS)
  • dns and machine?
• DNS for license servers (potentially new machine)
• AppArmour
• Env Vars on Deployments
• s4l-lite.io and redirections
• Monitoring services/hardware/cost