Abstract
In these unprecedented times of a global pandemic, video conferencing has taken the center stage when it comes to meetings, or virtually so. With recent security issues, bans, and class action lawsuits reported against a popular videoconferencing service, and a recent petition moved at the Supreme Court of India in this matter, it becomes important to find secure alternatives without losing functionality.
This talk covers setting up a self-hosted instance of Jitsi Meet, a secure and opensource alternative with maximum security and privacy (in Tor we trust). The talk shall start with a no-code setup of Jitsi Meet on Amazon AWS using Terraform Cloud, and then we will dive in deeper into what happens behind the scenes.
Expected Duration - 30 to 45 minutes + 15 minutes for QnA
Track - Beginner
Pre-requisites - None. Having Terraform CLI installed is desired to practice along, but not required.
Resources
- Jitsi Meet Homepage
- Infrastructure as Code
- Orchestration
- DNS
- WebRTC
- This is what end-to-end encryption should look like!
- Simulcast
- Terraform CLI Installation instructions
- Installing Jitsi Meet on Amazon AWS with Terraform
- Dancing Pigs
Slides/Talk Outline
- What is the difference between hosted software and self-hosted software, and why you should care
- What are the basic requirements for any self-hosted online solution?
- Self-hosting manually
- Infrastructure as code
- No-code setup of Jitsi Meet with Amazon AWS and Terraform Cloud
- Gotchas
- Network bandwidth
- Number of participants
- Cost
- Under the hood
- What is Terraform?
- What is Amazon AWS?
- What is an Amazon EC2 instance?
- What is Route53?
- How does this play together?
- Running it from your local machine
- Enhancements and possibilities with Jitsi
- Live streaming and recording
- Collaboration
- Single Sign On
- Integration with SIP for audio/voice calls
- A word on enterprise scalability
- QnA
- Closing remarks
Link to all streams for the session: https://bit.ly/2WVi82F
Preferred time and mode
5pm on Saturday, May 23
Online video conference. We will host it on a self-hosted Jitsi setup and eat our own dog food. ;)
Previous Experience
April 2020 - Interactive session at RebootFest on Lean Practices for Remote Teams
Feb 2020 - A talk on Project Langdon at JSFoo Pune.
Feb 2020 - Panel discussion on Tooling and Processes for Managing Large Codebases at JSFoo Pune.
Checklist
Place an '[x]' (no spaces) in all the fields you agree to. You can keep the fields blank on which you don't agree
The talk/workshop speaker agrees to,
Abstract
In these unprecedented times of a global pandemic, video conferencing has taken the center stage when it comes to meetings, or virtually so. With recent security issues, bans, and class action lawsuits reported against a popular videoconferencing service, and a recent petition moved at the Supreme Court of India in this matter, it becomes important to find secure alternatives without losing functionality.
This talk covers setting up a self-hosted instance of Jitsi Meet, a secure and opensource alternative with maximum security and privacy (in Tor we trust). The talk shall start with a no-code setup of Jitsi Meet on Amazon AWS using Terraform Cloud, and then we will dive in deeper into what happens behind the scenes.
Expected Duration - 30 to 45 minutes + 15 minutes for QnA
Track - Beginner
Pre-requisites - None. Having Terraform CLI installed is desired to practice along, but not required.
Resources
Slides/Talk Outline
Link to all streams for the session: https://bit.ly/2WVi82F
Preferred time and mode
5pm on Saturday, May 23
Online video conference. We will host it on a self-hosted Jitsi setup and eat our own dog food. ;)
Previous Experience
April 2020 - Interactive session at RebootFest on Lean Practices for Remote Teams
Feb 2020 - A talk on Project Langdon at JSFoo Pune.
Feb 2020 - Panel discussion on Tooling and Processes for Managing Large Codebases at JSFoo Pune.
Checklist
Place an '[x]' (no spaces) in all the fields you agree to. You can keep the fields blank on which you don't agree
The talk/workshop speaker agrees to,