Skip to content
This repository has been archived by the owner on Dec 17, 2021. It is now read-only.

Edda

Jump to bottom
Joe Hohertz edited this page May 30, 2014 · 1 revision

HOME > BURI ROLE GUIDE > EDDA

Edda is a Netflix OSS tool that collects information on EC2 configuration over time, and allows query of the state of the configuration, comparisons of differences over time, and more.

This role definition is currently very basic, allowing for the monitoring of a single account.

  1. Configure local/site.yml and build AMI
  2. Create IAM role
  3. Create security group
  4. Launch Exhibitor Cluster
## Step 2: Configure local/site.yml and build AMI

  1. Edit local/site.yml in your Buri build tree and ensure the following is set if needed:

    edda_region: "us-east-1"

  2. Build the AMI for Edda

    ./resnap.sh <base-pvm-ami-ID> edda
## Step 2: Create IAM role
  1. In the AWS IAM console left-side menu, click "Roles"
  2. Click "Create New Role"
  3. Give it a name. ("Edda" is suggested)
  4. On the "Select Role Type" screen, click "Select" next to "Amazon EC2"
  5. Click "Custom Policy", then "Select"
  6. Under "Policy Name", give it the same name as in 3rd point of this section.
  7. Under "Policy Document", paste in the file policies/edda.sample from the Buri distribution
  8. Click "Continue" and then "Create Role" to complete creating the IAM role needed by Exihibitor.
## Step 3: Create security group
  1. In the AWS EC2 console left-side menu, under "Network & Security", click "Security Groups"
  2. Click "Create Security Group"
  3. Give it a name. ("Edda" is suggested), and a description, pick VPC if applicable.
  4. Add a rule to allow SSH from the source IPs you wish to administrate from
  5. Add a rule to allow HTTP from the source IPs you wish to administrate from
  6. Click "Create"
## Step 4: Launch Edda

  1. Select the Edda AMI to launch, and ensure it has the IAM role and security group for Edda applied. You should only have one instance of this running at any given time. It will take a couple minutes to startup as it does the initial collection of configuration data.

  2. Run the following to test, substituting hostname with one of yours. You should see a large amount of information about your instances

    curl 'ec2-12-34-56-78.compute-1.amazonaws.com/edda/api/v2/view/instances;_pp;_expand;'  | less
Clone this wiki locally