Choosing the Type
This article is released for AWS solution, SendPortal 1.0.3 on AWS.
Elyxia Global Limited provides SendPortal in Amazon Machine Images (AMIs) for AWS EC2 instances. These are all general purpose instances that are well-suited for a variety of purposes.
When choosing an instance for use, pay close attention to the amount of RAM it comes with. The more web sites you intend to host, the more traffic the hosted web sites generate, the more RAM you will need.
- If you are considering trying out, you can choose T2.micro. It provides sufficient resources for testing purposes.
- If you handle small load, T2.micro should also be suitable.
- A server used for medium traffic website should use a T2.medium or an M3.medium instance.
- When choosing an instance for high traffic website, analyze the website’s traffic carefully. Servers with frequently accessed web sites may require up to 1GB RAM per website.
- If you are not sure what instance to choose, we recommend using the M3.medium instance. It suits most users’ needs and is used for hosting most frequently.
Important Note: As per requested by AWS if you are choosing instance type u-12tb1.metal, u-18tb1.metal, u-24tb1.metal, u-6tb1.metal, u-9tb1.metal, please visit https://aws.amazon.com/blogs/aws/now-available-amazon-ec2-high-memory-instances-with-6-9-and-12-tb-of-memory-perfect-for-sap-hana/
When configuring an instance, you will be asked to configure the following options:
- Instance type: choose the server configuration that best suits your needs. For the details on different types of instances, see Instance Types. However, we recommend instances with minimum 1 virtual CPUs and 2 GB memory (recommeded instance t2.small) in order to run smoothly on Linux CentOS 7.
- Storage space: the default allocated storage size is 20 GB for Linux instances. You can specify the necessary storage size when launching a new instance or change it after deployment.
- Security groups: a security group is created based on our recommended specifications. You can configure your own security group based on your requirements.
Type: SSH, Protocol: TCP, Port Range: 22, Destination: 0.0.0.0/0
Type: HTTP, Protocol: TCP, Port Range: 80, Destination: 0.0.0.0/0
Type: HTTPS, Protocol: TCP, Port Range: 443, Destination: 0.0.0.0/0
Type: POP, Protocol: TCP, Port Range: 110, Destination: 0.0.0.0/0
Type: POPS, Protocol: TCP, Port Range: 995, Destination: 0.0.0.0/0
Type: SMTP, Protocol: TCP, Port Range: 25, Destination: 0.0.0.0/0
Type: SMTPS, Protocol: TCP, Port Range: 465, Destination: 0.0.0.0/0
Type: IMAP, Protocol: TCP, Port Range: 143, Destination: 0.0.0.0/0
Type: IMAPS, Protocol: TCP, Port Range: 993, Destination: 0.0.0.0/0
Type: MYSQL/Aurora, Protocol: TCP, Port Range: 3306, Destination: 0.0.0.0/0
Type: Custom TCP Rule, Protocol: TCP, Port Range: 587, Destination: 0.0.0.0/0
Type: All traffic, Protocol: All, Port Range: All, Destination: 0.0.0.0/0
- Key pairs: choose or create a key pair to be used for authentication when accessing the instance. For information and instructions on creating key pairs, see Amazon EC2 Key Pairs.
After the selected instance is initiated, follow the steps below to initialize SendPortal:
Once the instance is initiated, remote into your AWS instance via SSH. When you are prompted “login as”, execute the following command;
$ sudo -i
And your initial credentials for SendPortal and database will be prompted. Please be reminded to change your password after logged into SendPortal.
Reset Administrator Password
To reset your Administrator password, remote into your AWS instance via SSH. When you are prompted “login as”, execute the following command;
$ sudo -i
Our script will NOT change your email address, it will generate a random password and update the record for you automatically.
Error Port 2525
If you hit this error during email sending, it means you haven’t set your mail relay with any service provider. Please follow the guide at https://sendportal.io/docs/email-services/introduction to set up your mail service.
Associate Your Domain
To associate your domain with the application and the AWS IP address, you will need to edit the following files;
File 1: /etc/httpd/sites-available/sendportal.conf
Log on via SSH,
$ sudo -i
$ nano /etc/httpd/sites-available/sendportal.conf
then modify these 2 lines with your domain. Replace example.com with your domain name.
File 2: /var/www/sendportal/.env
Remote into your AWS instance via SSH. When you are prompted “login as”, execute the following command;
$ sudo -i
$ nano /var/www/sendportal/.env
then modify the line with your domain. Replace example.com with your domain name.
Documentation & Configuration
After you have successfully initiatied and logged into SendPortal, you may follow https://sendportal.io/docs to continue SendPortal for configuration and setup.
For community support, please visit https://github.com/mettle/sendportal/issues