macklus For those who wish to use the Ajenti control panel in AWS, I have created an AMI optimized with Ajenti v1.2.23 installed. This page shows both its features and its operation, configuration and use, so please read it carefully.
Features
- AMI based on Ubuntu Bionic Beaver
- Ajenti 1.2.23 installed (latest stable version)
- Ajenti VH for virtual accommodations installed (latest stable version)
- Optimized with: nginx, PHP 7, mysql server, ajenti repository
Installation and configuration
Installation
The installation follows the normal process of creating an instance in EC2. The recommended instance size is t3.medium.
The security group usually includes the following permissions:
| Tipo | Protocolo | Rango de puertos | Origen |
| Custome TCP rule | TCP | 20 – 21 | 0.0.0.0/0 |
| SSH | TCP | 22 | 0.0.0.0/0 |
| SMTP | TCP | 25 | 0.0.0.0/0 |
| DNS | UDP | 53 | 0.0.0.0/0 |
| HTTP | TCP | 80 | 0.0.0.0/0 |
| POP3 | TCP | 110 | 0.0.0.0/0 |
| NTP | UDP | 123 | 0.0.0.0/0 |
| IMAP | TCP | 143 | 0.0.0.0/0 |
| (*) HTTPS | TCP | 443 | 0.0.0.0/0 |
| MYSQL | TCP | 3306 | 0.0.0.0/0 |
| (*) Custom TCP rule | TCP | 8000 | 0.0.0.0/0 |
| Custome TCP rule | TCP | 12000 – 12100 | 0.0.0.0/0 |
The fields marked with (*) are essential, either to access the web interface or for the normal operation of the server.
Once the instance is up, we can access using:
- SSH: Using the .pem that we have selected when launching the instance.
- HTTPS: Using the url https: //ip.de.la.instancia: 8000, with root user and key the ID of the instance that we just created.
Configure valid Let’s Encrypt SSL certificate
In order to configure a valid certificate we must first change the host name of the EC2 instance to allow us to generate the certificate. AWS does not allow certificates to be generated for the default name of the instance, because names (and IPs are volatile).
Personalization and support
If you need to customize the default options of the AMI, or have any questions or problems, you can write me at the address:
Recent Comments