Hi, there.
Just getting started with the 3CX experience, and I've run into a confusing conflict of direction with my install on AWS.
First, AWS Marketplace offers a 3CX Phone System image that runs on a 64-bit (x86) Amazon Machine Image (AMI). It's a simple search to find the product, but I've provided this Link. (I mean, it's the only 3CX product on the AWS Marketplace). It's the latest version, is packaged by 3CX, and it seems like the way to go, right? Spoilers: Maybe not?!?
For me, I installed a 3CX Phone System instance on AWS and then went to the 3CX site to create my user account. Linking the two is where things get really confusing. The instruction set on 3CX regarding AWS installation seems to indicate the preferred method of installation is to "subscribe" (license) and run a Debian 10 instance on AWS and allow their wizard to do the rest of the configuration (via the AWS IAM credentials you create). If you don't use the Debian 10 instance on AWS, the 3CX wizard will not allow you to continue (as the machine type option will not load). This was my first clue that I was working on two different paths.
The 3CX Phone System instance does have its own wizard as well where you can load a 3CX license and perform the setup from there. I can copy the license key from my 3CX profile and put it in there, but now I have a conflict: I have both the 3CX Phone System and Debian 10 instances running at the same time. The 3CX site-based wizard completed as soon as I subscribed to Debian 10.
That leads to my ultimate question: what's the correct, supported method for installing 3CX on AWS? Should we use the pre-packaged image on AWS or let the 3CX wizard do its magic? The wizard sure seems like it does a lot of the background work for you (creating an FQDN, establishes security rules for networking, etc.), so it definitely seems comprehensive. That said, what's the point of the AWS image?
Thanks in advance!
- Dave
Just getting started with the 3CX experience, and I've run into a confusing conflict of direction with my install on AWS.
First, AWS Marketplace offers a 3CX Phone System image that runs on a 64-bit (x86) Amazon Machine Image (AMI). It's a simple search to find the product, but I've provided this Link. (I mean, it's the only 3CX product on the AWS Marketplace). It's the latest version, is packaged by 3CX, and it seems like the way to go, right? Spoilers: Maybe not?!?
For me, I installed a 3CX Phone System instance on AWS and then went to the 3CX site to create my user account. Linking the two is where things get really confusing. The instruction set on 3CX regarding AWS installation seems to indicate the preferred method of installation is to "subscribe" (license) and run a Debian 10 instance on AWS and allow their wizard to do the rest of the configuration (via the AWS IAM credentials you create). If you don't use the Debian 10 instance on AWS, the 3CX wizard will not allow you to continue (as the machine type option will not load). This was my first clue that I was working on two different paths.
The 3CX Phone System instance does have its own wizard as well where you can load a 3CX license and perform the setup from there. I can copy the license key from my 3CX profile and put it in there, but now I have a conflict: I have both the 3CX Phone System and Debian 10 instances running at the same time. The 3CX site-based wizard completed as soon as I subscribed to Debian 10.
That leads to my ultimate question: what's the correct, supported method for installing 3CX on AWS? Should we use the pre-packaged image on AWS or let the 3CX wizard do its magic? The wizard sure seems like it does a lot of the background work for you (creating an FQDN, establishes security rules for networking, etc.), so it definitely seems comprehensive. That said, what's the point of the AWS image?
Thanks in advance!
- Dave
