Installing on EC2

[Sangam Gupta]

I recently tried to install Jira 4.4 on Amazon EC2 - 64bit Amazon Linux AMI. Install went well - Console gives the message to visithttp://localhost:8080 but when I try to access it using the Amazon url I dont see anything. I did not modify anything and am running on a fresh instance.

Would be great if someone can help out on this.

[Pavel Korsukov]

The installation JIRA on Amazon Web Service EC2 requires the following steps to be done. So, just make sure you have checked all this to ensure you are up and running:

1. Your instance secure group allows you to connect on JIRA port or proxy port
2. Your VPC (if any) has inbound rules for the JIRA or proxy port
3. Your VPC (if any) has outbound rules to allow plugins download as well as inbound rules on
   32768-65535 to get the response
4. Your instance's firewall allows the connection to JIRA port. Commonly you configure iptables especially for RHEL
5. The Java instance have permissions to bind to the system ports (ports lower then 1024)
6. Your JIRA is listening on right DNS name
7. Your DNS is mapped to Elastic IP
8. Your Elastic IP is assigned to the instance

So, as you can see the configuration and deployment can be tricky. I would suggest you to install JIRA or Confluence using the automated deployment services like Deploy4Me. They already configure everyting you need in terms of installation and security with AWS infreastructure. So, just use it: https://deploy4me.com/en/install/jira.html

[justindowning]

It sounds like the firewall is preventing access to tcp/8080. I suggest you either (a) open access to 8080 or (b) if you can't do that, change the port in conf/server.xml to a high TCP port that you can grant access to (eg: 9090). Don't forget to restart JIRA if you modify the server.xml file.

[Przemek Bruski]

It's not EC2-specific anymore:

For jira.domainname.com stuf you have to set up DNS redirects to your IP from your domain name (the way to do this depends on how/where you have registered your domain).

For having multiple virtual host names (jira.domainname.com / confluence.domainname.com etc.) served from the same physical server, you need to set up virtual hosts on your HTTP server. It's a pretty popular task, you should be able to easily find tutorials for your HTTP server on the Internet.

Finally, to hide the different ports (9090 / 9080) behind a common address, you need to set up a fronting server, have a look at how to set up mod_proxy for the products you use. There's Atlassian documentation for that created for each product - just google for mod_proxy and the product name.

[Sangam Gupta]

Thanks Guys ( Przemek and Justin ) - I have now managed to get the server up and running on a ubuntu instance with EBS Volume. Learnt alot because of you guys.

Now i have both Jira and Confluence running on one server with 1 elastic IP. Jira is accessed by 107.x.x.x:9090 and Confluence by 107.x.x.x:9080

Now my last step is to use a domain name with this so when I do jira.domainname.com i can acess the jira part and when I do confluence.domainname.com I can acess the confluence part.

I have already installed apache2 for ubuntu and the server is running.

Would be great if you can provide your thoughts and steps on this.

[Sangam Gupta]

Hi Prezemek

when I do wget http://localhost:8080 I get this in Terminal :

--2011-09-08 01:16:51-- http://localhost:8080/

Resolving localhost... 127.0.0.1

Connecting to localhost|127.0.0.1|:8080... connected.

HTTP request sent, awaiting response... 302 Moved Temporarily

Location: http://localhost:8080/secure/SetupDatabase!default.jspa [following]

--2011-09-08 01:16:51-- http://localhost:8080/secure/SetupDatabase!default.jspa

Reusing existing connection to localhost:8080.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/html]

Saving to: “SetupDatabase!default.jspa”

[ <=> ] 17,778 --.-K/s in 0.001s

2011-09-08 01:16:51 (29.8 MB/s) - “SetupDatabase!default.jspa” saved [17778

So seems like it did install correctly. but I still cant access it outside using the Amazon url

[Przemek Bruski]

I'd go with Justin's suggestion and had a look at the firewall settings from AWS console.

[Przemek Bruski]

Does it work when you try wget http://localhost:8080 directly on the instance? Amazon Linux ships OpenJDK by default, did you try to change it to Sun's/Oracle's JRE?

[David Yu]

You didn't actually try to visit localhost:8080, right? You need to replace localhost with the external IP address of your Amazon instance. Your Amazon management console should be able to reveal the true IP.

[Sangam Gupta]

haha ofcourse not! I did get the IP from the amazon console but still no luck :( Can you recommend whats the best environment to install it