-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
apigatewayv2-integrations: Add support for SQS-SendMessage integration #24785
Comments
Yes this would be awesome! We'd be glad to review your PR when it is ready. Thank you. |
@pahud , I just realized there are more than a single SQS integration type: Should we:
|
Hi @DaWyz This will need discussion with the core team maintainers, I would suggest you create a PR draft and describe your API design in the description and discuss with the maintainer in the PR draft before you finalize it. |
In case it helps give a start, here's how I did it for the SendMessage: Usage:
Extended class:
|
Thank you for sharing your implementation @benm5678! I haven't seen anyone else have this |
@clutteralx This might be because, in my experience, the MessageAttributes cannot be an empty string. Try removing the mapping entirely if there is no value. |
That was the issue. It works perfectly now. Thanks so much 🎉 |
Is this on any roadmap? It would be nice to have CDK support for stuff you can do in the console |
Comments on closed issues and PRs are hard for our team to see. |
1 similar comment
Comments on closed issues and PRs are hard for our team to see. |
Describe the feature
ApiGatewayv2 HTTP API integrates with SQS to redirect the request into a queue. It would be nice to have CDK implement this. See documentation on
SQS-SendMessage
mapping.Use Case
I want an easy way to use an SQS Queue as a proxy for my HTTP API.
Proposed Solution
Implement the construct similarly to the lambda integration.
It would look like the following:
Other Information
No response
Acknowledgements
CDK version used
2.70.0
Environment details (OS name and version, etc.)
Ubuntu 20
The text was updated successfully, but these errors were encountered: