Default AWS instance-type t3.micro too small

[jamesbeedy]

@rick_h

James is this in 2.5? I know we setup guards to make sure instance sizes stayed consistent with the new instance types in 2.3/2.4 but we are planning to evaluate if we should be adjusting these defaults before 2.5 goes final now that there’s a new array of instance types available. The baked in constraints have always been 1gb of ram but there wasn’t an instance that matched that so historically folks got 2. Personally I think that 2gb seems a reasonable default but I wanted to double check other clouds and see what the cost/etc would be.

@rick_h 2.4.4

To replicate, juju deploy cs:~omnivector/bundle/elk-0 on an AWS model running 2.4.4.

I think its the controller version that matters, not the model. I can switch to models that haven’t been upgraded to 2.4.4 yet and deploy something without constraints and get a t3.micro. I’ll try with an older controller.