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

<@U018WCG42MN>,
There is a breaking change according to this <https://github.com/pulumi/pulumi-aws/blob/master/CHANGELOG.md#400-2021-04-19|changelog>.
• `aws.elasticache.Cluster` now only allows a single `snapshotArn`.
There is an issue open for this <https://github.com/pulumi/pulumi/issues/6943|here>

<@U019AM8NP1A> point is that I do not need any snapshot.

can I not simply not passing anything since it is an optional parameter?

```  return new aws.elasticache.Cluster('data-feed-control', {
    clusterId: 'data-feed-control',
    engine: 'redis',
    engineVersion: '6.x',
    nodeType: 'cache.t3.micro',
    numCacheNodes: 1,
    parameterGroupName: 'default.redis6.x',
    securityGroupIds: [defaultSecurityGroup.id],
    subnetGroupName: feedControlSubnetGroup.id
  })```

even if I copy the one in the docs, fails with the same error

There is a work around <https://github.com/pulumi/pulumi-aws/issues/1458#issuecomment-825333911|here>

I have manually removed the existing redis instance from aws console

and now I cannot do pulumi up anymore since it is trying to update something that does not exists anymore

I tried to export the stack and remove it manually, but it is in 16 different entries and I don't think that is the right way to do it

what is the right approach for this case?

You can use <https://www.pulumi.com/docs/reference/cli/pulumi_state_delete/|pulumi state delete> to remove it from the state file that you exported.  Then if you import the state file, and do a `pulumi up` what happens?

```  aws:iam:RolePolicyAttachment (iamrpa-data-feed-lambda-role-lambda-access-policy):
    error: 1 error occurred:
        * Error attaching policy arn:aws:iam::aws:policy/AWSLambdaFullAccess to IAM Role iamr-data-feed-lambda-71c3895: NoSuchEntity: Policy arn:aws:iam::aws:policy/AWSLambdaFullAccess does not exist or is not attachable.
        status code: 404, request id: a306fb38-152c-40a4-a922-d44802d8e8d4```

I know that AWSLambdaFullAccess is now deprecated and no longer attachable