The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
AI Content Automation on AWS | GitHub + Slack + Bedrock
Description:-
I built a production-grade AI content automation system that transforms GitHub commits and Slack conversations into authentic LinkedIn posts.
The solution uses AWS, Terraform, ECS Fargate, and EventBridge to automate content generation, approval, and scheduling.
- Automated content generation from GitHub and Slack activity
- Human-in-the-loop Slack approval workflow
- Security filtering to reduce sensitive data exposure
- Scheduled content publishing with EventBridge
- Production-ready AWS infrastructure managed with Terraform
The result is a reliable, scalable automation pipeline that eliminates repetitive content creation while maintaining human control over what gets published.
My Role: AWS DevOps Engineer
Technologies: AWS ECS · Fargate · Terraform · Docker · CI/CD · EventBridge · GitHub · Slack · AWS Bedrock
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
One architectural decision changed everything.
"We don't deploy into our own cloud."
Customers design their backend visually. Our platform generates the Terraform. It deploys straight into their cloud account — not ours.
That sentence sounds simple.
In practice it forced us to rethink five things:
• Terraform state architecture — one isolated state per service, not one shared state per customer
• Identity separation — every tenant runs on its own scoped credentials, sealed off from the rest
• Existing-resource adoption — customers already have infrastructure, so we import it instead of fighting it
• Parallel deployments — many resources at once, without stepping on each other
• Runtime vs infrastructure health — "did it deploy" and "is it healthy" are different questions
The hard part was never generating Terraform.
It was making a system safe enough that someone would point it at their production account.
I designed and built this end to end — the architecture, the Terraform generation, the deploy pipeline.
If your team is heading somewhere similar, or you're about to point automation at a customer's production account for the first time, happy to compare notes. 👋
AI News Digest
I built an automated AI News Digest with n8n that collects the latest AI & automation news from RSS sources, selects the most relevant items, summarizes them using Groq AI, and delivers a structured daily digest directly to Telegram.
The workflow runs automatically every day, eliminating the need to manually check multiple sources.
Built with n8n, RSS, Groq API, Telegram API, and JavaScript.
A simple example of how AI automation can turn information overload into a useful daily workflow.
Automating Orders with Telegram Bot
I recently built a workflow that automates order processing using a Telegram bot and Google Sheets. The tech stack includes n8n, Telegram, and Google Sheets. It's been a game saver, especially when dealing with a high volume of orders. I can now focus on more important tasks, like growing my business.
#n8n #automation #TelegramTrigger #IF
Follow for more: https://go.phonezait.de/
