<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Bedrock - Tag - AWS Sensei</title><link>https://aws-sensei.cloud/tags/bedrock/</link><description>Bedrock - Tag - AWS Sensei</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 26 May 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://aws-sensei.cloud/tags/bedrock/" rel="self" type="application/rss+xml"/><item><title>Automated LinkedIn Posts with AWS Lambda and Bedrock — An Approval-First Approach</title><link>https://aws-sensei.cloud/posts/2026-05-26-automated-linkedin-posts-aws-bedrock/</link><pubDate>Tue, 26 May 2026 00:00:00 +0200</pubDate><author>Marcel</author><guid>https://aws-sensei.cloud/posts/2026-05-26-automated-linkedin-posts-aws-bedrock/</guid><description>🔊 Voiced by Amazon Polly
Writing blog posts is one thing. Getting people to actually read them is another. LinkedIn is an obvious channel — but if you&amp;rsquo;re going to automate, do it properly from the start. So I built a pipeline that automatically turns new articles into LinkedIn post drafts — with an approval step built in, because AI-generated text going straight to production without review is not something I&amp;rsquo;m comfortable with.</description></item></channel></rss>