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

You mean without the auto naming of the resource?

Like this?
```
new aws.elasticache.Cluster("cachecluster", {
    name: "cachecluster",
...
```

I don’t see name as a property. Didn’t try to see if it would still work though.

Seems like clusterId may be what I’m looking for, unfortunately it seems like AWS has really low restrictions on the name.

<@UGDSK5RNC> if that doesn’t work for you, can you open an issue on github under pulumi-aws and add me to the comment?

<@UGDSK5RNC> You are right, I was too quick...

Seems like some validation logic needs work on elasticache at least. `numCacheNodes` seems to be required, but isn’t being required during the preview. Not sure if there is anything else.

Yeah anything you feel should be different there, add it to that issue and I can get that fixed up