media server logo
PricingAPI docsSign inStart in the cloud for free

How to use Callaba Cloud: from AWS launch to first SRT stream

Jul 26, 2022
Iurii Pakholkov, founder of Callaba

Written by Iurii Pakholkov

Founder of Callaba. Building cloud video tools for SRT, RTMP, WebRTC, NDI, live routing, monitoring, recording, and production workflows · LinkedIn

The fastest way to start with Callaba is the cloud path. Launch Callaba Cloud on AWS, sign in to the dashboard, create your first SRT server, send a real stream from OBS Studio, and verify playback in VLC.

This page is built for one practical outcome: move from zero deployment to first working stream without assembling a streaming stack by hand first.

AWS
launch instance
Dashboard
sign in safely
SRT server
create input
OBS
publish stream
VLC
verify receive
The beginner path is one controlled route from AWS launch to first working stream.

What you will accomplish on this page

This is a cloud-first getting-started path. It avoids abstract setup theory and moves directly to a real stream.

  • Launch Callaba Cloud on AWS.
  • Sign in to the dashboard safely.
  • Create your first SRT server.
  • Send a stream from OBS Studio.
  • Receive and verify playback in VLC.

Pre-flight checklist

Prepare these items before opening AWS Marketplace.

  • ☐ AWS account is ready.
  • ☐ You know which AWS region is closest to the stream publisher.
  • ☐ You can save an SSH .pem key safely.
  • ☐ You have OBS Studio installed for the first publish test.
  • ☐ You have VLC installed for the receiver-side playback test.
  • ☐ You understand that AWS charges while the instance is running.
  • ☐ You will tighten security group rules after the first workflow is known.

Part 1. Launch Callaba Cloud on AWS

The AWS route is the fastest production-shaped way to start. You launch a real cloud instance, open the dashboard, and immediately get a controllable environment for ingest, routing, failover, recording and playback workflows.

Open the Callaba Cloud listing on AWS Marketplace and start the launch flow.

Region

Choose a region close to publishers and viewers.

Instance

Use c5.xlarge as a practical early evaluation starting point if unsure.

Security group

Start from seller settings, then tighten ports after you know the workflow.

Key pair

Save the .pem file safely in case direct instance access is needed later.

AWS choices that affect the first evaluation: region, instance type, security group and SSH key pair.

Start from the AWS Marketplace listing

Open the AWS Marketplace page and click Continue to Subscribe.

Callaba Cloud Live Streaming product page on AWS Marketplace, with the Continue to Subscribe button, price box, product overview and highlights.
Callaba Cloud Live Streaming product page on AWS Marketplace, with the Continue to Subscribe button, price box, product overview and highlights.

1. Accept the software terms

Accept the software terms before the configuration step becomes available.

Subscribe to this software screen with Terms and Conditions and the Accept Terms button.
Subscribe to this software screen with Terms and Conditions and the Accept Terms button.

2. Continue to configuration

When the subscription state changes, continue to the configuration screen.

Subscribed state screen with the Continue to Configuration button.
Subscribed state screen with the Continue to Configuration button.

3. Choose the AWS region

Choose the AWS region closest to the stream publisher. This usually matters more than the viewer location for the first ingest test.

Configure this software screen with fulfillment option, software version, Region dropdown and Continue to Launch button.
Configure this software screen with fulfillment option, software version, Region dropdown and Continue to Launch button.

4. Choose the instance type

If you are unsure about the first evaluation size, start with a practical instance type and adjust later after you know the workload.

Launch this software screen with the EC2 Instance Type dropdown visible and t3.2xlarge selected.
Launch this software screen with the EC2 Instance Type dropdown visible and t3.2xlarge selected.

5. Keep VPC and subnet simple for the first test

Leave VPC and subnet settings unchanged unless your team already has a specific AWS network design.

VPC Settings and Subnet Settings screen with a warning not to modify these settings unless you understand them.
VPC Settings and Subnet Settings screen with a warning not to modify these settings unless you understand them.

6. Create a security group from seller settings

Create the security group from seller settings for the first launch, then tighten inbound rules after you know which ports your workflow uses.

Security Group Settings screen with the Create New Based On Seller Settings button.
Security Group Settings screen with the Create New Based On Seller Settings button.
Security Groups notice explaining that all ports are accessible by default and should be reviewed before production use.
Security Groups notice explaining that all ports are accessible by default and should be reviewed before production use.

7. Verify that the new security group is selected

Make sure the group you created is selected before you move to the launch step.

Security Group Settings screen with a selected security group named I_am_a_good_group.
Security Group Settings screen with a selected security group named I_am_a_good_group.

8. Choose or create an EC2 key pair

Select an existing key pair or create a new one in EC2. Save the .pem file safely.

Key Pair Settings screen with an existing key pair dropdown and a link to create a key pair in EC2.
Key Pair Settings screen with an existing key pair dropdown and a link to create a key pair in EC2.
EC2 Create key pair screen with name field, RSA key type, .pem private key format and Create key pair button.
EC2 Create key pair screen with name field, RSA key type, .pem private key format and Create key pair button.

9. Launch the instance

Check the selected security group and key pair, then launch the software.

Final Launch this software screen with Security Group Settings, Key Pair Settings and the Launch button.
Final Launch this software screen with Security Group Settings, Key Pair Settings and the Launch button.

Part 2. Open EC2 and sign in to the Callaba dashboard

Once the instance is live, open the dashboard and remember the basic AWS operating rule: AWS charges while the instance is running. Do not leave test infrastructure up indefinitely.

10. Go from AWS Marketplace to the AWS Console

Open the AWS Console and go to EC2.

AWS Management Console home screen with the EC2 service highlighted.
AWS Management Console home screen with the EC2 service highlighted.

11. Check the region and open Instances

Make sure the same AWS region is selected, then open the Instances page.

EC2 Dashboard screen with the region selector and Instances menu item highlighted.
EC2 Dashboard screen with the region selector and Instances menu item highlighted.

12. Wait for the instance checks

Select the Callaba instance and wait until it is running and the status checks pass.

EC2 Instances table showing instance states and the status check area with 2/2 checks passed.
EC2 Instances table showing instance states and the status check area with 2/2 checks passed.

13. Copy Public IPv4 and keep the Instance ID

Copy the Public IPv4 address and open it in your browser with http://. Keep the Instance ID because it is used as the first password in this AWS Marketplace flow.

EC2 instance details screen with the Public IPv4 address and Instance ID highlighted.
EC2 instance details screen with the Public IPv4 address and Instance ID highlighted.

14. Sign in to Callaba

Use admin as the login and the EC2 Instance ID as the first password for this AWS Marketplace launch.

Callaba Cloud sign in page with login admin, password as the unique Instance ID and Sign In button.
Callaba Cloud sign in page with login admin, password as the unique Instance ID and Sign In button.

15. Remember the AWS cost rule

When your work is over, stop or terminate the EC2 instance so AWS does not keep charging for idle runtime.

AWS charges notice explaining that charges continue while the instance is running and how to stop or terminate it.
AWS charges notice explaining that charges continue while the instance is running and how to stop or terminate it.
EC2 Instances table with the Instance state menu open, showing Stop instance, Reboot instance and Terminate instance.
EC2 Instances table with the Instance state menu open, showing Stop instance, Reboot instance and Terminate instance.

Part 3. Create your first SRT server

Now move from deployment into actual streaming. SRT is a strong first workflow because it exposes the core logic clearly: one side publishes a stream into Callaba, and another side receives it from Callaba.

Publisher port

The port used when OBS or an encoder sends a stream into Callaba.

Receiver port

The port used when a receiver takes the stream out of Callaba.

Latency

A buffer that helps absorb network jitter.

Passphrase

Optional encryption/access control when the workflow needs it.

The first SRT server is easier to understand as one input object with ports, latency, access and routing settings.

16. Open SRT Servers and add a new server

Go to SRT Servers and click Add New.

Callaba dashboard SRT Servers section with the Add New button.
Callaba dashboard SRT Servers section with the Add New button.

17. Fill the main SRT server settings

Use a recognizable name. Set the publisher port, receiver port, latency, optional passphrase, timeout and routing settings. Keep the first setup simple, then tune later after the stream works.

New SRT Server form with basic settings, port, receiver port, latency, bandwidth, timeout, passphrase and routing settings.
New SRT Server form with basic settings, port, receiver port, latency, bandwidth, timeout, passphrase and routing settings.
Lower part of the New SRT Server form with passphrase, SRT routing controls and the Save button.
Lower part of the New SRT Server form with passphrase, SRT routing controls and the Save button.

If you need a deeper explanation of this object, use the dedicated SRT server setup page.

Part 4. Send your first stream from OBS Studio

The next goal is to prove that real media can reach Callaba. Use OBS Studio as the first publisher.

OBS
publisher
Publisher URL
send into Callaba
Callaba
server receives
Receiver URL
take stream out
Publisher URL sends video into Callaba. Receiver URL takes video out.

18. Copy the SRT Publisher URL

In the SRT server list, open Info and copy the SRT Publisher URL. This URL is used by OBS or another publisher to send video into Callaba.

SRT server info modal showing host, publisher port, receiver port, Publisher URL, Receiver URL, latency and bandwidth.
SRT server info modal showing host, publisher port, receiver port, Publisher URL, Receiver URL, latency and bandwidth.

19. Paste the Publisher URL into OBS

Open OBS Studio, add your sources, go to Settings → Stream, paste the SRT Publisher URL into the server field, and start streaming. For a full OBS-specific guide, see how to start SRT streaming in OBS Studio.

OBS Studio Stream settings with Service set to Custom and the SRT Publisher URL in the Server field.
OBS Studio Stream settings with Service set to Custom and the SRT Publisher URL in the Server field.

20. Confirm OBS is sending bitrate

After starting the stream, check that OBS shows active bitrate. Then check Callaba for incoming stream activity before testing any receiver.

OBS Studio status bar while streaming, showing bitrate moving to Callaba.
OBS Studio status bar while streaming, showing bitrate moving to Callaba.

Part 5. Verify playback in VLC

After Callaba receives the stream, verify the receiver side. This proves that the stream can leave Callaba and be consumed by another tool.

21. Use the SRT Receiver URL in VLC

The same SRT server info modal contains the Receiver URL. Copy the Receiver URL, open VLC, choose File → Open Network, paste the URL, and confirm playback.

VLC Open Source dialog with the Network tab selected and the SRT Receiver URL in the URL field.
VLC Open Source dialog with the Network tab selected and the SRT Receiver URL in the URL field.
VLC playback result screen showing the received stream after opening the SRT Receiver URL.
VLC playback result screen showing the received stream after opening the SRT Receiver URL.

What to do next in Callaba Cloud

Once the first stream works, the cloud deployment becomes more than a demo. You can keep the same input and build real workflows around it.

Multiview

Watch several live inputs from one browser board.

Recording

Save the incoming stream for archive, replay or post-production.

Restreaming

Send one input to multiple destinations.

Failover

Prepare a main and backup contribution path before the live window.

Once the first stream works, the same input can lead to real production workflows.

Start with Callaba Cloud and your first SRT server

Launch Callaba Cloud, create one SRT server, send a real stream from OBS, and verify playback before adding multiview, recording, restreaming, failover, playback or API workflows.