Requirement

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

t3a.small – 2 virtual CPUs and 2 GB memory.
t3.small – 2 virtual CPUs and 2 GB memory.

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

CPU / Memory	Suitable for
2 CPU cores / 2 GB	Evaluation, and small support teams of up to about 5 agents
2 CPU cores / 4 GB	Everyday use by up to about 15 agents, with email ticketing and a public knowledgebase in daily use
4 CPU cores / 8 GB	Larger support teams, several mailboxes, and a growing archive of closed tickets
8 CPU cores / 16 GB	High ticket volumes, many marketplace channels, and sustained concurrent use

UVdesk is a PHP application backed by MariaDB, and both run on this instance. Memory is the first thing to run short: every ticket keeps its full conversation thread and its attachments, so the working set grows with your archive rather than with your headcount. If the helpdesk feels slow before the CPU is busy, add memory first.

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

30 GB (recommended)

A helpdesk grows on disk in two directions at once: the database holding every ticket and its conversation history, and every file your customers attach to them. Both live on this volume, so allow room for a few years of tickets rather than sizing for today.

3. Ports Configuration

To ensure smooth operation of your installation, open the inbound ports below. These three are all that this image needs.

Please note: the database does not need an open port, and must not be given one. MariaDB runs on a private network inside the instance and is reachable only by the application. Opening port 3306 to the internet would expose every ticket, customer address and conversation your helpdesk holds, and is not required for anything.

Please also note: you do not need to open a port for incoming email. UVdesk collects support mail by connecting outwards to your mail provider on a schedule, so nothing needs to be able to reach the instance for email ticketing to work.

Inbound Ports:

Type	Protocol	Port Range	Source	Why
SSH	TCP	22	0.0.0.0/0	To run the one-click installer and the domain setup tool. Restrict this to your own address if you can.
HTTP	TCP	80	0.0.0.0/0	Reaching your helpdesk before you add a domain, and SSL certificate validation afterwards.
HTTPS	TCP	443	0.0.0.0/0	Required once you associate a domain. Without it your site cannot serve HTTPS.

Outbound Ports:

Outbound access is needed to download the application on first boot, to obtain and renew your SSL certificate, and to send and collect support mail through your own mail provider. The default AWS security group allows all outbound traffic, and no change is required.