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

The inputs are fine:

```pulumi.all([subnetIds.ids, taskDefinition.taskDefinition.arn, deadLetterQueue.arn])
    .apply(([subnetIds, taskDefinitionArn, deadLetterQueueArn]) =&gt; console.log([subnetIds, taskDefinitionArn, deadLetterQueueArn]))
console.log(securityGroupId)```
yields
```    sg-&lt;redacted&gt;
    [
      [ 'subnet-&lt;redacted&gt;', 'subnet-&lt;redacted&gt;' ],
      'arn:aws:ecs:us-east-2:&lt;redacted&gt;:task-definition/task-definition-&lt;redacted&gt;:3',
      'arn:aws:sqs:us-east-2:&lt;redacted&gt;:&lt;redacted&gt;'
    ]```

I believe the problem is the `arn` - that should point to the target ECS cluster.

There's an example in the TF docs that gets dropped by our conversion process for reasons we would need to investigate (and fix), but that's how I figured it out: <https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_event_target#example-ecs-run-task-with-role-and-task-override-usage|https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_event_target#example-ecs-run-task-w[…]and-task-override-usage>

Folks running into difficulties because of dropped examples in the docs is a common issue with our users and a current area of focus for us.

When you have a minute, please let me know if the solution worked for you.

```const eventRule = new aws.cloudwatch.EventRule("event-rule", {
    name: `${pulumi.getProject()}-event-rule`,
    description: genericDescription,
    eventBusName: "default",
    scheduleExpression: "cron(1 0 * * ? *)",
}, {provider: targetAwsProvider});```

Yes, the `eventTarget.d.ts` docs define `arn` as `ARN of the SQS queue specified as the target for the dead-letter queue.`

:white_check_mark: success! Updating the `arn` to the cluster arn allowed the resource creation to finish. Thank you <@U02FZC2RE0Y>