I'm having a play with running the Unifi software up on a AWS instance.

I thought it would be relatively straight forward, launch instance, install Unifi, set up security groups and I'm away.

So I have the following,
- Ubuntu 12.04 LTS
- Elastic IP assigned to the instance (54.206.47.245)
- Security group set up with ports for Unifi (TCP 8443, 8080, 8843, 8880 and UDP 3478, as well as SSH & ICMP obviously)
- Appropriate iptables rules in the VM for the above ports (accept rules in the input chain, no output or forward rules yet)

I can connect with SSH no problem. But I can't access the controller management which appears on 'https://54.206.47.245:8443/'

I am fairly certain the controller is running and listening...
'netstat -tlp' returns
tcp 0 0 *:8443    *:* LISTEN 853/java
tcp 0 0 *:27017  *:* LISTEN 740/mongod
tcp 0 0 *:8843    *:* LISTEN 853/java
tcp 0 0 *:8880    *:* LISTEN 853/java
tcp 0 0 *:http-alt *:* LISTEN 853/java
tcp 0 0 *:28017  *:* LISTEN 740/mongod
tcp 0 0 *:ssh      *:* LISTEN 635/sshd
tcp6 0 0 [::]:ssh [::]:* LISTEN 635/sshd

If I do 'netstat -a|grep 8443' I get...
tcp 0 0 *:8443 *:* LISTEN
tcp 518 0 ip-172-31-2-149.ap:8443 125-236-XXX-XXX.a:52095 CLOSE_WAIT
tcp 518 0 ip-172-31-2-149.ap:8443 125-236-XXX-XXX.a:52094 CLOSE_WAIT
tcp 518 0 ip-172-31-2-149.ap:8443 125-236-XXX-XXX.a:52234 CLOSE_WAIT
tcp 518 0 ip-172-31-2-149.ap:8443 125-236-XXX-XXX.a:52235 CLOSE_WAIT
tcp 518 0 ip-172-31-2-149.ap:8443 125-236-XXX-XXX.a:52154 CLOSE_WAIT

....which shows the connections from me, not sure why they are on close_wait. Maybe that's a clue?

So my overall assumption is that the security groups are set up properly in AWS and the controller is running on the server. But I figure I must be missing something in AWS - perhaps in the VPC side of things.
From what I can figure out from the VPC part is I have routes to the internet and appropriate firewalling.

Am about to put it in the cant be bothered basket but thought i would post up here first.

Any help much appreciated!

Thanks,
Sam