Michael Bahr

✍️ blogs about AWS serverless on newsletter: Open for work:

[Michael Bahr @bahrdev]

@PavelTcholakov Cognito has relatively low usage quotas. I'd suggest familiarizing yourself with them to see if they'd break any use case: https://t.co/dorZhjD2al

[Michael Bahr @bahrdev]

@mattgillard Happy birthday!

[Michael Bahr @bahrdev]

@theburningmonk I have a small utility class that I'm copying around projects. Feels quite easy to use: https://t.co/CTp0J5GNUW

[Michael Bahr @bahrdev]

@readysetcloud

[Michael Bahr @bahrdev]

@jrmyhdgs Both are possible :)

[Michael Bahr @bahrdev]

🛠️ I'm available for hire again!

Are you looking for an engineer with a lot of #aws experience in #serverless backends, dependency automation, and operational excellence? Let's have a chat about the challenges you're working on!

CV is available on request.

[Michael Bahr @bahrdev]

@astuyve If you want to automate those PRs, let me know! I have some experience from automating dependency upgrades at Stedi.

[Michael Bahr @bahrdev]

@tlakomy 🥰

[Michael Bahr @bahrdev]

I'm looking for a company that is fully remote, and has the same compensation philosophy for everyone on the globe.

If you already have a job opening, feel free to share it here privately: https://t.co/Wp3W678UHL

[Michael Bahr @bahrdev]

@aisamu @tlakomy All the libraries then!

[Michael Bahr @bahrdev]

@tlakomy This is actually a good one, well done Tomasz!

[Michael Bahr @bahrdev]

@tlakomy Still better than Vercel's AI prompt box, which just sends you to a waitlist

[Michael Bahr @bahrdev]

@jeremy_daly @kleinmau

[Michael Bahr @bahrdev]

@GeorgeCadman same here, messaged their support

[Michael Bahr @bahrdev]

@__steele @erlendekern @AIDAN Me too! @AWS_Security What do you think about rejecting statements that contain fields that you won't validate? #wishlist

[Michael Bahr @bahrdev]

🚨 New Blog Post: Your OIDC Deployments From Public Repositories May Be At Risk

#GitHub #OIDC #CICD #AWS

https://t.co/NHL4hAJOMT

[Michael Bahr @bahrdev]

Leaving the "outside collaborators" setting at the default (require approval for first time contributors) actually works quite well. I've spun up a couple fully automated repositories since writing the article, and I feel confident about that approach.

[Michael Bahr @bahrdev]

I decided to revoke this article, because there are substantial errors.

If you already made changes based on this article, please read the messages below.

[Michael Bahr @bahrdev]

🚨 New Blog Post: Your OIDC Deployments From Public Repositories May Be At Risk

#GitHub #OIDC #CICD #AWS

https://t.co/NHL4hAJOMT

[Michael Bahr @bahrdev]

Read more at https://t.co/wEp0ms1TSZ.

[Michael Bahr @bahrdev]

@erlendekern @__steele @AIDAN Took me a bit, but I decided to revoke this article. Further testing showed me that the audience field is not verified, and that the default settings of GitHub are actually good enough. Thank you for correcting this! :)