Horizon Platform Community Hallmark Node on Amazon EC2 ?
Thread Posts Reply To This Post
Viewing 3 posts - 1 through 3 (of 3 total)
  • AndreasKae

    5th October 2014 at 11:35 pm

    Anyone successful with a hallmarked node on an Amazon EC2 instance?

    Mine is running – but not visible from the outside with

    “Failed to connect to node – is NHZ running? Did you open port 7774?”

    I did exactly the same that I did for an NHZ node running successfully on a DigitalOcean droplet, but Amazon EC2 seems to be somehow different:

    It has two IP addresses, a private which is only visible within the EC2 cloud, and an external one.
    I used that external IP address to create the hallmark. I always connect to the same external IP.
    I also checked that external IP by wget -qO- http://ifconfig.me/ip

    The other thing different is Ubuntu 13.10 (at Amazon) instead of Debian7 (at DigitalOcean)

    Not sure what to do now.

    Do I perhaps need an “Elastic IP Addresses”? http://aws.amazon.com/articles/1346
    I don’t think so, because I already have a public IP address … but who knows.

    Or do I have to create a special “security group” ?

    Anyone any experience with amazon EC2 ?



    Horizon: 0.00 HZ
    6th October 2014 at 12:05 am

    Yeah I’ve used EC2 loads. Their firewalls are completely restrictive. It’s quite a pain in the backside getting used to it, but it’s very secure. Here’s Amazon’s guide on how to use their insane, but pretty awesome firewall.

    An elastic IP is only useful if you’re planning on upgrading the rig. The IP you currently have will only be destroyed if you terminate the instance. Elastic IP allows you to connect a given static IP to any of your EC2 instances.


    Horizon: 0.00 HZ
    7th October 2014 at 2:59 am

    Yes, I had to edit the ‘security group’.
    The elastic IP is useful, because it seems to stay same after rebooting.
    Thanks a lot!

Viewing 3 posts - 1 through 3 (of 3 total)