CDK Hotswap Feature : AWS::SQS::Queue Attribute Support

[naedx]

Describe the bug

A project with the L3 construct LambdaToSqsToLambda falls back to full deployments everytime because of the SQS Queue

Expected Behavior

A hotswap is perfomed.

Current Behavior

A full deployment is performed.

amplify-xxxx-xxxx-sandbox-xxxx: deploying... [1/1]
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
Falling back to doing a full deployment
amplify-xxxx-xxxx-sandbox-xxxx: updating stack...

Reproduction Steps

1. Create an Amplify project
2. Add the L3 construct LambdaToSqsToLambda
3. Deploy.

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.147.0 (build 3338fc0)

Framework Version

No response

Node.js Version

20.9.0

OS

macOS 14.5, arm64

Language

TypeScript

Language Version

5.5.2

Other information

No response

[khushail]

Hey @naedx , thanks for reaching out. Could you please check if your issue is similar to this existing one -
#23533 and several others mentioned under it ?

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[naedx]

I'll take a look at it and let you know shortly

[naedx]

Hi @khushail , I think it's related. From the thread I gathered that the cross stack references are linked to the issue occuring.

My SQS references a lambda which references a stack with S3 resources and another lambda which references a stack with AppSync/DynamoDb resources. The lambdas are declared in the stack of the resources that they reference.

I tried removing the references between the lambda and the S3 and AppSync/DynamoDB resources. Hotswap still doesn't work.

I then moved the SQS and both lambdas to the same stack and this allows hotswap to work again.

This sheds some light on the issue but it's not a workable solution for me because I cannot re-add access to my S3, AppSync/DynamoDB resources without running into a circular dependency issues.

[naedx]

Thank you @khushail . I'll continue following up on the thread you referenced.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[aws-cdk-automation]

Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one.