Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Ken Vida
Setting up Portal Instances in an EC2 instance on Amazon
December 28, 2012 11:05 AM
Answer

Ken Vida

Rank: New Member

Posts: 15

Join Date: March 14, 2012

Recent Posts

Hello,
I have successfully setup a Liferay EE 6.1.2 server on an EC2 instance in the cloud, however we use a number of Portal Instances in our current environment and I am struggling trying to replicate our setup on Amazon.

We use a prefix to get to our individual portal instances in our current environment.

For instance our main site for example will be liferay.com and we have instances setup like dev.liferay.com, stage.liferay.com

Not sure how to do this on Amazon and Linux.

Wondering if we need to setup an elastic IP or alternatively do something with a load balancer.

If anyone has any experience with this, please chime in.

Thanks,
Ken
Srikanth Reddy
RE: Setting up Portal Instances in an EC2 instance on Amazon
July 17, 2014 9:02 PM
Answer

Srikanth Reddy

Rank: New Member

Posts: 5

Join Date: October 22, 2013

Recent Posts

Me Too Facing the same Issue !Any one would like to share their experience?
David H Nebinger
RE: Setting up Portal Instances in an EC2 instance on Amazon
July 17, 2014 9:58 PM
Answer

David H Nebinger

Rank: Liferay Legend

Posts: 7866

Join Date: September 1, 2006

Recent Posts

This is truly an amazon question. Basically you need to know how to get multiple DNS names to point at your EC2 node; when you get that working, your normal liferay virtual host handling takes over and should just work.
Jack Bakker
RE: Setting up Portal Instances in an EC2 instance on Amazon
July 18, 2014 7:24 AM
Answer

Jack Bakker

Rank: Liferay Master

Posts: 688

Join Date: January 3, 2010

Recent Posts

I would put production on its own separate instance. Then after properly set up, you might save an image of it and reuse that for dev and staging. On the staging/dev you could put one apache2 in front with mod_jk, and then multiple Liferay installs listening at port 8009, 8010, etc. If you need SSL for dev and staging, then you might get a wildcard cert, or a multi-domain cert.

Yeah, this is not really an AWS question, more a hosting question that might apply if you were hosting with RackSpace, Digital Ocean, or on your on VPS, or ...