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

Not at all! `awsx` is a higher-level abstraction library that provides a convenient, opinionated way on using `aws`

Thanks <@UTH0AMTQQ> This much I’ve understood. What I’m asking is how can I have all 3 of lifecyclePolicy, imageScanningConfiguration and imageTagMutablility when choosing either library. Or how can I use both for defining a single resource?

You have a couple options here. You can wire this up in `aws` and if you did that, then you’d use `Repository` for the scanning and tag immutability along with the `LifecyclePolicy` resource to handle the lifecycle part (<https://www.pulumi.com/docs/reference/pkg/aws/ecr/>)

Alternatively, if you wanted to use `awsx`, you can pass a `transformation`  (<https://www.pulumi.com/docs/intro/concepts/programming-model/#transformations>) to the `awsx.Repository` to modify the underlying `aws.Repository` resource to include the `imageScanningConfiguration` and `imageTagImmutability` properties.