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 or t3.small (recommended) – 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:

Mautic and MariaDB run as containers on the same instance and share its memory. If you send large campaigns, add memory before adding CPU.

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.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your Mautic installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

You do not need to open inbound ports for email. Mautic connects out to your mail provider to send, and connects out to your mailbox over IMAP to process bounces. AWS security groups are stateful, so those outbound connections and their replies are already permitted by the outbound rule below.

You do not need to open port 3306. MariaDB runs on an isolated internal Docker network and is not reachable from outside the instance. This is deliberate.

Outbound Ports:

4. Important Notes:

• Mail Sending Restrictions:
  AWS imposes restrictions on sending emails from EC2 instances by default. To remove this limitation, you may need to submit a request to AWS to lift the email sending blockage before you can use Mautic for email campaigns.