> Markdown version of [/jobs/ext/186383-aws-cloud-engineering-ops-lead-application-support](https://www.wearedevelopers.com/jobs/ext/186383-aws-cloud-engineering-ops-lead-application-support). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # AWS Cloud Engineering Ops Lead (Application Support) - **Company:** CONGLOMERATE IT LLC - **Location:** Atlanta, GA, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Amazon Web Services, Amazon Cloudfront, Amazon Elastic Compute Cloud, Backup Devices, Identity and Access Management, Python (Programming Language), OpenID, Ansible, Data Logging, Cloud-native Network Functions (CNF), Mttr, Amazon Virtual Private Cloud (VPC), Terraform - **Published:** May 13, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=04d198b7fc0682f5 ## About the Role Do you have experience in Terraform?, * 8-10+ years in cloud/app operations with strong AWS hands-on experience. * Comfortable leading incidents, shaping dashboards and alerts, and automating the boring bits (Terraform, Ansible, Python). * Experience running backups/DR in AWS and proving it with real restore tests. * Cloud network experience. Preferred Experience * AWS Solution Architect Certification * Any professional networking certifications * ITIL Certification ## Description * AWS operations: EC2, EKS, RDS, ALB/CloudFront, IAM/OIDC, VPC/TGW/SGs, patching, and hygiene. * Application support: release readiness, runbooks, post-deploy smoke checks, performance baselines, and clean rollback paths. * Visibility: dashboards, logs, metrics, traces, synthetics, error budgets, and alert health. * Backup & DR: policies, schedules, retention, cross-region copies, restore testing, and DR runbooks (RPO/RTO owned and measured). * Incident leadership: run Sev-1/2 bridges, keep comms clear, and land post-mortems with actions that actually close. * Cost hygiene: tagging, right-sizing, SP/RI coverage, lifecycle cleanups (EBS/EIP/AMIs). * Team enablement: guardrails, golden runbooks, and small automations that remove toil. Day-to-day (what this looks like) * Triage overnight alerts and hot issues, set priorities, and make sure owners are clear. * Keep dashboards honest; fix flapping or missing alerts before they wake people up. * Check backups and recent restore points; open tickets for any gaps and track to done. * Unblock releases; verify smoke checks; keep environments tidy and predictable. * Lead or delegate break/fix; no lingering "mystery" incidents. * Write down what we learned in the runbook so the next person can fix it faster. Weekly rhythm * Ops review: incidents, alerts, deploys, costs, capacity, and backup status in one short readout. * Observability tune-up: delete noise, add the missing signal, and test a synthetic from the edge. * Backup/DR: run a small restore test and record RPO/RTO evidence. * Patch and change review: what shipped, what rolled back, why. Monthly outcomes * Share availability/SLOs, MTTR, change failure rate, observability coverage, backup compliance, and costs in plain English. * Close the top recurring issues (noisy alerts, flaky deploys). * Refresh the most-used runbooks; validate DR for one critical workload (tabletop or live restore). Core responsibilities * Own production readiness and stability for assigned AWS accounts and apps. * Lead incidents and land post-mortems; make the fixes stick. * Keep monitoring/logging/tracing standards real; enforce SLOs and error budgets. * Own backup strategy end-to-end, including monthly restore tests and DR docs. * Keep access least-privileged and auditable; rotate secrets and certs on time. * Drive cost posture and mentor the team; make on-call humane. What "good" looks like * Visibility: one clear dashboard per service, clean alert routing, low false positives. * Backups: 100% jobs green (or retried), documented RPO/RTO, and monthly restore tests that pass. * Reliability: MTTR trending down; most issues solved by the first responder with a runbook. * Change: predictable releases with smoke and rollback; fewer failed changes month over month. * Cost: flat or down against growth; tagging at or above 95%. ## Related Videos - [Dev & Test in the Cloud? Deploy your cloud environments with Ansible & Terraform](https://www.wearedevelopers.com/videos/1607-dev-test-in-the-cloud-deploy-your-cloud-environments-with-ansible-terraform) - [What Developers Get Wrong About Application Quality](https://www.wearedevelopers.com/videos/233-what-developers-get-wrong-about-application-quality) - [Keeping applications secure by evolving OAuth 2.0 and OpenID Connect](https://www.wearedevelopers.com/videos/100152-keeping-applications-secure-by-evolving-oauth-2-0-and-openid-connect) - [We adopted DevOps and are Cloud-native, Now What?](https://www.wearedevelopers.com/videos/485-we-adopted-devops-and-are-cloud-native-now-what) - [Terraform for Developers](https://www.wearedevelopers.com/videos/3-terraform-for-developers) - [Embracing the Hybrid Cloud: Unlocking Success with Ansible](https://www.wearedevelopers.com/videos/932-embracing-the-hybrid-cloud-unlocking-success-with-ansible) ## Related Articles - [What Are The Top Skills Required For Azure Developers?](https://www.wearedevelopers.com/magazine/77-what-are-the-top-skills-required-for-azure-developers) - [7 Cloud Computing Trends Coming in 2025 for Developers](https://www.wearedevelopers.com/magazine/412-7-cloud-computing-trends-coming-in-2025-for-developers) - [Best US AI Conferences for CTOs in 2026: Build vs. Buy, Vendor Evaluation, and Peer Intelligence](https://www.wearedevelopers.com/magazine/736-best-us-ai-conferences-for-ctos-in-2026-build-vs-buy-vendor-evaluation-and-peer-intelligence) - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [Best Paying Jobs in Technology](https://www.wearedevelopers.com/magazine/256-best-paying-jobs-in-technology) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)