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

Hello! I was wondering if anyone has created an *ECS cluster* that is placed inside an *existing security group*. This is what I'm currently work with and it's complaining that I'm passing a string and not a *type of awsx.ec2.securityGroupOrId[]*
```const config = new pulumi.Config();
const existingSecurityGroup = config.require('existingSG');
const cluster = new awsx.ecs.Cluster(`app-${env}`, {
  securityGroups: [existingSecurityGroup],
  vpc: vpc,
  name: `app-${env}`
});```

I believe that a security group of string is a valid thing to pass for `SecurityGroupOrId`. 

Could you share the exact error?  Is that for the exact code above?

See also <https://pulumi.io/reference/pkg/nodejs/pulumi/awsx/ec2/#SecurityGroupOrId> which indicates that a string should be valid here. 

Hi Luke, thanks for the reply!
I figured out the issue... When I copied over my security group id into my pulumi config, I missed the last number. I put in the full security group id and it's working now!