AWS Free tier accounts require specifying micro instance type

Bug #1618973 reported by Nicholas Skaggs
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

AWS Free Tier accounts are limited to t2.micro instances. As juju itself will default to medium instance types, a new user trying out juju using an AWS free tier account will fail to bootstrap, and instead return the following message:

"ERROR failed to bootstrap model: cannot start bootstrap instance: cannot run instances: Your account is currently being verified. Verification normally takes less than 2 hours. Until your account is verified, you may not be able to launch additional instances or create additional volumes. If you are still receiving this message after more than 2 hours, please let us know by writing to <email address hidden>. We appreciate your patience. (PendingVerification)"

The message displayed is incorrect in this case as the verification isn't the issue. Rather it's the idea the account cannot use any other instance type besides t2.micro as juju is presumably asking aws for medium.

Can we support these free tier accounts that are limited to specific instance types? It would be useful to default to t2.micro for these accounts. The concern with using micro instances is charm compatibility -- perhaps juju could warn about this when it switches the default because of the limited account.

I was able to bootstrap after receiving the above message by running

juju bootstrap aws aws --constraints 'instance-type=t2.micro'

summary: - AWS Free tier accounts require launching with a constraint
+ AWS Free tier accounts require specifying micro instance type
tags: added: ec2-provider usability
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0.0
Changed in juju:
assignee: nobody → Richard Harding (rharding)
Changed in juju:
milestone: 2.0.0 → 2.1.0
Changed in juju:
assignee: Richard Harding (rharding) → nobody
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Removing 2.1 milestone as we will not be addressing this issue in 2.1.

Changed in juju:
milestone: 2.1.0 → none
tags: added: adoption
Revision history for this message
Tim McNamara (tim-clicks) wrote :

I've added some documentation around this:

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers