Our team adapted the Metron Single Node VM install to deploy a single node to AWS.https://cwiki.apache.org/confluence/display/METRON/Dev+VM+Install
Our Vagrent file is here:https://github.com/LTW-GCR-CSOC/csoc-installation-scripts/blob/master/amazon-deploy/Metron/Vagrantfile
You can define your AWS Elastic IP, Subnet ID, and Security Group ID.
Hope it helps.
Ahmed Shah (PMP, M. Eng.)
Cybersecurity Analyst & Developer
GCR - Cybersecurity Operations Center
Carleton University - cugcr.com<https://cugcr.com/tiki/lce/index.php>
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Sent: December 8, 2017 9:06 AM
To: [EMAIL PROTECTED]
Subject: Re: AWS elastic IP configuration for metron?
Are you using AWS for a testing, or a more static infrastructure? If it's just to test I've found that just spinning up everything on one big box in AWS could help that problem a bit (if you would point to localhost or similar during setup). Requires a bit of a hack - I have a very old version of what I did here<https://github.com/jonzeolla/metron/tree/single_node_ec2>
to spin it up on one big machine (mostly this<https://github.com/JonZeolla/metron/commit/ad8444af0bb5ca7cfae33e9bd69868d90741da43>
On Fri, Dec 8, 2017 at 12:50 AM pele_smk <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
When spinning up metron is it possible to define the IPs/hostnames to use? Otherwise, upon shutting down the cluster in AWS, hostnames change and updating ambari, etc... a mess seems to ensue. Any tips and tricks to manage turning up a cluster using EIP?