Amazon Hosting

[Andrey]

#1302

Amazon Hosting questions and answers.

[Mark Hanson]

#1305

Looking for AWS hosting, come up with your machine architecture so it can be set up for you in a right way.
You may need to sign up with AWS , get required AWS instance with your requirement and share us your AWS new credentials. We can assist you to configure.

IMPORTANT : AWS might have some restriction need some request and rules are need to be modified on CloudPanel. Once you signup the server share us the AWS credentials too we will adjust the settings to make the server hostable for your needs.

[Andrey]

#1377

Hi Mark just though to bring our conversation in here so we can track it back when necessary…
Currently the AWS set up is complete would you please advice what would be the best VOIP architecture on Amazon?

[Mark Hanson]

#1378

I would like to suggest you to start with an instance type such as “m5d.4xlarge” with cloud watch enabled. By Enabling cloud watch you will be able to monitor the server CPU, memory usage ,etc. After complete the server setup and cPanel installtion, we will create an Amazon® RDS™ instance for newly developed project in same region and migrate account from current server to AWS cloud

Please note that, the M5d instances are available in On-Demand, Reserved Instance, and Spot form in the US East (N. Virginia), US West (Oregon), Europe (Ireland), US East (Ohio), and Canada (Central) Regions. Prices vary by Region, and are just a bit higher than for the equivalent M5 instances.

• This reply was modified 10 months, 2 weeks ago by Mark Hanson.

[Andrey]

#1382

Thanks Mark the machine specs looks promising but costly at this development stage. What if we launch “m5d.large” and upgrade as we go? Please advice..

[Mark Hanson]

#1385

I would suggest you to have the voipus account remain now as it is in the present cPanel server and we shall configure RDS instance in AWS and configure it in your present cPanel server. So we can configure the database queries of the voip account redirected and handled by the RDS instance.

[Andrey]

#1386

Hi Mark the other reason of moving VoIP to AWS is to ability to apply for US dedicated IP.

Please let me know if we can achieve it on current server?

• This reply was modified 10 months, 2 weeks ago by Andrey.

[Mark Hanson]

#1388

Then we can go for Instance “m5d.large” and Amazon Aurora “db.t3.medium” database service on US based region. The current webmaklay server is specs wise high but AWS services provide upgradation of server. In future we can update without any issue.

[Mark Hanson]

#1436

All the server set up has been completed:

I’ve installed mariadb 10.3 on the server and migrated the account voip.us from the old server to the current server.Also setup the redis cache on the server too. Please confirm us to reboot the server to test reliability of the server.

[root@server ~]# mysql -V
mysql Ver 15.1 Distrib 10.3.21-MariaDB, for Linux (x86_64) using readline 5.1

[root@server ~]# redis-cli
127.0.0.1:6379> ping
PONG
Further we tested the site by locally pointing on our end, it is loading fine. Check with developer to check the same by locally pointing to their local machine.

# /etc/hosts
100.24.208.120 voip.us http://www.voip.us portal.voip.us

Congratulations with your new machine with AWS!
Cheers

[Jeff Simpson]

#1438

Great work Mark!
Unfortunately the development is in process on webmaklay server so we will forward this new server access to the voip domain owner and once they finished the development they will migrate their newest version of the project to the new voip machine and point they DNS.

[Author]

Posts