Skip to content

[I Made This]: Build Serverless WebSockets with AWS AppSync Events and Powertools for AWS Lambda #6609

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

Closed
1 task done
ran-isenberg opened this issue May 5, 2025 · 1 comment · Fixed by #6610
Closed
1 task done
Assignees
Labels
community-content Community content to feature in the documentation

Comments

@ran-isenberg
Copy link
Contributor

Link to your material

https://www.ranthebuilder.cloud/post/aws-appsync-events-and-powertools-for-aws-lambda

Description

In this post, you'll learn how to build an AppSync Events API with AWS CDK, connect a Lambda event handler to a namespace, and process every publish and subscription event using Powertools for AWS Lambda.

Preferred contact

i'll open a PR

(Optional) Social Network

No response

(Optional) Additional notes

No response

Acknowledgment

  • I understand this content may be removed from Powertools for AWS Lambda (Python) documentation if it doesn't conform with the Code of Conduct
Copy link
Contributor

github-actions bot commented May 5, 2025

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments 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.

@leandrodamascena leandrodamascena moved this from Coming soon to Shipped in Powertools for AWS Lambda (Python) May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-content Community content to feature in the documentation
Projects
Status: Shipped
Development

Successfully merging a pull request may close this issue.

1 participant