This message was deleted.

we've had another issue for this in the last 24 hours if I recall, could you open an issue at github.com/pulumi/pulumi-aws with a repro please

i didn't manage to reproduce it in any other environment other than the one i am working on. i also tried to increase the timeouts by setting

customTimeouts

property but it didn't help. The timeouts remain on 2m. what else can i do?

@best-train-86003 can you please add code to allow us to repro the issue

@billowy-army-68599 here is the code:

import * as aws from "@pulumi/aws";


const q = new aws.sqs.Queue('Experts-CS-dev-Experts-CSLambda20220404121254156400000016', {
    kmsDataKeyReusePeriodSeconds: 300,
    maxMessageSize: 10240,
    messageRetentionSeconds: 604800,
    namePrefix: 'Experts-CS-dev-Experts-CSLambda',
    policy: '{"Statement":[{"Action":["sqs:SendMessage"],"Condition":{"ArnEquals":{"aws:SourceArn":"arn:aws:sns:eu-west-1:225051786593:Experts-CS-dev-f8eba3f"}},"Effect":"Allow","Principal":{"Service":"<http://sns.amazonaws.com|sns.amazonaws.com>"},"Resource":"*"}]}',
    redrivePolicy: '{"deadLetterTargetArn":"arn:aws:sqs:eu-west-1:225051786593:Experts-CS-dev-Experts-CSLambda-dlq-8672972","maxReceiveCount":10}',
    tags: {
        costCenter: 'operations',
        org: 'cliotechweb',
        project: 'backend-stacks',
        stack: 'dev'
    },
    visibilityTimeoutSeconds: 30
})

exports.queueName = q.id;