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

Did you edit your state recently? There's a pointer in your state file to something that doesn't exist (or has been renamed).

I don't really understand the problem well. I deleted some manual stuff from aws console. After doing refresh with pulumi and there I got stuck with that problem

Ah that will be it. When Pulumi refreshed your SQS queue and determined that it had been deleted in AWS, it deleted it from the Pulumi state too. For some reason, this didn't delete the child EventSubscription resource (maybe it still exists?).

But the EventSubscription has a dependency on the now-missing queue.

To fix this, I _think_ you'll have to export your stack, remove the parent property of the EventSubscription, and import your edited stack.

IMO this is a bug: Pulumi should have cleared the parent property of the EventSubscription when it detected that it had been removed.

But, it's a tough call: in _code_, the EventSubscription still has the queue as its parent.

In general, don't manually edit or delete resources that are managed by Pulumi. This sort of thing happens.