The Amazon EC2 cloud and Juju

List of supported clouds > Amazon EC2

This document describes details specific to using your existing Amazon EC2 cloud with Juju.

See more: Amazon EC2

When using the Amazon EC2 cloud with Juju, it is important to keep in mind that it is a (1) machine cloud and (2) not some other cloud.

See more: Cloud differences in Juju

As the differences related to (1) are already documented generically in our Tutorial, How-to guides, and Reference docs, here we record just those that follow from (2).

Juju points of variation Notes for the Amazon EC2 cloud
setup (chronological order):
CLOUD
requirements: TBA
definition: Already known to Juju. Run juju clouds --all to confirm. (Pre-defined cloud name in Juju: aws.)
CREDENTIAL
definition: auth-type: access-key, which requires you to provide your access key and your secret key.
> See more: Amazon | AWS security credentials

If you want to use a YAML file:

credentials:
 aws:
  <user-defined credential name>:
   auth-type: access-key
   access-key: <key>
   secret-key: <key>

If you want to use environment variables:

AWS_ACCESS_KEY_ID="<id>"

AWS_SECRET_KEY_ID="<id>"
CONTROLLER
notes on bootstrap: –
other (alphabetical order:)
CONFIGURATION (model)
cloud-specific: vpc-id (string)
Sets a specific AWS VPC ID. Optional. When not specified, Juju requires a default VPC or EC2-Classic features to be available for the account/region. :warning: If your AWS account was created before 04-12-2013: Your account does not have a default VPC. As a result, Juju may select a much larger instance type than what is required. To remedy this, create a default VPC.

vpc-id-force (boolean)
Forces Juju to use the AWS VPC ID specified with vpc-id, when it fails the minimum validation criteria. :warning: Not accepted without vpc-id.
CONSTRAINT
conflicting: [instance-type] vs. [cores, cpu-power, mem]
allocate-public-id :white_check_mark:
arch :white_check_mark:
container :white_check_mark:
cores :white_check_mark:
cpu-power :white_check_mark:
instance-role :white_check_mark:
instance-type :white_check_mark:
Valid values: See cloud provider.
Default value: m3.medium.
mem :white_check_mark:
root-disk :white_check_mark:
root-disk-source :white_check_mark:
spaces :white_check_mark:
tags :negative_squared_cross_mark:
virt-type :negative_squared_cross_mark:
zones :white_check_mark:
PLACEMENT DIRECTIVE
<machine> :white_check_mark:
subnet=... :white_check_mark:
system-id=... :negative_squared_cross_mark:
zone=... :white_check_mark:
If the query looks like a CIDR, then this will match subnets with the same CIDR. If it follows the syntax of a “subnet-XXXX”, this will match the Subnet ID. Everything else is just matched as a Name.
RESOURCE (cloud)

Consistent naming, tagging, and the ability to add user-controlled tags to created instances.

 :white_check_mark:

Last updated a month ago.

Help improve this document in the forum.