Constraint allocate-public-ip is not recognized on AWS
Bug #2060103 reported by
Diko Parvanov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Alastair Flynn |
Bug Description
Trying to bootstrap on AWS EC2 with --constraints allocate-
juju bootstrap --constraints allocate-
Creating Juju controller "aws-us-east-1" on aws/us-east-1
WARNING unsupported constraints: allocate-public-ip
According to https:/
The constraint is explicitly marked in the EC2 logic as unsupported, but we should support it.
This might be simple.
We construct an instance of ec2.RunInstance sInput to pass to runInstances.
This has a member NetworkInterfaces, which is a slice of InstanceNetwork InterfaceSpecif ication. We do not populate this.
That type has a member AssociatePublic IpAddress. If it is as simple as populating this and otherwise relying on defaults, we're good. If we have to fully construct it once opted in, maybe a little harder.