Juju already has knowledge of the AWS cloud, so unlike previous versions there is no need to provide a specific configuration for it, it 'just works'. AWS will appear in the list of known clouds when you issue the command:
And you can see more specific information (e.g. the supported regions) by running:
juju show-cloud aws
If at any point you believe Juju's information is out of date (e.g. Amazon just announced support for a new region), you can update Juju's public cloud data by running:
In order to access AWS, you will need to add some credentials for Juju to use. These can easily be set by either:
If you already use your AWS account with other tools, you may find that the
already set. Note that the the additional fallback environment variables
AWS_SECRET_KEY are also supported.
These can easily be imported into Juju. Run the command:
This will scan known locations and environment variables for cloud credentials and ask which ones to use/what name to store them under.
You can retrieve the values for the Access key and Secret Key easily from your AWS Management Console at http://console.aws.amazon.com. Click on your name in the top-right and then the "Security Credentials" link from the drop down menu.
Under the "Access Keys" heading click the "Create New Root Key" button. You will be prompted to "Download Key File" which by default is named rootkey.csv. Open this file to get the access-key and secret-key.
Armed with these values, you can then use the interactive command line tool to add them to Juju:
juju add-credential aws
Alternately, you can also use this credential with Juju as a Service and create and deploy your model using its GUI.
Place the AWS information in a
~/.aws/credentials file, or
%USERPROFILE%/.aws/credentials on Windows. The file will contain YAML
See Cloud credentials for more about adding credentials from a YAML file.
To create the controller for AWS, you then need to run:
juju bootstrap aws mycloud
Features supported by Juju-owned instances running within AWS: