when building a new host with the EC2 compute resource, when the security groups dialog is presented, the list is totally empty. This makes it impossible to select a security group from your host and forces a security risk, to work around being unable to select a security group, the default security group must be configured to allow foreman access on ssh and puppet or builds will fail, you then need to go into the AWS console and manually change the security group for the new host, which adds manual tasks to provisioning, and raises questions from support groups about the use of foreman.

this bug is in 1.9.3 and is present in my current test system build of 1.10-RC3

On occasion if you build the host, re-visit the host and click "edit" against the host, the security groups dialog will be populated, but this is very rare, and useless unless the above default security group compromise configuration has been implemented !