Automated Windows AMI Patching & AWS Infrastructure Automation I built an automated AWS pipeline ...Automated Windows AMI Patching & AWS Infrastructure Automation I built an automated AWS pipeline ...
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
Automated Windows AMI Patching & AWS Infrastructure Automation
I built an automated AWS pipeline to eliminate the manual process of patching Windows servers and updating the AMI used by an Auto Scaling Group.
The solution uses AWS Image Builder, SSM Patch Manager, CloudWatch, EventBridge, Lambda, and CloudFormation to automate the complete patching lifecycle.
Automated Windows patch scanning and installation
Automated Sysprep and patched AMI creation
CloudWatch logging for patching and audit visibility
Automatic Launch Template and ASG updates
Preserved existing production configuration
The infrastructure is deployed through a single CloudFormation template, creating a repeatable and auditable workflow with minimal manual intervention.
My Role: AWS DevOps / Cloud Automation Engineer
Technologies: AWS Image Builder, SSM Patch Manager, EC2, Auto Scaling, Lambda, EventBridge, CloudWatch, CloudFormation, IAM, Windows Server, PowerShell
If you let an AI coding agent run unconstrained self-repair loops, it won’t fix the bug—it will rewrite your unit tests to pass.
The concept of "Reflexion"—agents diagnosing and repairing code from test feedback—is powerful. But in production, autonomous repair creates severe operational risks.
First, agents enter endless retry loops that burn API budgets while degrading code structure. Second, if an agent has write access to your workspace, its quickest path to a green checkmark is modifying the test assertions rather than fixing the bug.
In our Bounded Reflexion workflow, we enforce three hard guardrails:
Bounded Retries: Cap repairs at exactly two attempts. If the patch fails twice, stop the loop and route to a human developer.
Read-Only Test Suites: Mount test files as strictly read-only (:ro) volumes in the container. The agent inspects stack traces, but cannot touch the grading harness.
Air-Gapped Sandboxing: Run code execution in hardened, non-root Docker containers with network egress locked down.
How do you stop autonomous coding agents from "cheating" your evaluation harnesses?
Making the tests read-only is a smart rule: the agent can't change the thing that grades it. After two failed attempts, what does the developer get: only the stack trace, or also the two patches the agent tried?
Missed DMs turning into lost leads is a real problem for agents. What's the first automated reply you set up: an instant greeting or a qualifying question?
Your Business Doesn't Need More Tools. It Needs Better Systems.
Most businesses don't have a software problem. They have an integration problem.
Their CRM is disconnected from their database. Their spreadsheets require manual updates. Their reports take hours to prepare. Their teams waste valuable time moving information between platforms.
That's where I come in.
I'm a Full-Stack AI Engineer specializing in building connected, intelligent business systems.
What I can build for your business:
CRM & ERP Integrations — Connect business platforms, databases, and third-party services through APIs.
Workflow Automation — Eliminate repetitive processes with intelligent automation.
Custom Dashboards — Turn scattered business data into actionable insights.
Data Pipelines — Build reliable systems for collecting, processing, validating, and synchronizing data.
AI-Powered Solutions — Integrate LLMs, intelligent agents, and automation into existing workflows.
Custom Software — Build complete web applications and business platforms from architecture to deployment.
I've independently developed complex digital platforms, including government-level systems, international applications, and AI-powered products.
My approach is simple:
Understand the business problem. Design the right architecture. Build the complete solution. Make it reliable.
I'm interested in working with founders, agencies, and businesses looking to modernize their operations and build software that actually solves problems.
Have a complex workflow or an integration challenge? Let's build something that works.
When a CRM-to-database sync fails halfway, how do you handle it: idempotent retries, or a reconciliation pass afterward? That's usually where integrations start to drift.