AWS Marketplace quickstart

Launch Pixop Prime as a single EC2 instance from the published AWS Marketplace listing for your account and Region. The product version shown on the listing (for example under delivery or software version) is what AWS records for that offer; it is not the same identifier as the AMI recipe on the guest. After first boot, run pixop-version on the appliance to see the installed recipe and tool surface. CloudFormation sets up IAM, security groups, and the root volume; the AMI configures the media pipeline on first boot.

Prerequisites

1. Accept the Pixop Prime offer in your AWS account.
2. Choose an existing VPC and subnet (the template does not create a VPC).
3. Ensure the subnet can reach AWS License Manager APIs, DNS, and https://live-pulse.pixop.com over HTTPS.
4. Initialize AWS License Manager once in the buyer account so the service-linked role AWSServiceRoleForAWSLicenseManagerRole exists. The CloudFormation stack does not create it.
5. Prepare trusted CIDRs:
   • SRT input — sources that send to UDP 5000
   • SRT output — receivers that connect to UDP 5001
   • Management — HTTP TCP 8080 (do not use 0.0.0.0/0)
   • SSH — TCP 22 for ec2-user (do not use 0.0.0.0/0)
6. Have an EC2 key pair for SSH.

Launch with CloudFormation

Use the template bundled with the product (pixop-live.yaml). Create the stack with CAPABILITY_IAM.

When launching from Marketplace, AWS supplies the Region-specific ImageId. For a manual test launch you must pass a valid product AMI ID for your Region.

Typical parameters:

Optional helper pixop-live-inputs.sh (in the engineering bundle) discovers VPC, subnet, and key-pair candidates; it does not create resources.

After CREATE_COMPLETE

1. SSH as ec2-user using the key pair and a path allowed by SshCidr.
2. Run license diagnostics:

pixop-license doctor

If the doctor reports a missing License Manager service-linked role, initialize License Manager in the account, then:

sudo systemctl restart pixop-instance-init.service
pixop-license doctor

3. Continue commissioning: Connect your first SRT stream.

Security group (what the stack opens)

Optional aux SRT ports 5002–5003 are not opened; they stay disabled on the AMI.

The instance cannot modify its own security group. If pixop-preflight shows local listeners but peers cannot connect, update the security group or network ACLs outside the instance.

Instance IAM

The stack attaches an instance role with the minimum License Manager actions:

license-manager:ListReceivedLicenses
license-manager:CheckoutLicense
license-manager:CheckInLicense

First boot (high level)

On first boot the appliance generates SRT credentials, completes Marketplace license activation, and starts the primary pipeline (main ingest, egress-main egress, pixop-live). Later reboots do not repeat full activation.

Cold start and EBS

New volumes from snapshots may take several minutes to hydrate. The default launch template requests provisioned volume initialization at 300 MiB/s. During hydration, Pixop may start slowly; this is not a misconfiguration. See Monitoring and troubleshooting.

Stack updates

Operator configuration lives on the root volume (/etc/pixop-live, /var/lib/pixop-live, SRT secrets). Updating ImageId or launch-template volume settings can replace the instance and discard that state. Do not use stack update as an in-place upgrade unless your release procedure explicitly says so.

Next steps

• Connect your first SRT stream
• Configuration
• pixop-license