hotswap: we don't support attributes of the 'AWS::SQS::Queue' resource. This is a CDK limitation.

[jpangburn]

Describe the feature

I'm using AWS Amplify Gen 2, and every time I update my lambda functions it does a full deployment. It blames CDK and requests it be reported here:

Could not perform a hotswap deployment, because the CloudFormation template could not be resolved: We don't support attributes of the 'AWS::SQS::Queue' resource. This is a CDK limitation. Please report it at https://github.com/aws/aws-cdk/issues/new/choose

Use Case

Everyone who is using Amplify Gen 2, and uses SQS queues in their backend.ts CDK definition is/will run into this. For example, I have a bit of CDK code like:

const accessLogsDLQ = new sqs.Queue(logNotificationStack, "AccessLogsDLQ", {
  retentionPeriod: Duration.days(7), // keep problematic events for 7 days
});

It's part of a queue definition for my lambda functions to write to. Because of this, every time I update a lambda function or change anything about my backend, it does a full deployment which takes a while. It's a pretty high impact to the development flow of Amplify Gen 2 if you need an SQS queue, which I imagine most serious projects will use at some point.

Proposed Solution

Maybe work with the Amplify team, find out who wrote this warning message into their code instead of submitting this bug/feature report themselves, and ask them what they need :-)

Other Information

For working on parts of the application that don't involve the queues, it's possible to comment all that out but this is likely to lead to unintended consequences in development and seems like a poor workaround.

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.147.0

Environment details (OS name and version, etc.)

Mac OS Sonoma 14.5

[pahud]

reaching out to Amplify team for clarifying

internal tracking: V1462555712

[jpangburn]

@pahud thanks for looking into this!

[pahud]

At this moment, CDK hotswap is only supported for those resources.

Making it a hotswap feature request for SQS Queue. Please help us prioritize with 👍

Adding hotswap label.