No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Reading the issue it looks like `security_groups` is a leftover from when VPCs weren't a thing, or you were able to have EC2 instances outside of a VPC. You should use `vpcSecurityGroupIds`

Experienced its consequence now; when I updated the SG rules, pulumi ended replacing the instance using the SG :scream:

Unfortunately, `vpcSecurityGroupIds`  doesn’t seem to work
```      File "./__main__.py", line 30, in &lt;module&gt;
        du = aws.ec2.Instance(
    TypeError: __init__() got an unexpected keyword argument 'vpcSecurityGroupIds'
    error: an unhandled error occurred: Program exited with non-zero exit code: 1```


Ah..found the right parameter in the doc; it’s `vpc_security_group_ids`