A couple of points to help evaluate the security implications of this:
* in-instance users are created by the use who originally created the stack
* an in-instance user can only call CreateStack and UpdateStack if the ec2 keypair for that user is known
* practically speaking, this can probably only be exploited if a stack-launched nova server is compromised, or if the heat->server communication containing the ec2 keypair is intercepted.
+2 for this patch.
A couple of points to help evaluate the security implications of this:
* in-instance users are created by the use who originally created the stack
* an in-instance user can only call CreateStack and UpdateStack if the ec2 keypair for that user is known
* practically speaking, this can probably only be exploited if a stack-launched nova server is compromised, or if the heat->server communication containing the ec2 keypair is intercepted.