ploy_ec2 is best installed with easy_install, pip or with zc.recipe.egg in a buildout.
To use ploy_ec2 you need an Amazon account and AWS keys.
Once you got your keys, you should put them in a secure location and reference them in your
Additionally you need to set the region of the master:
[ec2-master:ec2eu] access-key-id = ~/.aws/ec2.id secret-access-key = ~/.aws/ec2.key region = eu-west-1
You can also set the
AWS_SECRET_ACCESS_KEY environment variables instead.
You need to define a master for each region you want to use.
Each instance has the following mandatory settings:
- The Amazon Machine Image (AMI) that this instance will start up with.
- The name of the SSH keypair to use.
- The availability zone in which to launch the instances.
- The name of the Securitygroups this instance should be assigned to.
The following settings are optional:
- Path to a script which will be run right after creation and first start of the instance. This uses the User Data feature and needs to be supported by the AMI.
[ec2-securitygroup:app-server] description = The production server connections = tcp 22 22 0.0.0.0/0 tcp 80 80 0.0.0.0/0
You can define volumes via
The id of the section must not start with
You can declare the
size as a number of GB.
If the volume doesn’t exist, it is automatically created.
[ec2-volume:a-volume-name] size = 100 [ec2-instance:foo] ... volumes = a-volume-name /dev/sdf
For instances the
volumes options aren’t copied when expanding macros.
Automatic ssh fingerprint verification works by checking whether the fingerprint is in the console output of the instance.
After reboot or stop/start of an instance, the console output is refreshed.
The problem with that is, that the fingerprint isn’t included in the console anymore by default.
To fix that you need to log the fingerprint on reboot somehow.
One way to do that with Ubuntu is to add a script at
/var/lib/cloud/scripts/per-boot/ssh-keys with this content:
#!/bin/sh /usr/bin/ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub
Make sure that script is executable.