Upgrading to VPC on AWS

Junien Fridrick junien.fridrick at canonical.com
Mon Oct 10 05:37:02 UTC 2016

On Mon, Oct 10, 2016 at 12:51:21AM +0000, Andrew Wilkins wrote:
> On Fri, Oct 7, 2016 at 11:31 PM Mark Shuttleworth <mark at ubuntu.com> wrote:
> > Hi folks
> >
> >
> >
> > My AWS account pre-dates VPCs, so I didn't have one by default. I've now
> >
> > added one, how can I update my credential / controller to make use of it
> >
> > by default?
> >
> At the moment the only way to use a non-default VPC is to specify it
> explicitly when bootstrapping or adding a model, using "--config
> vpc-id=vpc-xyz".
> [...]

Also, please note that only AWS Support can create a default VPC, and it
can only do so if the region doesn't have any EC2-Classic instance.

If you look at the VPC you created, it won't be considered a "default
VPC" by AWS.


"If you created your AWS account before December 4th, 2013, your account
may have never had a default VPC. For more information, see Differences
Between EC2-Classic and EC2-VPC. If you'd like a default VPC, or you'd
like to switch to the EC2-VPC platform, contact AWS Support."


More information about the Juju mailing list