On 7/19/2019 1:40 PM, Christopher Schultz wrote:
Hash: SHA256


On 7/19/19 13:38, Jerry Malcolm wrote:
I have had a dedicated hosted environment with WAMP and Tomcat for
over 15 years.  I'm very familiar with everything related to that
environment... apache http, mysql, dns server, the file system,
JAMES, and all of my management scripts that I've accumulated over
the years. Everything is in the same box and basically on the same
desktop. But now I have a client that has needs that are best met
in an AWS environment.
Can you explain that in a little more depth? What is it about AWS that
meets their needs better?

I ask because you can provision a one-box wonder in AWS just like you
do on a physical space with a single server. You just have to use
remote-desktop to get into it, and then it's all the same.

But if they want to use RDS, auto-scaling, and other Amazon-provided
services then things can get confusing.
Unfortunately, that is the precise reason we need to go AWS.... Extremely high availability and scalability / load-balancing across multiple instances.  There will need to at least one instance running at all times. Even when doing maintenance/upgrades on other instances.

So the answer to your question really depends upon what the client
thinks they'll be getting by you taking your existing product "to the

I understand just enough AWS to be dangerous, which is not
much.... I do know that it's a bunch of different modules, and I
believe I lose the direct file system access.
That heavily depends upon how you do things. You can get yourself a
server with a disk and everything, just like you are used to doing.
Do you mean AWS offers a 'file server' module that I can basically access directly as a drive from TC?  If so, that eases my mind a bunch.  I manage and serve gigabytes of videos and photos.  I don't really want a full CMS implementation.  Just want a big hard drive I can get to.

I've watched an AWS intro video and a couple of youtube videos on
setting up TC in AWS. But they always starts with "now that you
have your AWS environment set up....".   I am looking for something
that explains the big picture of migrating an existing WAMP+TC to
AWS.  I am not so naive to think that there won't be significant
rip-up to what I have now. But I don't want to do unnecessary
rip-up just because I don't understand where I'm heading.
Basically, I don't know enough to know what I don't know.... But I
need to start planning ahead and learning soon if I'm going to have
any disasters in my code where I might have played it too loose
with accessing the file system directly in my dedicated

Has anyone been down this path before and could point me to some
tutorials targeted to migrating WAMP+TC to AWS? Or possible
hand-hold me just a little...? I'm a pretty quick learner.  I just
don't know where to start.
As usual, start with your requirements :)

Requirements are what I have now in a single box, but with the addition of multiple instances of TC (and HTTPD and/or mySQL?) for HA and load balancing.  Day-1 launch won't be massive traffic and theoretically could be handled by my single dedicated server I have today.  But if this takes off like the client predicts, I don't want to get caught flat-footed and have to throw together an emergency redesign to begin clustering TC to handle the traffic. Rather go live initially with single instance AWS, but with a thought-out (and tested/verified) plan to easily begin clustering when the need hits.

Thanks again for the info.

- -chris
Comment: Using GnuPG with Thunderbird -


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to