Skip to content
Getting started

Deploy Habile iEYE on AWS, step by step

From an AWS Marketplace subscription to a console with your first camera on it. This page is the short version; the full deployment and operating guide and the console's own help centre go deeper.

Last updated

Before you start

Have these ready

  • A subscription to Habile iEYE on AWS Marketplace

    AWS will not launch the AMI without one.

  • A VPC and a subnet

    A public subnet for an internet-facing console; a private subnet with a NAT gateway otherwise.

  • A network path to your cameras

    The appliance reaches cameras over RTSP (usually port 554) and ONVIF. Cameras on a site network need a VPN, AWS Direct Connect or a peered VPC.

  • The address range your viewers come from

    The stack asks for it and has no default.

  • An instance size for your cameras

    From about 24 cameras on large to about 750 on 4xlarge.

  • A current browser with WebRTC

    Live video goes to the browser over WebRTC.

Deploy

Five steps to a working console

  1. Subscribe on AWS Marketplace

    On the listing choose Continue to Subscribe, then Continue to Configuration, and pick the Appliance with CloudFormation delivery option and your Region.

  2. Launch the CloudFormation stack

    Choose the VPC, subnet and Availability Zone, who may open the console, the instance type, where recordings are kept (S3 by default), and the administrator and alarm e-mail addresses.

  3. Wait for CREATE_COMPLETE

    The stack reports complete only when the console answers: about six minutes, measured at 6 min 12 s on an m7i.xlarge on 26 October 2026.

  4. Sign in and change the password

    The stack output ConsoleUrl is the console. The first administrator's generated password is in the Secrets Manager secret the stack names; change it at once.

  5. Create an organisation and add cameras

    Add cameras by network discovery or by address, test each stream, and give people accounts. The console's help centre and first-visit tour cover the rest.

Change the first password at once

The generated password in Secrets Manager is for the first sign-in only. After you change it the secret is out of date, and nothing rewrites it.

Operate

Once it is running

Adding cameras

Add a camera by network discovery or by its address, choose the main stream and the substream, and use Test stream before saving: it reports the codec, the picture size, the frame rate and whether there is audio. Never retry a refused camera login by hand: many recorders lock out an address for about half an hour after a few failures, and Habile iEYE holds such a camera for that reason.

Certificates

The appliance serves HTTPS from the first minute with a certificate it issued itself, which browsers warn about. For regular use, set Your host name to a name that points at the stack and Certificate to lets-encrypt, or install your own certificate on the data volume.

Live video and the network

Live video goes from the media server to the browser over WebRTC on port 8189, UDP with a TCP fallback, which the stack opens to the same address range as the console. Viewers behind strict NAT need a STUN or TURN server, set in the appliance's environment file.

Recording storage

With s3 (the default) recordings go to an encrypted bucket and the data volume holds only the database and segments waiting to upload: 200 GiB suits most sites. With ebs everything is on the volume, sized for your whole retention. In a private subnet, give the stack the subnet's route table so uploads use a free S3 endpoint instead of the NAT gateway.

Monitoring

The stack creates four CloudWatch alarms on one SNS topic: system status, instance status, the data volume over 85%, and CPU over 90% for half an hour. Subscribe your on-call to the topic. The console keeps its own camera health and sends a daily digest.

Backup and recovery

The data volume and the recording bucket are the state. Snapshot the volume on your own schedule, for example with AWS Backup. If the instance or the whole stack is lost, create the stack again and name the old volume and bucket: the new instance carries on with the same cameras, users, recordings and settings.

Updating

Subscribe to the new version, then update the stack with the new template and your existing parameters. A new instance takes over the data volume and the bucket; recording stops for a few minutes, so choose a quiet window. If the new instance cannot start the appliance, the update rolls back.

Getting a shell and getting help

Use AWS Systems Manager Session Manager: aws ssm start-session --target <InstanceId>. On the instance, sudo vms-support makes a diagnostic bundle for support@habilelabs.io with no video, no credentials and no database contents.

Go deeper

Where the rest is written down

  • Deployment and operating guide

    Every stack parameter, moving a stack from an earlier version, extending the volume, and deleting safely.

    Open the guide
  • The help centre in the console

    User, administrator and platform guides, and a first-visit tour you can take again from the account menu. Press the ? button once you are signed in.

  • Questions and answers

    Cameras, Regions, storage, pricing and support, each answered in a few sentences.

    Read the FAQ
Get started

See it on your own cameras

Start the free trial from AWS Marketplace and have a console in about six minutes, or book thirty minutes with a HabileLabs engineer to walk through the console and size a deployment for your cameras.

Or email support@habilelabs.io · Monday to Friday, 10:00–19:00 IST

  1. Subscribe on AWS Marketplace30 days with no software charge on one instance; AWS bills the instance and storage.
  2. Launch the stackPick a Region and a size. A working console in about six minutes.
  3. Add your camerasGive the stack a route to your site (a VPN, Direct Connect or a peered VPC) and add each camera by its address.