-
Notifications
You must be signed in to change notification settings - Fork 117
AMIs for NetflixOSS
Latest AMIs
Name: | aminator-ubuntu.yml---x86_64-201309130537-ebs |
---|---|
Description: | name=aminator-ubuntu.yml, arch=x86_64, ancestor_name=foundation-ubuntu-12.04-x86_64-ebs-20130814-0339, ancestor_id=ami-2cac311c, ancestor_version= |
Architecture: | x86_64 (amd64) |
OS: | Ubuntu 12.04 precise |
us-east-1 (N. Virginia) | ami-9deca5f4 | Launch |
---|---|---|
us-west-1 (N. California) | ami-880633cd | Launch |
us-west-2 (Oregon) | ami-bef9668e | Launch |
eu-west-1 (Ireland) | ami-8c799cfb | Launch |
sa-east-1 (San Paulo) | ami-8da50290 | Launch |
ap-northeast-1 (Tokyo) | ami-05950904 | Launch |
ap-southeast-1 (Singapore) | ami-2c90db7e | Launch |
ap-southeast-2 (Sydney) | ami-8d8f12b7 | Launch |
Use the CloudFormation script to do all of the tedious stuff for you. The script is here:
https://github.com/Answers4AWS/netflixoss-ansible/blob/master/cloudformation/aminator.json
and more details instructions are here:
http://answersforaws.com/blog/2013/08/ansible-provisioner-for-aminator/
-
Create an IAM Role called 'aminator' with this policy
-
Click Launch for your desired region
-
Select any instance size, even
t1.micro
-
During the wizard, create a new security group with the following rules
- Port 22: 0.0.0.0/0
-
Once launched,
ssh
to the instance and runaminate
e.g.
sudo aminate -h
-
Enjoy Aminator
Asgard is available on the AWS Marketplace: https://aws.amazon.com/marketplace/pp/B00F46U3TS
There is also a video on getting it started: http://youtu.be/q2XZ-O_C0HY
Name: | Asgard-1.3.1-ubuntu-12.04-amd64-ebs-20130716-2158 |
---|---|
Architecture: | x86_64 (amd64) |
OS: | Ubuntu 12.04 precise |
us-east-1 (N. Virginia) | ami-8f4118e6 | Launch Asgard from the AWS Marketplace |
---|---|---|
us-west-1 (N. California) | ami-905761d5 | Launch Asgard from the AWS Marketplace |
us-west-2 (Oregon) | ami-6ebe265e | Launch Asgard from the AWS Marketplace |
eu-west-1 (Ireland) | ami-eb0ae99c | Launch Asgard from the AWS Marketplace |
sa-east-1 (San Paulo) | ami-1b9a3c06 | Launch Asgard from the AWS Marketplace |
ap-northeast-1 (Tokyo) | ami-91395c90 | Launch Asgard from the AWS Marketplace |
ap-southeast-1 (Singapore) | ami-8e4114dc | Launch Asgard from the AWS Marketplace |
ap-southeast-2 (Sydney) | ami-5b5bc761 | Launch Asgard from the AWS Marketplace |
Use Asgard 1.3.1 above.
-
Click Launch for your desired region (if you don't see the region you want, let me know)
-
Select an instance at least
m1.medium
or larger (Asgard likes RAM) -
During the wizard, create a new security group with the following rules
- Port 22: 0.0.0.0/0
- Port 80: your ip/32
-
Once launched, go to the public DNS for the instance and set up Asgard.
e.g. http://ec2-12-212-12-121.us-west-2.compute.amazonaws.com/
Note: It can take a few minutes for the URL to become available as Tomcat starts.
-
Enjoy Asgard
Name: | edda-2.1-answers4aws-ubuntu-12.04-amd64-ebs-20130913-2103 |
---|---|
Description: | Edda-2.1-answers4aws on Ubuntu 12.04 by AWS Answers |
Architecture: | x86_64 (amd64) |
OS: | Ubuntu 12.04 precise |
us-east-1 (N. Virginia) | ami-5d1d5534 | Launch |
---|---|---|
us-west-1 (N. California) | ami-06093c43 | Launch |
us-west-2 (Oregon) | ami-18ed7228 | Launch |
eu-west-1 (Ireland) | ami-1a48ad6d | Launch |
sa-east-1 (San Paulo) | ami-79a20564 | Launch |
ap-northeast-1 (Tokyo) | ami-a1bf23a0 | Launch |
ap-southeast-1 (Singapore) | ami-10abe042 | Launch |
ap-southeast-2 (Sydney) | ami-1f8b1625 | Launch |
Use the CloudFormation script to do all of the tedious stuff for you. The script is here and works in all regions:
https://github.com/Answers4AWS/netflixoss-ansible/blob/master/cloudformation/edda.json
-
Create an IAM Role called 'edda' with this policy
-
Click Launch for your desired region (if you don't see the region you want, let me know)
-
Select an instance at least
m1.medium
or larger -
During the wizard, remember to select the 'edda' role you created above. Also create a new security group with the following rules
- Port 22: 0.0.0.0/0
- Port 80: your ip/32
-
Once launched, go to the public DNS for the instance and make queries to it via HTTP. Example:
http://ec2-12-212-12-121.us-west-2.compute.amazonaws.com/edda/api/v2/view/instances;_pp
Note: It can take a few minutes for the URL to become available as Tomcat starts.
-
Enjoy Edda
Name: | eureka-1.1.98-awsanswers-ubuntu-12.04-amd64-ebs-20130716-2243 |
---|---|
Description: | Eureka-1.1.98-awsanswers on Ubuntu 12.04 by AWS Answers |
Architecture: | x86_64 (amd64) |
OS: | Ubuntu 12.04 precise |
us-east-1 | us-west-1 | us-west-2 | eu-west-1 |
---|---|---|---|
ami-f685fb9f Launch |
ami-a4052de1 Launch |
ami-7b30a34b Launch |
ami-922bcce5 Launch |
-
Click Launch for your desired region (if you don't see the region you want, let me know)
-
Select an instance type (not tested on
t1.micro
) -
During the wizard, create a new security group with the following rules
- Port 22: 0.0.0.0/0
- Port 80: your ip/32
-
Once launched, go to the public DNS for the instance.
e.g. http://ec2-12-212-12-121.us-west-2.compute.amazonaws.com/eureka/
Note: It can take a few minutes for the URL to become available as Tomcat starts.
-
Enjoy Eureka
Name: | simian-army-ubuntu.yml---x86_64-201309120428-ebs |
---|---|
Description: | name=simian-army-ubuntu.yml, arch=x86_64, ancestor_name=foundation-ubuntu-12.04-x86_64-ebs-20130814-0339, ancestor_id=ami-2cac311c, ancestor_version= |
Architecture: | x86_64 (amd64) |
OS: | Ubuntu 12.04 precise |
us-east-1 (N. Virginia) | ami-b386cfda | Launch |
---|---|---|
us-west-1 (N. California) | ami-ee1124ab | Launch |
us-west-2 (Oregon) | ami-e0cc53d0 | Launch |
eu-west-1 (Ireland) | ami-b819fccf | Launch |
sa-east-1 (San Paulo) | ami-bddc7ba0 | Launch |
ap-northeast-1 (Tokyo) | ami-a1fa66a0 | Launch |
ap-southeast-1 (Singapore) | ami-369ad164 | Launch |
ap-southeast-2 (Sydney) | ami-29910c13 | Launch |
Use the CloudFormation script to do all of the tedious stuff for you. The script is here:
You can find your own IP (to limit port 80 access) by doing a google search
-
Create an IAM Role called 'simian-army' with this policy
-
Click Launch for your desired region
-
Select any instance size, even
t1.micro
-
During the wizard, create a new security group with the following rules
- Port 22: 0.0.0.0/0
- Port 80: your-ip/32
-
Once launched, you can configure the Simian Army (sending email in particular) by editing the properties files in
/usr/local/tomcat/webapps/simianarmy/WEB-INF/classes/
and then restarting Tomcat by runningsudo service tomcat7 restart
-
Enjoy the Simian Army