osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now
I am new here, but I thought it would be a good idea to me to join this board in order to search for answers on some of my questions regarding migration to AWS. I've browsed the forums before posting, but couldn't find answers to most of my questions.
Currently, we're running quite old 1.7.0 OSTicket on Windows. It's a physical server running some other stuff, and since we're migration to cloud for different reasons, we're looking into moving the OSTicket to AWS. I've had quite a lot of experience with AWS, but I am not so familiar with OSTicket, so I have a couple of different scenarions in my mind.
1st would be the most simple one, one EC2 and S3 and RDS to store files / DB, but with Linux and not Windows, since I wouldn't like to pay for extra licenses on AWS, and it has a smaller footprint. Do I need to to take some special care here, with migrating the database to RDS (and should I use MySQL or MariaDB) and is it enough to just before migrating files use the S3 plugin and just copy the files over?
As a 2nd solution, which I would like more, is to have two EC2 instances behind ELB. That way, even though availability zones are not going down that often on AWS, I would have some sort of HA, which is important to me since we run OSTicket as an external ticketing software. Here, concern is about polling e-mails (can be done to set up different time intervals, one option), and sharing the attachments upload folder (both can upload to same S3 bucket, if that's supported) or to use EFS and to mount EFS as regular mount point in Linux.
My apologies in advance if I already posted something discussed in detail here, I couldn't really help myself with the things I found, and also I am quite unfamiliar with the application since the setup on Windows physical box was done ages before I started to work at this job.
I appreciate every help and comment!