Skip to content
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

[I Made This]: Creating a serverless API using AWS Lambda Powertools and CDK #3595

Closed
1 task done
thomasgtaylor opened this issue Jan 5, 2024 · 6 comments · Fixed by #3605
Closed
1 task done

[I Made This]: Creating a serverless API using AWS Lambda Powertools and CDK #3595

thomasgtaylor opened this issue Jan 5, 2024 · 6 comments · Fixed by #3605
Assignees
Labels
community-content Community content to feature in the documentation

Comments

@thomasgtaylor
Copy link

thomasgtaylor commented Jan 5, 2024

Link to your material

https://how.wtf/creating-a-serverless-api-using-aws-lambda-powertools-and-cdk.html

Description

This article walks through the process of using the AWS CDK to deploy an L3 construct, LambdaRestApi, with a lambda proxy integration that leverages the AWS Powertools SDK end-to-end. Readers walk away with a CDK-deployable application.

Techniques include:

  • Leveraging SAR
  • Using L3 constructs
  • Explaining the Powertools
  • etc.

Preferred contact

Thomas Taylor

(Optional) Social Network

https://www.linkedin.com/in/iamthomastaylor/

(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
@thomasgtaylor thomasgtaylor added the community-content Community content to feature in the documentation label Jan 5, 2024
Copy link

boring-cyborg bot commented Jan 5, 2024

Thanks for opening your first issue here! We'll come back to you as soon as we can.
In the meantime, check out the #python channel on our Powertools for AWS Lambda Discord: Invite link

@leandrodamascena
Copy link
Contributor

Hi @iamthomastaylor! We're really happy when the community spends their time creating content using Powertools, this is what motivates us to work hard in this project!

I'll read the article tomorrow, make comments (if needed) and add it in our documentation!

Thanks ❤️

@leandrodamascena leandrodamascena self-assigned this Jan 9, 2024
@thomasgtaylor
Copy link
Author

Hey @leandrodamascena! I'm always happy to spread the word! For context, this blog gets around 13,000 monthly viewers - so hopefully it'll gain some well-deserved attention for Powertools!

Please let me know if something does not suffice!

@leandrodamascena
Copy link
Contributor

Hey @leandrodamascena! I'm always happy to spread the word! For context, this blog gets around 13,000 monthly viewers - so hopefully it'll gain some well-deserved attention for Powertools!

Wow, those are impressive numbers of viewers!!

Please let me know if something does not suffice!

Just a note and this is not mandatory, but we recently renamed the project from AWS Lambda Powertools to Powertools for AWS Lambda and it might be cool in this/future articles for you to use the new name!

Working now to open the PR to include this article!

Copy link
Contributor

github-actions bot commented Jan 9, 2024

⚠️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.

@github-actions github-actions bot added the pending-release Fix or implementation already in dev waiting to be released label Jan 9, 2024
Copy link
Contributor

This is now released under 2.32.0 version!

@github-actions github-actions bot removed the pending-release Fix or implementation already in dev waiting to be released label Jan 19, 2024
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
2 participants