# DevOps

DevOps is a combination of cultural philosophies, practices, and tools for delivering applications and services through collaboration between development and operations teams.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## This Month in AWS DevOps Agent: November 2026

DevFeed: [This Month in AWS DevOps Agent: November 2026](<https://devfeed.tech/articles/this-month-in-aws-devops-agent-november-2026-146990.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/this-month-in-aws-devops-agent-november-2026/>)

Author: Nereida Woo

Published: 2026-11-21T01:47:57Z

Content type: release

Language: en

Sources: [AWS Cloud Operations Blog](<https://devfeed.tech/sources/aws-cloud-operations-blog.md>)

Topics: [DevOps](<https://devfeed.tech/topics/devops.md>), [DevAIOps](<https://devfeed.tech/topics/devaiops.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>)

Tags: [agent-sandbox](<https://devfeed.tech/tags/agent-sandbox.md>), [amazon-bedrock-guardrails](<https://devfeed.tech/tags/amazon-bedrock-guardrails.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-govcloud-us](<https://devfeed.tech/tags/aws-govcloud-us.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [faster](<https://devfeed.tech/tags/faster.md>), [november-2026](<https://devfeed.tech/tags/november-2026.md>), [post-types](<https://devfeed.tech/tags/post-types.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [reviews](<https://devfeed.tech/tags/reviews.md>)

### AI overview

November updates extend AWS DevOps Agent to AWS GovCloud (US-West) and let teams associate an Agent Space with an organizational unit or organization root; organization mode is unavailable in GovCloud, and GovCloud omits some features, including Sandbox and private connections. Investigations now finish faster and stream summaries, while Sandbox (preview) runs code in an isolated environment scoped to one investigation or conversation, with read-only AWS calls and restricted network access. Teams can replay investigations to compare configuration changes, receive sampled automatic quality Reviews, and track nine CloudWatch metrics. Memory additions include importing custom knowledge, semantic search, linked memories, and weekly reviews that can remove stale claims, merge duplicates, or resolve contradictions with recorded evidence and version history. The agent also adds partner-hosted MCP connectors, a skills catalog, chat in Slack, Teams, and MCP clients, and code change risk analysis in preview. Availability and capabilities vary by Region; partner connector requests may leave the Agent Space's AWS Region.

### Source excerpt

Introduction November brought AWS DevOps Agent to AWS GovCloud (US-West) and added AWS Organizations support, so teams can connect an entire organizational unit to an Agent Space instead of one account at a time. Investigations now complete faster and show a real-time summary as they run. Replay and automatic Reviews give teams a way to [...]

## How Dynatrace and AWS create shared context for AI-powered operations

DevFeed: [How Dynatrace and AWS create shared context for AI-powered operations](<https://devfeed.tech/articles/how-dynatrace-and-aws-create-shared-context-for-ai-powered-operations-146204.md>)

Original publisher: [Read original article](<https://www.dynatrace.com/news/blog/how-dynatrace-and-aws-create-shared-context-for-ai-powered-operations/>)

Author: Erick Leon

Published: 2026-11-19T21:18:34Z

Content type: release

Language: en

Sources: [Dynatrace news](<https://devfeed.tech/sources/dynatrace-news.md>)

Topics: [dynatrace](<https://devfeed.tech/topics/dynatrace.md>), [AI-Ready Data](<https://devfeed.tech/topics/ai-ready-data.md>), [DevOps](<https://devfeed.tech/topics/devops.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-integration](<https://devfeed.tech/tags/agent-integration.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [ai-ready-data](<https://devfeed.tech/tags/ai-ready-data.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-re-invent](<https://devfeed.tech/tags/aws-re-invent.md>), [context](<https://devfeed.tech/tags/context.md>), [data](<https://devfeed.tech/tags/data.md>), [data-competency](<https://devfeed.tech/tags/data-competency.md>), [dynatrace](<https://devfeed.tech/tags/dynatrace.md>), [operations](<https://devfeed.tech/tags/operations.md>), [partners](<https://devfeed.tech/tags/partners.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

Dynatrace says its AWS Data Competency recognizes its expertise in connecting AWS telemetry with the runtime topology and production evidence used to operate AI workloads. It describes ingesting AWS signals through the Clouds App into Grail for analysis alongside service relationships, and extending observability to AI workloads and agentic workflows, including Amazon Bedrock AgentCore. Operational integrations put that context to work: Kiro Agent can use vulnerability signals to propose fixes, open pull requests, and verify remediation; AWS DevOps Agent uses Dynatrace context in incident investigations; and the SRE Agent can create root-cause analyses, with human approval where needed. Dynatrace reports joint users have seen up to a 70% reduction in MTTR. The text presents the AWS competencies as third-party validation and frames human oversight as part of the move toward autonomous operations.

### Source excerpt

We're pleased to announce that Dynatrace has achieved the AWS Data Competency, recognizing our expertise in building unified, AI-ready data foundations on AWS. Building and scaling on AWS means managing a vast, continuous stream of cloud telemetry and putting that data to work to drive better and faster outcomes. AI workloads need trustworthy runtime data, [...] The post How Dynatrace and AWS create shared context for AI-powered operations appeared first on Dynatrace news.

## Enterprise Live Migrations from Azure DevOps generally available

DevFeed: [Enterprise Live Migrations from Azure DevOps generally available](<https://devfeed.tech/articles/enterprise-live-migrations-from-azure-devops-generally-available-144209.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-19-enterprise-live-migrations-from-azure-devops-generally-available>)

Author: Allison

Published: 2026-11-19T18:50:57Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Azure DevOps](<https://devfeed.tech/topics/azure-devops.md>), [DevOps](<https://devfeed.tech/topics/devops.md>)

Tags: [azure](<https://devfeed.tech/tags/azure.md>), [azure-devops](<https://devfeed.tech/tags/azure-devops.md>), [azure-pipelines](<https://devfeed.tech/tags/azure-pipelines.md>), [branch](<https://devfeed.tech/tags/branch.md>), [cli](<https://devfeed.tech/tags/cli.md>), [data-residency](<https://devfeed.tech/tags/data-residency.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-management-tools](<https://devfeed.tech/tags/enterprise-management-tools.md>), [git](<https://devfeed.tech/tags/git.md>), [github](<https://devfeed.tech/tags/github.md>), [github-enterprise](<https://devfeed.tech/tags/github-enterprise.md>), [github-enterprise-cloud](<https://devfeed.tech/tags/github-enterprise-cloud.md>), [history](<https://devfeed.tech/tags/history.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [migration](<https://devfeed.tech/tags/migration.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [release](<https://devfeed.tech/tags/release.md>), [repositories](<https://devfeed.tech/tags/repositories.md>)

### AI overview

Enterprise Live Migrations (ELM) is generally available for moving repositories from Azure DevOps Services to GitHub Enterprise Cloud with data residency while teams continue working. Migrations can be managed through a guided Azure DevOps portal flow or scripted with the Azure DevOps CLI; pre-migration validation and lifecycle tracking help surface issues and monitor progress. ELM continuously syncs changes until a brief, team-scheduled cutover. It carries over Git history, branches, tags, pull requests and their associated details, and converts Azure DevOps branch policies to GitHub branch rulesets. ELM can also create the Azure Boards connection and rewire Azure Pipelines to the migrated repository; work items and pipeline definitions remain in Azure DevOps.

### Source excerpt

Enterprise Live Migrations (ELM) from Azure DevOps Services to GitHub Enterprise Cloud with data residency is now generally available. You can move your repositories while your teams keep working, then... The post Enterprise Live Migrations from Azure DevOps generally available appeared first on The GitHub Blog.

## Reducing database incident MTTR by 73% with a custom AWS DevOps Agent Skill

DevFeed: [Reducing database incident MTTR by 73% with a custom AWS DevOps Agent Skill](<https://devfeed.tech/articles/reducing-database-incident-mttr-by-73-with-a-custom-aws-devops-agent-skill-139360.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/reducing-database-incident-mttr-by-73-with-a-custom-aws-devops-agent-skill/>)

Author: Chetan Suri

Published: 2026-11-17T22:27:48Z

Content type: tutorial

Language: en

Sources: [AWS DevOps & Developer Productivity Blog](<https://devfeed.tech/sources/aws-devops-developer-productivity-blog.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>)

Tags: [agent-skill](<https://devfeed.tech/tags/agent-skill.md>), [aws](<https://devfeed.tech/tags/aws.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [database](<https://devfeed.tech/tags/database.md>), [decision](<https://devfeed.tech/tags/decision.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [mttr](<https://devfeed.tech/tags/mttr.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [reduction](<https://devfeed.tech/tags/reduction.md>)

### AI overview

A custom AWS DevOps Agent Skill uses signal classification and a prioritized decision tree to guide Aurora PostgreSQL incident investigations across five failure modes: connection exhaustion, replication lag, slow query regression, storage pressure, and parameter drift. In a controlled internal test of three simulated incidents, average time to identify root cause fell from 52 to 14 minutes, and wrong hypotheses per incident fell from 3.0 to 0.3. The comparison covered connection exhaustion, slow query regression, and parameter drift, so the reported results do not establish performance across every branch or production conditions. The guide requires an AWS account and Agent Space access to the cluster, CloudWatch metrics and Performance Insights, and the Operator Web App; it recommends deploying for Incident RCA and On-demand agents, excluding Incident Triage because the procedure is too thorough for fast triage.

### Source excerpt

Database incidents routinely take 45 to 60 minutes to triage. This post shows how to build a custom AWS DevOps Agent Skill that encodes expert Aurora PostgreSQL triage into decision-tree logic across five failure modes, cutting mean time to resolution from 52 minutes to 14 minutes (a 73% reduction) in a controlled test.

## Secure MCP integrations for AWS DevOps Agent with Amazon Bedrock AgentCore

DevFeed: [Secure MCP integrations for AWS DevOps Agent with Amazon Bedrock AgentCore](<https://devfeed.tech/articles/secure-mcp-integrations-for-aws-devops-agent-with-amazon-bedrock-agentcore-139361.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/secure-mcp-integrations-for-aws-devops-agent-with-amazon-bedrock-agentcore/>)

Author: Lakshmi Kumkala

Published: 2026-11-17T18:24:37Z

Content type: article

Language: en

Sources: [AWS DevOps & Developer Productivity Blog](<https://devfeed.tech/sources/aws-devops-developer-productivity-blog.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [admin](<https://devfeed.tech/tags/admin.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-opensearch-service](<https://devfeed.tech/tags/amazon-opensearch-service.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [mcp-tools](<https://devfeed.tech/tags/mcp-tools.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [observability](<https://devfeed.tech/tags/observability.md>), [private](<https://devfeed.tech/tags/private.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [rotation](<https://devfeed.tech/tags/rotation.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

AWS DevOps Agent can connect to MCP servers directly or through Amazon Bedrock AgentCore Gateway. Direct registration suits one or two servers in a single account and supports private endpoints through VPC Lattice; each tool must use streamable HTTP and a supported authentication method, and admins classify tools as read-only, mutating, or destructive. AgentCore Gateway offers a single registration and SigV4 connection, centralizes backend credentials, and can apply Cedar policies, unified CloudWatch audit logs, and X-Ray tracing across targets. It is useful when servers or accounts multiply or shared policy and observability are needed; private Gateway targets add central controls, while a direct private connection requires less configuration. The article recommends checking native integrations and existing vendor or sample MCP servers before building a custom one, and starting with a read-only tool in a non-production agent space.

### Source excerpt

As you connect more Model Context Protocol (MCP) tools to AWS DevOps Agent, each one adds its own authentication, credential rotation, and audit overhead. This post shows how to extend AWS DevOps Agent with MCP tools securely using Amazon Bedrock AgentCore, so new tools inherit consistent security, access control, private connectivity, and observability.

## Model-Driven Approaches for DevOps: A Systematic Literature Review

DevFeed: [Model-Driven Approaches for DevOps: A Systematic Literature Review](<https://devfeed.tech/articles/model-driven-approaches-for-devops-a-systematic-literature-review-137965.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18580>)

Author: Hugo da Gi\\~ao, Rui Pereira, J\\'acome Cunha

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [DevOps](<https://devfeed.tech/topics/devops.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops](<https://devfeed.tech/tags/devops.md>), [integration](<https://devfeed.tech/tags/integration.md>), [literature](<https://devfeed.tech/tags/literature.md>), [mde](<https://devfeed.tech/tags/mde.md>), [migration](<https://devfeed.tech/tags/migration.md>), [model](<https://devfeed.tech/tags/model.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [process](<https://devfeed.tech/tags/process.md>), [research](<https://devfeed.tech/tags/research.md>), [review](<https://devfeed.tech/tags/review.md>)

### AI overview

The review finds that model-driven approaches to DevOps research focus mainly on cloud computing, with deployment and integration the most explored phases. Some approaches are domain-agnostic. Nearly half of the reviewed papers use model-to-model transformations; text-to-model transformations are used less often, though the abstract also describes them as more prevalent overall. No reviewed study proposes a complete reengineering process, leaving gaps across both process coverage and the domains and DevOps phases studied.

### Source excerpt

arXiv:2611.18580v1 Announce Type: new Abstract: DevOps integrates tools and methodologies aimed at optimizing software development, building, deployment, and monitoring by automating and reducing the development lifecycle and improving software quality. However, despite its many advantages, it presents notable challenges, particularly in terms of usability and migration. On the other hand, model-driven engineering (MDE) offers a way to abstract from specific technologies and implementation details, which can be leveraged to improve these aspects, as happens in software development. In this paper, we present the first systematic literature review aiming to understand the current MDE approaches for supporting DevOps development. We focus on categorizing the works based on computing domains, the phases of the DevOps process to which they contribute, and the reengineering steps they propose. Our findings highlight a dominant focus on cloud computing, while some studies propose domain-agnostic approaches. We also observe that the deployment and integration phases are the most explored. This reveals research opportunities regarding both the domains and DevOps phases addressed. We also found limited use of text-to-model transformations, while nearly half of the papers employed model-to-model transformations. Text-to-model transformations were more prevalent overall. Most notably, we discovered that no study proposed a complete reengineering process, which represents an exciting avenue for future research.

## How Banco BMG moved from reactive to autonomous operations with AWS DevOps Agent

DevFeed: [How Banco BMG moved from reactive to autonomous operations with AWS DevOps Agent](<https://devfeed.tech/articles/how-banco-bmg-moved-from-reactive-to-autonomous-operations-with-aws-devops-agent-137734.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/how-banco-bmg-moved-from-reactive-to-autonomous-operations-with-aws-devops-agent/>)

Author: Matheus Arrais

Published: 2026-11-17T00:09:22Z

Content type: article

Language: en

Sources: [AWS Cloud Operations Blog](<https://devfeed.tech/sources/aws-cloud-operations-blog.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Cloud Native Operations](<https://devfeed.tech/topics/cloud-native-operations.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Azure DevOps](<https://devfeed.tech/topics/azure-devops.md>)

Tags: [alerts](<https://devfeed.tech/tags/alerts.md>), [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [autonomous-operations](<https://devfeed.tech/tags/autonomous-operations.md>), [aws](<https://devfeed.tech/tags/aws.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [incident](<https://devfeed.tech/tags/incident.md>), [logs](<https://devfeed.tech/tags/logs.md>), [management-tools](<https://devfeed.tech/tags/management-tools.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [pix](<https://devfeed.tech/tags/pix.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Banco BMG deployed AWS DevOps Agent across a hybrid and multicloud platform covering more than 1,150 services, connecting Dynatrace, Elasticsearch, Freshservice, Kubernetes audit logs, and Azure DevOps. Custom Skills capture product knowledge, while custom MCP servers extend access to internal systems. The agent correlates service topology, changes, metrics, and logs for investigations and anomaly detection. Reported outcomes include an 85% reduction in mean time to resolution (from two hours to 18 minutes), 62% of more than 300 sampled investigations resolved without human intervention, and pod restarts falling from about 25,000 to under 1,000 daily. In a PIX and Redis case, detection came up to six hours before traditional NOC alerting; payroll loan diagnosis fell from hours to minutes. The account describes a phased, domain-by-domain rollout and notes that broad signal coverage and encoding institutional knowledge were key to improving investigations. Banco BMG plans to add automated response while keeping a person in charge.

### Source excerpt

Summary Banco BMG is a Brazilian financial institution with 96 years of history. Its digital platform runs across AWS, other cloud providers, and on-premises infrastructure. At that scale, logs, metrics, alerts, and deployments come in faster than engineers can correlate them. When an incident hits a revenue-generating product such as PIX instant payments or payroll [...]

## Kubernetes Is Retiring kube-proxy's IPVS Mode. Canary nftables First

DevFeed: [Kubernetes Is Retiring kube-proxy's IPVS Mode. Canary nftables First](<https://devfeed.tech/articles/kubernetes-is-retiring-kube-proxy-s-ipvs-mode-canary-nftables-first-136239.md>)

Original publisher: [Read original article](<https://blog.devops.dev/kubernetes-is-retiring-kube-proxys-ipvs-mode-canary-nftables-first-5ec3e12c91fb?source=rss----33f8b2d9a328---4>)

Author: Daniel Valev

Published: 2026-11-16T13:26:06Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [canary release](<https://devfeed.tech/topics/canary-release.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>), [DevOps](<https://devfeed.tech/topics/devops.md>)

Tags: [deprecation](<https://devfeed.tech/tags/deprecation.md>), [devops](<https://devfeed.tech/tags/devops.md>), [dns](<https://devfeed.tech/tags/dns.md>), [exit](<https://devfeed.tech/tags/exit.md>), [feature](<https://devfeed.tech/tags/feature.md>), [gate](<https://devfeed.tech/tags/gate.md>), [interface](<https://devfeed.tech/tags/interface.md>), [ip](<https://devfeed.tech/tags/ip.md>), [iptables](<https://devfeed.tech/tags/iptables.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-clusters](<https://devfeed.tech/tags/kubernetes-clusters.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [model](<https://devfeed.tech/tags/model.md>), [nftables](<https://devfeed.tech/tags/nftables.md>), [node](<https://devfeed.tech/tags/node.md>), [override](<https://devfeed.tech/tags/override.md>), [packet](<https://devfeed.tech/tags/packet.md>), [pool](<https://devfeed.tech/tags/pool.md>), [programming](<https://devfeed.tech/tags/programming.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [technology](<https://devfeed.tech/tags/technology.md>), [trace](<https://devfeed.tech/tags/trace.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

The excerpt says kube-proxy IPVS mode has been deprecated since Kubernetes v1.35 and, from v1.40, kube-proxy exits at startup in that mode unless a feature gate is overridden. It identifies a key difference in how ClusterIPs are represented: in IPVS mode, a node's `ip addr` output shows Service ClusterIPs on `kube-ipvs0`. The teaser recommends tracing a packet through iptables, IPVS, and nftables, then canarying nftables on one node pool before upgrading. The excerpt does not provide the packet paths or explain the alternative modes in detail.

### Source excerpt

Trace one packet through iptables, IPVS, and nftables mode, then canary nftables on one node pool before the upgrade decides for you. Continue reading on DevOps.dev "

## Ops needs friction

DevFeed: [Ops needs friction](<https://devfeed.tech/articles/ops-needs-friction-134185.md>)

Original publisher: [Read original article](<https://www.jeffgeerling.com/blog/2026/ops-needs-friction/>)

Author: jeff@jeffgeerling.com (Jeff Geerling)

Published: 2026-11-14T16:30:00Z

Content type: opinion

Language: en

Sources: [Jeff Geerling](<https://devfeed.tech/sources/jeff-geerling.md>)

Topics: [DevOps](<https://devfeed.tech/topics/devops.md>), [cloud service outage management](<https://devfeed.tech/topics/cloud-service-outage-management.md>), [observability](<https://devfeed.tech/topics/observability.md>), [it modernization](<https://devfeed.tech/topics/it-modernization.md>)

Tags: [cluster](<https://devfeed.tech/tags/cluster.md>), [containers](<https://devfeed.tech/tags/containers.md>), [database](<https://devfeed.tech/tags/database.md>), [debug](<https://devfeed.tech/tags/debug.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [disaster](<https://devfeed.tech/tags/disaster.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [exploration](<https://devfeed.tech/tags/exploration.md>), [faa-ground-stop](<https://devfeed.tech/tags/faa-ground-stop.md>), [failure](<https://devfeed.tech/tags/failure.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [mindset](<https://devfeed.tech/tags/mindset.md>), [new-features](<https://devfeed.tech/tags/new-features.md>), [ops](<https://devfeed.tech/tags/ops.md>), [outages](<https://devfeed.tech/tags/outages.md>), [packet](<https://devfeed.tech/tags/packet.md>), [software](<https://devfeed.tech/tags/software.md>), [sysadmin](<https://devfeed.tech/tags/sysadmin.md>)

### AI overview

The author argues that operations teams need deliberate friction: people who stay calm during failures and flag risks before they grow. In one example, developers wanted debug-level production logs to avoid staging QA, but the added data burdened packet buffers. The author opposed keeping that logging permanently and compromised by having the cluster lower verbosity in new containers during traffic-driven scaling. The account presents this kind of pushback as a way to support development while preserving resilience, and describes early warnings and persistence around upgrades or system changes as safeguards against larger failures.

### Source excerpt

Between Microsoft's two-day outage and the FAA ground stop yesterday, there's plenty of ink spilled about who's responsible, why these things happened, etc. But it made me think back to some of the infrastructure and ops teams I've worked on, and similar (though much smaller scale) outages we encountered. Having an ops mindset is fundamentally different from a development or project management mindset. And it took me over a decade of software development to understand why.

## Best Tools for AI Agents in DevOps and IT Automation

DevFeed: [Best Tools for AI Agents in DevOps and IT Automation](<https://devfeed.tech/articles/best-tools-for-ai-agents-in-devops-and-it-automation-139352.md>)

Original publisher: [Read original article](<https://www.lyzr.ai/blog/best-tools-for-ai-agents-in-devops-and-it-automation-2/>)

Author: sujatha

Published: 2026-11-13T11:38:59Z

Content type: comparison

Language: en

Sources: [Lyzr.ai](<https://devfeed.tech/sources/lyzr-ai.md>)

Topics: [DevOps](<https://devfeed.tech/topics/devops.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [bits ai](<https://devfeed.tech/topics/bits-ai.md>)

Tags: [action-fabric](<https://devfeed.tech/tags/action-fabric.md>), [add-ons](<https://devfeed.tech/tags/add-ons.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-orchestration](<https://devfeed.tech/tags/agent-orchestration.md>), [agent-studio](<https://devfeed.tech/tags/agent-studio.md>), [agent-tools](<https://devfeed.tech/tags/agent-tools.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-credits](<https://devfeed.tech/tags/ai-credits.md>), [ai-features](<https://devfeed.tech/tags/ai-features.md>), [ai-software](<https://devfeed.tech/tags/ai-software.md>), [automation](<https://devfeed.tech/tags/automation.md>), [best](<https://devfeed.tech/tags/best.md>), [compare](<https://devfeed.tech/tags/compare.md>), [devops](<https://devfeed.tech/tags/devops.md>), [features](<https://devfeed.tech/tags/features.md>), [it](<https://devfeed.tech/tags/it.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

AI agent tools for DevOps differ in where they act and how they charge: PagerDuty focuses on on-call incident management, Datadog Bits investigates alerts in its observability stack using credits, Resolve AI offers autonomous on-call resolution with usage-based credits, ServiceNow coordinates IT service agents with metered assists, and Harness runs agents across CI/CD within a VPC or cluster, with automatic rollback after failed verification. Lyzr describes multi-agent workflows that detect, diagnose and resolve IT processes across existing systems, with approval gates and audit logs. The text recommends checking remediation capability, toolchain coverage, permission limits, audit records and costs at incident scale; most teams still want human approval for risky production actions. Pricing and plan constraints vary, and the text does not provide a like-for-like cost or performance comparison.

### Source excerpt

Compare the 6 best tools for AI agents in DevOps and IT automation, with key features, and tips to choose the right one for your...

## Profile your Amazon CloudWatch Logs estate with an AWS DevOps Agent skill in sandbox, no infrastructure to deploy

DevFeed: [Profile your Amazon CloudWatch Logs estate with an AWS DevOps Agent skill in sandbox, no infrastructure to deploy](<https://devfeed.tech/articles/profile-your-amazon-cloudwatch-logs-estate-with-an-aws-devops-agent-skill-in-sandbox-no-infrastructure-to-deploy-131308.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/profile-your-amazon-cloudwatch-logs-estate-with-an-aws-devops-agent-skill-in-sandbox-no-infrastructure-to-deploy/>)

Author: Rohan Vashi

Published: 2026-11-12T20:35:30Z

Content type: article

Language: en

Sources: [AWS Cloud Operations Blog](<https://devfeed.tech/sources/aws-cloud-operations-blog.md>)

Topics: [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-sandbox](<https://devfeed.tech/tags/agent-sandbox.md>), [agent-skill](<https://devfeed.tech/tags/agent-skill.md>), [aggregate](<https://devfeed.tech/tags/aggregate.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-data-firehose](<https://devfeed.tech/tags/amazon-data-firehose.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudwatch](<https://devfeed.tech/tags/aws-cloudwatch.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [data](<https://devfeed.tech/tags/data.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [logs](<https://devfeed.tech/tags/logs.md>), [profile](<https://devfeed.tech/tags/profile.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [skill](<https://devfeed.tech/tags/skill.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [view](<https://devfeed.tech/tags/view.md>), [zero](<https://devfeed.tech/tags/zero.md>)

### AI overview

The article presents a reusable AWS DevOps Agent skill that profiles CloudWatch log groups in one account and Region per run, joining inventory, retention and class, ingestion and growth, configured consumers, subscription destinations, and data protection into a per-group report. The script runs on demand in Sandbox with read-only access and no standing analysis infrastructure; metric requests are batched and describe calls run concurrently. Results are options for operator review: no detected consumer does not establish that a group is unnecessary, and Infrequent Access suitability depends on Standard-only features. Cost figures use configurable rate assumptions and name-based vended-log classification; verify current rates and adjust naming patterns. Query counts are reported, not query cost. Sandbox is described as a preview feature. Multi-Region coverage requires repeated runs, and multi-account coverage uses separate investigations; scheduled runs add EventBridge Scheduler and Lambda trigger infrastructure.

### Source excerpt

A zero-infrastructure AWS DevOps Agent skill profiles your Amazon CloudWatch Logs estate and gives you one view of it. CloudWatch Logs already captures the signals you need to operate it well, including how each log group is classed, how long it is kept, who reads it, where its data flows, and how fast it grows. [...]

## AI-driven database investigation using MCP, Agent Skills, and AWS DevOps Agent

DevFeed: [AI-driven database investigation using MCP, Agent Skills, and AWS DevOps Agent](<https://devfeed.tech/articles/ai-driven-database-investigation-using-mcp-agent-skills-and-aws-devops-agent-131174.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/integrate-mcp-tools-agent-skills-and-aws-devops-agent-for-ai-driven-database-investigation/>)

Author: Sudhir Amin

Published: 2026-11-12T18:34:07Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [sql-server](<https://devfeed.tech/topics/sql-server.md>), [RDS for SQL Server](<https://devfeed.tech/topics/rds-for-sql-server.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [connect](<https://devfeed.tech/tags/connect.md>), [database](<https://devfeed.tech/tags/database.md>), [dba](<https://devfeed.tech/tags/dba.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [diagnostic](<https://devfeed.tech/tags/diagnostic.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [rds-for-sql-server](<https://devfeed.tech/tags/rds-for-sql-server.md>), [skills](<https://devfeed.tech/tags/skills.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AWS DevOps Agent can investigate RDS for SQL Server incidents by combining CloudWatch and Database Insights telemetry with SQL-specific MCP tools hosted in Lambda and exposed through Amazon Bedrock AgentCore Gateway. A Markdown skill defines triage thresholds, diagnostic steps, and report format; built-in telemetry identifies the problem type, while Gateway tools retrieve session, query, plan, and index details. In the example, an alarm led the agent to identify a head blocker holding a lock on dbo.Orders, with about 14 sessions waiting. It linked recurring spikes to a five-minute transaction pattern, noted it could not identify the client process, and recommended removing the delay, bounding client timeouts, and raising the alarm threshold. Access is constrained through SigV4, an allowlist, Secrets Manager credential retrieval by Lambda, and a read-only SQL login. The sample requires Database Insights, suitable database permissions, private VPC access, and supported AWS services and region.

### Source excerpt

Learn how to connect Amazon RDS for SQL Server diagnostic tools to AWS DevOps Agent through Amazon Bedrock AgentCore Gateway. MCP tools run in AWS Lambda behind a governed Gateway endpoint, and an investigation skill encodes your DBA team's method so the agent can triage alarms and run autonomous, auditable database investigations.

## Agents Are Code Too: What I Learned Shipping a Cortex Agent Through Azure DevOps

DevFeed: [Agents Are Code Too: What I Learned Shipping a Cortex Agent Through Azure DevOps](<https://devfeed.tech/articles/agents-are-code-too-what-i-learned-shipping-a-cortex-agent-through-azure-devops-129094.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/agents-are-code-too-what-i-learned-shipping-a-cortex-agent-through-azure-devops-fab3adae29e8?source=rss----34b6daafc07---4>)

Author: Sanket Prabhu

Published: 2026-11-11T15:01:07Z

Content type: article

Language: en

Sources: [Snowflake Builders](<https://devfeed.tech/sources/snowflake-builders.md>)

Topics: [Azure DevOps](<https://devfeed.tech/topics/azure-devops.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [CI/CD Pipeline](<https://devfeed.tech/topics/ci-cd-pipeline.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [analyst](<https://devfeed.tech/tags/analyst.md>), [azure-devops](<https://devfeed.tech/tags/azure-devops.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [ci-cd-pipeline](<https://devfeed.tech/tags/ci-cd-pipeline.md>), [code](<https://devfeed.tech/tags/code.md>), [config](<https://devfeed.tech/tags/config.md>), [cortex](<https://devfeed.tech/tags/cortex.md>), [cortex-agent](<https://devfeed.tech/tags/cortex-agent.md>), [data](<https://devfeed.tech/tags/data.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [data-platforms](<https://devfeed.tech/tags/data-platforms.md>), [dev](<https://devfeed.tech/tags/dev.md>), [domain](<https://devfeed.tech/tags/domain.md>), [environment](<https://devfeed.tech/tags/environment.md>), [finance](<https://devfeed.tech/tags/finance.md>), [git](<https://devfeed.tech/tags/git.md>), [instructions](<https://devfeed.tech/tags/instructions.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [orchestrator](<https://devfeed.tech/tags/orchestrator.md>), [platform](<https://devfeed.tech/tags/platform.md>), [snowflake-cortex](<https://devfeed.tech/tags/snowflake-cortex.md>)

### AI overview

The main production challenge was safely promoting a finance Cortex Agent across sbx, dev, uat and prod; the author treats the agent as code managed through the existing Azure DevOps path. Store its YAML specification, semantic view, Cortex Search service, grants and evaluation questions in one repo. Use CREATE AGENT ... FROM SPECIFICATION with one environment variable for the target database; COPY GRANTS with OR REPLACE to preserve grants. Deploy the semantic view first, then search, agent and grants in the same release, with least-privilege deployment credentials and approval gates for uat and prod. A successful CREATE AGENT does not ensure runtime behavior: run fixed domain questions after each deployment, checking expected answers and whether questions route to Analyst or Search. The article also describes a Snowflake developer guide that evaluates semantic-view SQL against verified queries and agent answer correctness and tool-selection accuracy; check account release status before relying on agent evaluations and versioning. Grants must cover the agent, search service and objects behind the semantic view.

### Source excerpt

Building the agent took a week. Getting it safely from sandbox to production took longer, and taught me more. Most Cortex Agent content I read ends at the same place: a working demo in Snowsight, a clever question, a correct answer. That is where my real work started. In my recent project, I built a Cortex Agent for the finance domain. The agent itself came together quickly. What took real thought was the part nobody demos: moving it through sbx, dev, uat and prod with the same discipline we already applied to every other Snowflake object on the platform. After roughly a decade of building data platforms, I've learned to be suspicious of anything that only exists in one environment. So here is what I learned treating an agent like code, and what I'd do the same way again. An agent you can't rebuild from Git is a prototype, no matter how good its answers are.1. The myth: "An agent is just a config in the UI" It's easy to see a Cortex Agent as a few settings in a form: pick a semantic view, add a search service, write some instructions, done. But look at what actually decides whether the agent gives a good answer: Tool descriptions that tell the orchestrator when to use which tool Orchestration and response instructions The semantic view behind Cortex Analyst, including its verified queries The Cortex Search service and the columns it exposes Grants that decide who can call the agent and what it can reach Every one of these is a behavior change. If someone edits a tool description in prod by hand, the agent can start routing questions differently, and you have no diff, no review and no way back. On our platform, warehouses, roles, schemas and grants were already managed through Terraform and Azure DevOps. It didn't make sense for the agent to be the one thing people clicked together. So where does an agent actually live, if not in the UI? 2. Everything the agent needs goes in the repo The good news is that Snowflake gives you a clean way to express an agent as code. C

## Rubrik enhances DevOps Protection to preserve legitimate work during recovery

DevFeed: [Rubrik enhances DevOps Protection to preserve legitimate work during recovery](<https://devfeed.tech/articles/rubrik-enhances-devops-protection-to-preserve-legitimate-work-during-recovery-128036.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/11/11/rubrik-devops-protection/>)

Author: Industry News

Published: 2026-11-11T12:01:53Z

Content type: release

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [Incident response](<https://devfeed.tech/topics/incident-response.md>), [Azure DevOps](<https://devfeed.tech/topics/azure-devops.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [DevSecOps](<https://devfeed.tech/topics/devsecops.md>)

Tags: [air-gapped](<https://devfeed.tech/tags/air-gapped.md>), [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [attack](<https://devfeed.tech/tags/attack.md>), [azure](<https://devfeed.tech/tags/azure.md>), [azure-devops](<https://devfeed.tech/tags/azure-devops.md>), [backups](<https://devfeed.tech/tags/backups.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [changes](<https://devfeed.tech/tags/changes.md>), [code](<https://devfeed.tech/tags/code.md>), [cyber](<https://devfeed.tech/tags/cyber.md>), [cyber-recovery](<https://devfeed.tech/tags/cyber-recovery.md>), [detection](<https://devfeed.tech/tags/detection.md>), [developer](<https://devfeed.tech/tags/developer.md>), [devops](<https://devfeed.tech/tags/devops.md>), [industry-news](<https://devfeed.tech/tags/industry-news.md>), [protection](<https://devfeed.tech/tags/protection.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [rubrik](<https://devfeed.tech/tags/rubrik.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

Rubrik says its DevOps Protection Enterprise Edition adds a unified recovery workflow for Microsoft Azure DevOps and GitHub. It baselines audit logs and correlates them with backup metadata to flag suspicious identity activity; investigation categorizes affected repositories, commits, pipelines, workflows, pull requests, and settings; and surgical recovery restores attacker changes while preserving other developers' legitimate work from clean, air-gapped, immutable backups. Rubrik says this can avoid manual rebuilds and organization-wide code freezes. Foundation Edition also expands backups to platform metadata and collaboration items such as issues, pull requests, Azure Boards, wikis, packages, and organization settings, enabling recovery of broader team context. The capabilities were expected to become generally available in the coming months.

### Source excerpt

Rubrik has announced cyber recovery capabilities for DevOps platforms Microsoft Azure DevOps and GitHub. With built-in anomaly detection, blast radius investigation, and surgical recovery, organizations will be able to detect suspicious activity on their code, instantly scope the impact of an attack, and undo the attackers' changes from air-gapped, immutable backups, without disrupting legitimate developer work. "An organization's source code is where innovation lives, and attackers know it," said Anneka Gupta, Chief Product Officer at ... More -> The post Rubrik enhances DevOps Protection to preserve legitimate work during recovery appeared first on Help Net Security.

## Invisible engineering teams

DevFeed: [Invisible engineering teams](<https://devfeed.tech/articles/invisible-engineering-teams-125627.md>)

Original publisher: [Read original article](<https://www.manager.dev/newsletter/invisible-engineering-teams>)

Author: Anton Zaides

Published: 2026-11-10T07:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [AI tools for developers](<https://devfeed.tech/topics/ai-tools-for-developers.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [business](<https://devfeed.tech/tags/business.md>), [devops](<https://devfeed.tech/tags/devops.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-manager](<https://devfeed.tech/tags/engineering-manager.md>), [teams](<https://devfeed.tech/tags/teams.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

The author argues that low team visibility can cost engineers recognition and promotion opportunities and leave teams vulnerable to business changes, headcount cuts, or layoffs. Signs include receiving little credit but blame, accumulating operations work, difficulty advocating for promotions, and engineers feeling disconnected from the business. To improve visibility, the author recommends sending relevant updates through channels stakeholders actually use, tailoring detail to each audience; questioning whether the work would be missed if it stopped; and bringing stakeholders and concrete examples of the team's impact into team meetings. The piece draws on the author's experience managing teams with different visibility levels and presents these as practical approaches, not guaranteed outcomes.

### Source excerpt

Dealing with the left side of the visibility spectrum

## 7 DevOps Books Worth Reading Before Your First Engineering Job

DevFeed: [7 DevOps Books Worth Reading Before Your First Engineering Job](<https://devfeed.tech/articles/7-devops-books-worth-reading-before-your-first-engineering-job-121893.md>)

Original publisher: [Read original article](<https://blog.devops.dev/7-devops-books-worth-reading-before-your-first-engineering-job-65f030d17633?source=rss----33f8b2d9a328---4>)

Author: Zudonu Osomudeya

Published: 2026-11-06T21:46:01Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [DevOps](<https://devfeed.tech/topics/devops.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Deployment & Scaling](<https://devfeed.tech/topics/deployment-scaling.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [ai](<https://devfeed.tech/tags/ai.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [applying](<https://devfeed.tech/tags/applying.md>), [beginners](<https://devfeed.tech/tags/beginners.md>), [best](<https://devfeed.tech/tags/best.md>), [better](<https://devfeed.tech/tags/better.md>), [book](<https://devfeed.tech/tags/book.md>), [books](<https://devfeed.tech/tags/books.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [career](<https://devfeed.tech/tags/career.md>), [certifications](<https://devfeed.tech/tags/certifications.md>), [devops](<https://devfeed.tech/tags/devops.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [first](<https://devfeed.tech/tags/first.md>), [job](<https://devfeed.tech/tags/job.md>), [programming](<https://devfeed.tech/tags/programming.md>), [reading](<https://devfeed.tech/tags/reading.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [sre](<https://devfeed.tech/tags/sre.md>), [vibe-coding](<https://devfeed.tech/tags/vibe-coding.md>), [worth-reading](<https://devfeed.tech/tags/worth-reading.md>)

### AI overview

The article recommends choosing books to address a specific gap rather than finishing all seven before applying for jobs. The Phoenix Project introduces why communication and shared delivery processes matter; DevOps Operating System offers a 12-phase path that combines tools around one three-tier application and includes job-search preparation. The DevOps Handbook explains CI/CD and team delivery practices across tools. The UNIX and Linux System Administration Handbook is a reference for troubleshooting systems. DevOps Interview Decoder provides 47 questions, response guidance, mock prompts, and a seven-day plan for explaining technical work. Designing Data-Intensive Applications covers data systems and scalability for readers with application fundamentals; Google's Site Reliability Engineering book covers monitoring, incident response, automation, SLOs, and reliability. The article stresses that more study or certifications do not guarantee a job, and suggests seeking feedback or opportunities when existing skills and projects are already strong.

### Source excerpt

For beginners, career switchers, and engineers who have spent months learning but still haven't landed their first role. Getting your first DevOps job today can be frustrating. You've spent months learning Linux, Docker, Kubernetes, and Terraform. Completed courses, built projects, earned certifications, and sent out applications. Then you get another rejection email. Meanwhile, companies are announcing layoffs, AI is changing how engineering teams work, and every job posting seems to require three years of experience for a junior position. At some point, you begin to wonder what else you're supposed to learn. I've experienced that frustration myself. And I know the last thing someone in that position wants is another list of ten tools to master. So I'm not recommending seven books you must finish before applying for jobs. These are resources for different problems you might be facing. Some explain how engineering teams work, others help with practical projects, and a few help you prepare for interviews. Pick what you need. 1. The Phoenix Project: Gene Kim, Kevin Behr, and George Spafford If you're completely new to DevOps, I'd start here. The Phoenix Project follows an IT manager dealing with failed deployments, delayed projects, angry executives, and an endless list of urgent problems. Not exactly the dream workplace. But that's what makes the book interesting. It shows what happens when developers, operations teams, and management work separately, and how better communication and delivery processes can improve things. There are no Kubernetes manifests to memorize. Just a story that helps explain why companies need DevOps practices. Best for: Career switchers and beginners who want to understand what DevOps engineers are trying to improve at work. 2. DevOps Operating System: A Practical, 12-Phase Learning Path Here's a problem I've noticed among people learning DevOps. Someone completes a Docker course, deploys an application to Kubernetes, learns Terraform, and m

## GitLab 19.5 Makes Agentic Development a Governed Part of the DevOps Platform

DevFeed: [GitLab 19.5 Makes Agentic Development a Governed Part of the DevOps Platform](<https://devfeed.tech/articles/gitlab-19-5-makes-agentic-development-a-governed-part-of-the-devops-platform-121075.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/gitlab-19-5-agentic-platform/>)

Author: Craig Risi

Published: 2026-11-06T12:00:00Z

Content type: release

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-development](<https://devfeed.tech/tags/agentic-development.md>), [agentic-development-lifecycle](<https://devfeed.tech/tags/agentic-development-lifecycle.md>), [agentic-software-development](<https://devfeed.tech/tags/agentic-software-development.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cli](<https://devfeed.tech/tags/cli.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [devops](<https://devfeed.tech/tags/devops.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [gitlab-19-5-agentic-platform](<https://devfeed.tech/tags/gitlab-19-5-agentic-platform.md>), [governance](<https://devfeed.tech/tags/governance.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [news](<https://devfeed.tech/tags/news.md>)

### AI overview

GitLab 19.5 makes its MCP server generally available, letting compatible tools such as Claude Code and Cursor access GitLab capabilities and start or monitor Duo agents and flows. Administrators can restrict exposed toolsets; GitLab.com limits MCP requests to 60 per minute for Free users and 600 for Premium and Ultimate, counting reconnects and retries. Organizations can connect external agents through the GitLab CLI, record qualifying sessions in AI Governance, and stream audit events to a SIEM. Duo CLI's auto mode can run tools without per-action approval, but is disabled by default, can be controlled at instance, group, and project levels, and still blocks tools marked Always Deny. The release also makes Secrets Manager generally available and adds centralized security profiles for Secret Detection and SAST. The article presents GitLab's approach as making the DevOps platform agent-accessible while emphasizing governance.

### Source excerpt

GitLab 19.5, released on October 15, puts agentic software development and governance at the centre of the platform, making its GitLab MCP server generally available while expanding how external AI agents can interact with GitLab. By Craig Risi

## Complete DevOps Engineer Roadmap 2026: A Beginner-to-Production Guide to Everything You Need to...

DevFeed: [Complete DevOps Engineer Roadmap 2026: A Beginner-to-Production Guide to Everything You Need to...](<https://devfeed.tech/articles/complete-devops-engineer-roadmap-2026-a-beginner-to-production-guide-to-everything-you-need-to-121429.md>)

Original publisher: [Read original article](<https://blog.devops.dev/complete-devops-engineer-roadmap-2026-a-beginner-to-production-guide-to-everything-you-need-to-39e5683095ee?source=rss----33f8b2d9a328---4>)

Author: Arvind Verma

Published: 2026-11-06T09:47:21Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [DevOps](<https://devfeed.tech/topics/devops.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [DevSecOps](<https://devfeed.tech/topics/devsecops.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Ansible](<https://devfeed.tech/topics/ansible.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ansible](<https://devfeed.tech/tags/ansible.md>), [aws](<https://devfeed.tech/tags/aws.md>), [beginner](<https://devfeed.tech/tags/beginner.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-engineer](<https://devfeed.tech/tags/devops-engineer.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [guide](<https://devfeed.tech/tags/guide.md>), [it](<https://devfeed.tech/tags/it.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linux](<https://devfeed.tech/tags/linux.md>), [production](<https://devfeed.tech/tags/production.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [python](<https://devfeed.tech/tags/python.md>), [roadmap](<https://devfeed.tech/tags/roadmap.md>)

### AI overview

The roadmap frames DevOps as understanding an application's full path from code through deployment, security, monitoring, and production support--not collecting tools. It recommends progressing through Linux, networking, Git, Shell and Python; cloud fundamentals (using AWS as a starting point); Docker and one CI/CD platform; then Kubernetes, Terraform, Ansible, Helm and Argo CD, observability, DevSecOps, and SRE practices. It distinguishes Terraform for provisioning infrastructure from Ansible for configuring servers, and describes GitOps as a controller reconciling cluster state with configuration stored in Git. Hands-on projects build toward a documented AWS EKS delivery platform, with troubleshooting, security, monitoring, rollback, and recovery included. An intensive eight-week plan assumes 4-6 study hours daily; the article cautions that this is a learning guide, recommends focusing on fundamentals and reproducible projects, and says certifications do not replace practical experience.

### Source excerpt

Complete DevOps Engineer Roadmap 2026: A Beginner-to-Production Guide to Everything You Need to LearnA highly recommended read for aspiring DevOps Engineers, IT professionals, and anyone planning to transition into DevOps. A must-read roadmap for building your DevOps career in 2026. If you're starting your DevOps journey, one question probably keeps coming up: What exactly should I learn to become a complete DevOps Engineer? Should you start with Linux? Should you learn AWS first? Is Docker enough? When should you start Kubernetes? Do you need Terraform, Jenkins, Python, Ansible, GitOps, Prometheus, Grafana, and DevSecOps? The number of tools can feel overwhelming, especially when every tutorial introduces another technology. But here is something important: Becoming a DevOps Engineer is not about learning 30 tools. It is about understanding how software is developed, built, tested, deployed, monitored, secured, and maintained in production. You need to understand the complete journey of an application, from a developer writing code to customers using that application reliably. This guide explains what to learn, why you need it, where it is used, which tools to practise, and what projects you should build. Whether you're a fresher, system administrator, cloud engineer, developer, or someone switching careers, follow this roadmap in sequence. First, Understand What a DevOps Engineer Actually Does Imagine a company building an e-commerce application. Developers write code for product listings, payments, customer accounts, and order management. But writing code is only one part of delivering software. Someone must: Maintain the infrastructure where the application runs. Automate code building and testing. Package applications into containers. Provision cloud resources. Deploy applications safely. Monitor application performance. Manage security and access. Troubleshoot production failures. Maintain availability and control infrastructure costs. This is where DevOps eng

## Azure MCP Server 3.0 Goes Stable: A Practical Guide for DevOps & Platform Engineers

DevFeed: [Azure MCP Server 3.0 Goes Stable: A Practical Guide for DevOps & Platform Engineers](<https://devfeed.tech/articles/azure-mcp-server-3-0-goes-stable-a-practical-guide-for-devops-platform-engineers-121426.md>)

Original publisher: [Read original article](<https://blog.devops.dev/azure-mcp-server-3-0-goes-stable-a-practical-guide-for-devops-platform-engineers-0b83bd64ef0c?source=rss----33f8b2d9a328---4>)

Author: Ashish Kasaudhan

Published: 2026-11-06T09:46:00Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Azure](<https://devfeed.tech/topics/azure.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Azure DevOps](<https://devfeed.tech/topics/azure-devops.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [azure](<https://devfeed.tech/tags/azure.md>), [azure-devops](<https://devfeed.tech/tags/azure-devops.md>), [backup](<https://devfeed.tech/tags/backup.md>), [devops](<https://devfeed.tech/tags/devops.md>), [generative-ai-tools](<https://devfeed.tech/tags/generative-ai-tools.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [operations](<https://devfeed.tech/tags/operations.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [stable](<https://devfeed.tech/tags/stable.md>)

### AI overview

Azure MCP Server 3.0 exposes Azure operations to MCP-compatible agents, with permissions bounded by the signed-in identity's RBAC. It adds operational toolsets for Backup, Resilience, SRE Agent, Terraform and Advisor/Optimization, plus stricter tool schemas, opt-in structured output, stateless protocol support, and secure defaults for newly created resources. The guide recommends starting read-only with a Reader-scoped identity, exploring commands with `--learn`, and using exact tool allowlists; agents can gather evidence and prepare IaC changes for human review and pipeline approval. It also outlines practical workflows for Terraform imports, cost recommendations, backup audits, disaster recovery readiness, incident triage and Azure Pipelines reports. Upgrades require attention to renamed tools, changed response wrappers and configuration, and database query tools are treated as destructive. SRE Agent tools depend on a preview provider, and the remote deployment mode remains preview.

### Source excerpt

TL;DR Azure MCP Server 3.0 went stable on 12 October 2026, and it is the first release that feels built for operations teams rather than demo-driven developers. It rolls up 50 beta iterations into one version that adds Backup, Resilience, SRE Agent, Terraform and Advisor/Optimization toolsets, ships secure-by-default resource creation, and plugs into Azure Pipelines through workload identity federation (Microsoft announcement). For a platform engineer, the short version is this: your AI agent can now answer "is this workload protected, what does it cost, and what would the Terraform change look like" in one conversation, and still hand the final change to your normal PR and approval flow. What Azure MCP Server actually is It is Microsoft's open-source implementation of the Model Context Protocol for Azure: a single server that exposes Azure operations as tools any MCP-compatible agent can discover and call. Think of it as a typed, permission-aware adapter between your agent and Azure Resource Manager plus the service data planes. A request flows like this: You ask a question in your client (VS Code, Claude, Copilot CLI, Cursor, or a custom agent). The client picks a tool from the server's catalog, based on the tool descriptions and input schemas. Azure MCP Server authenticates with your identity (Azure CLI login, managed identity, or a pipeline service connection). It calls the Azure control or data plane and returns structured results to the agent. The agent reasons over the result and either answers or proposes the next call. The key point for platform teams: the agent can only do what the signed-in identity is allowed to do. RBAC, not the prompt, is the real boundary. Ways to run it 3.0 ships through every channel a platform team is likely to standardise on (3.0.0 release notes): For an enterprise rollout, the container image is usually the right default: you can mirror it into your own registry, scan it, pin it by digest and run it behind your network controls.

## DevOps Log Management: A Comprehensive Evaluation Guide

DevFeed: [DevOps Log Management: A Comprehensive Evaluation Guide](<https://devfeed.tech/articles/devops-log-management-a-comprehensive-evaluation-guide-117733.md>)

Original publisher: [Read original article](<https://newrelic.com/blog/log/devops-log-management>)

Author: John Blust

Published: 2026-11-04T12:00:00Z

Content type: article

Language: en

Sources: [New Relic](<https://devfeed.tech/sources/new-relic.md>)

Topics: [log management](<https://devfeed.tech/topics/log-management.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Application Performance Management (APM)](<https://devfeed.tech/topics/apm.md>), [Azure DevOps](<https://devfeed.tech/topics/azure-devops.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>)

Tags: [accelerate](<https://devfeed.tech/tags/accelerate.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [agents](<https://devfeed.tech/tags/agents.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [api](<https://devfeed.tech/tags/api.md>), [apm](<https://devfeed.tech/tags/apm.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [data](<https://devfeed.tech/tags/data.md>), [devops](<https://devfeed.tech/tags/devops.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [guide](<https://devfeed.tech/tags/guide.md>), [log-management](<https://devfeed.tech/tags/log-management.md>), [noise](<https://devfeed.tech/tags/noise.md>)

### AI overview

Effective DevOps log management centers on searchable, structured logs correlated with metrics, traces and deployment data, so teams can trace incidents across distributed services. The guide distinguishes Azure DevOps audit logs, which record administrative activity in the platform, from operational logs that capture runtime behavior. It outlines a pipeline of collection, enrichment and indexing, analysis and alerting, and retention and governance. Suggested practices include consistent structured logging, sampling or deduplication of noisy events, trace IDs and deployment markers. Its evaluation criteria include query performance, ingestion flexibility, noise controls, alert quality, pricing and ease of parsing. The guide presents New Relic as a unified option with cross-telemetry querying, no-code parsing and federated logs; these are source claims. It also states that pricing is 100 GB/month free and $0.40/GB thereafter.

### Source excerpt

Discover how effective devops log management helps you quickly troubleshoot incidents, reduce noise, and improve operational visibility with the right data.

## Meet Paige, PagerDuty's SRE Agent: Faster Fixes Today, Fewer Incidents Tomorrow by PagerDuty

DevFeed: [Meet Paige, PagerDuty's SRE Agent: Faster Fixes Today, Fewer Incidents Tomorrow by PagerDuty](<https://devfeed.tech/articles/meet-paige-pagerduty-s-sre-agent-faster-fixes-today-fewer-incidents-tomorrow-by-pagerduty-115677.md>)

Original publisher: [Read original article](<https://www.pagerduty.com/blog/ai/meet-paige-sre-agent/>)

Author: PagerDuty

Published: 2026-11-03T11:00:27Z

Content type: release

Language: en

Sources: [PagerDuty](<https://devfeed.tech/sources/pagerduty.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [DevAIOps](<https://devfeed.tech/topics/devaiops.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [supervisor agent pattern](<https://devfeed.tech/topics/supervisor-agent-pattern.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [data](<https://devfeed.tech/tags/data.md>), [devops](<https://devfeed.tech/tags/devops.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-and-devops](<https://devfeed.tech/tags/engineering-and-devops.md>), [faster](<https://devfeed.tech/tags/faster.md>), [fewer](<https://devfeed.tech/tags/fewer.md>), [first](<https://devfeed.tech/tags/first.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [operational](<https://devfeed.tech/tags/operational.md>), [operations](<https://devfeed.tech/tags/operations.md>), [over](<https://devfeed.tech/tags/over.md>), [pagerduty](<https://devfeed.tech/tags/pagerduty.md>), [paige](<https://devfeed.tech/tags/paige.md>), [post](<https://devfeed.tech/tags/post.md>), [sre](<https://devfeed.tech/tags/sre.md>), [sre-agent](<https://devfeed.tech/tags/sre-agent.md>), [works](<https://devfeed.tech/tags/works.md>)

### AI overview

PagerDuty presents Paige as an SRE agent that uses incident history, telemetry, documentation, and team feedback to support incident response and prevention. It consolidates alerts, routes incidents, briefs responders, tests and ranks possible causes with visible reasoning, and suggests fixes based on similar past incidents. Paige can run specified workflows or apply resolutions with approval; autonomous handling of user-defined, well-understood incidents is described as coming soon. Teams set its data access and authority, can override its recommendations, and retain judgment over novel cases and stakeholder communications. Each incident can inform shared memory and a draft post-incident review. Deep Investigation and SRE Workbench are identified as PD Labs previews; the article also describes MCP connections and 750+ integrations.

### Source excerpt

Today, we're introducing Paige, PagerDuty's SRE Agent. Built on over 16 years of operational data, Paige works as a member of operations, engineering, and DevOps... The post Meet Paige, PagerDuty's SRE Agent: Faster Fixes Today, Fewer Incidents Tomorrow appeared first on PagerDuty.

## Extending AWS DevOps Agent with Skills, Model Context Protocol (MCP) Servers, Custom Agents and Connectors

DevFeed: [Extending AWS DevOps Agent with Skills, Model Context Protocol (MCP) Servers, Custom Agents and Connectors](<https://devfeed.tech/articles/extending-aws-devops-agent-with-skills-model-context-protocol-mcp-servers-custom-agents-and-connectors-114285.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/extending-aws-devops-agent-with-skills-model-context-protocol-mcp-servers-custom-agents-and-connectors/>)

Author: Yaki Ratz

Published: 2026-11-02T22:30:58Z

Content type: tutorial

Language: en

Sources: [AWS Cloud Operations Blog](<https://devfeed.tech/sources/aws-cloud-operations-blog.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-operations](<https://devfeed.tech/tags/cloud-operations.md>), [code](<https://devfeed.tech/tags/code.md>), [connectors](<https://devfeed.tech/tags/connectors.md>), [container](<https://devfeed.tech/tags/container.md>), [custom](<https://devfeed.tech/tags/custom.md>), [custom-agents](<https://devfeed.tech/tags/custom-agents.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [ecs](<https://devfeed.tech/tags/ecs.md>), [generic](<https://devfeed.tech/tags/generic.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-servers](<https://devfeed.tech/tags/mcp-servers.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [skills](<https://devfeed.tech/tags/skills.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AWS DevOps Agent can incorporate team-specific operational knowledge through skills, MCP servers, custom agents and connectors. Skills guide investigations; MCP servers provide data-plane access beyond the built-in read-only use_aws tool; custom agents package skills and tools into repeatable workflows; connectors point to partner-hosted MCP servers. The article describes an open-source catalog and an Amazon EKS Operations Review skill that gathers cluster and signal data, grades 288 checks across nine best-practice pillars, and produces a Markdown report. Contributions are evaluated through static structure checks, LLM-judged best-practice checks, and functional runs with and without the skill in a real Agent Space. The repository provides sample code, so its guidance calls for non-production testing and review of IAM permissions and security settings before production use. Skills and custom agents trigger billed agent work; MCP servers may create billable infrastructure, while connector service charges depend on the partner.

### Source excerpt

AWS DevOps Agent investigates incidents, traces problems from code to cloud, and analyzes Amazon CloudWatch, AWS CloudTrail, and third-party observability tools out of the box. But every operations team carries knowledge the agent cannot reach through generic reasoning: the order you check things in when, for example, an Amazon Elastic Container Service (ECS) task won't [...]

## How Circle K accelerated DevOps incident triage to under 15 minutes with Amazon Bedrock

DevFeed: [How Circle K accelerated DevOps incident triage to under 15 minutes with Amazon Bedrock](<https://devfeed.tech/articles/how-circle-k-accelerated-devops-incident-triage-to-under-15-minutes-with-amazon-bedrock-113558.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/how-circle-k-accelerated-devops-incident-triage-to-under-15-minutes-with-amazon-bedrock/>)

Author: Marek Klatowicz

Published: 2026-11-02T17:00:58Z

Content type: article

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [aws-sns](<https://devfeed.tech/topics/aws-sns.md>)

Tags: [agentcore](<https://devfeed.tech/tags/agentcore.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-bedrock-knowledge-bases](<https://devfeed.tech/tags/amazon-bedrock-knowledge-bases.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [amazon-opensearch-service](<https://devfeed.tech/tags/amazon-opensearch-service.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-sns](<https://devfeed.tech/tags/amazon-sns.md>), [amazon-sqs](<https://devfeed.tech/tags/amazon-sqs.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [api](<https://devfeed.tech/tags/api.md>), [application-load-balancer](<https://devfeed.tech/tags/application-load-balancer.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automated](<https://devfeed.tech/tags/automated.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [devops](<https://devfeed.tech/tags/devops.md>), [incident](<https://devfeed.tech/tags/incident.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [triage](<https://devfeed.tech/tags/triage.md>)

### AI overview

Circle K reports reducing mean DevOps incident triage from 45-60 minutes to under 15 minutes by automating investigation and sending structured findings to Slack. Its initial Amazon Bedrock Flows design ran AWS resource and OpenSearch analysis in parallel, then used those findings to focus GitHub code searches; a final model call summarized likely cause, evidence, service owner, and remediation. As investigations outgrew the Flow design, Circle K moved the same analysis logic to one containerized agent on Amazon Bedrock AgentCore Runtime, with AgentCore Gateway brokering access to OpenSearch, Knowledge Bases, and GitHub. Runtime supports longer sessions, persistent investigation state, OpenTelemetry traces surfaced in CloudWatch, and framework flexibility. The post says straightforward cases produce summaries in 5-8 minutes and complex cases within 15. Lessons include pre-querying logs and passing relevant lines directly, narrowing code searches using earlier findings, and keeping analysis logic independent of orchestration. Remediation remains engineer-performed; planned automated actions would require Slack approval.

### Source excerpt

Circle K's DevOps team cut incident triage from 45-60 minutes to under 15 by building an agentic triage system on Amazon Bedrock. This post walks through the architecture, the initial Amazon Bedrock Flows implementation, the migration to Amazon Bedrock AgentCore, and the lessons learned from scaling it.

## 85+ DevOps Concepts Explained in Layman's Terms: The Complete Beginner's Guide for 2026

DevFeed: [85+ DevOps Concepts Explained in Layman's Terms: The Complete Beginner's Guide for 2026](<https://devfeed.tech/articles/85-devops-concepts-explained-in-layman-s-terms-the-complete-beginner-s-guide-for-2026-109718.md>)

Original publisher: [Read original article](<https://blog.devops.dev/85-devops-concepts-explained-in-laymans-terms-the-complete-beginner-s-guide-for-2026-47918ae47519?source=rss----33f8b2d9a328---4>)

Author: Arvind Verma

Published: 2026-10-30T18:59:49Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [DevOps](<https://devfeed.tech/topics/devops.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [DevSecOps](<https://devfeed.tech/topics/devsecops.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>), [Continuous Deployment (CD)](<https://devfeed.tech/topics/continuous-deployment.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [aws](<https://devfeed.tech/tags/aws.md>), [beginner](<https://devfeed.tech/tags/beginner.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [concepts](<https://devfeed.tech/tags/concepts.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [git](<https://devfeed.tech/tags/git.md>), [gitops](<https://devfeed.tech/tags/gitops.md>), [guide](<https://devfeed.tech/tags/guide.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [linux](<https://devfeed.tech/tags/linux.md>)

### AI overview

The guide presents DevOps as coordinating code, infrastructure, networking, security, and monitoring so applications run reliably. It explains concepts through practical examples, from Linux, Git, networking, and scripting to Docker, Kubernetes, CI/CD, Terraform, cloud services, security, observability, and production troubleshooting. It distinguishes related tools and practices--for example, Helm packages Kubernetes resources while Kustomize applies overlays; Terraform manages infrastructure state while Ansible automates machine configuration; and metrics, logs, and traces reveal different aspects of system behavior. It recommends learning in stages: fundamentals, containers and Kubernetes, automation and cloud, security and observability, then production engineering. Examples also qualify operational limits: rollbacks may not reverse database changes, replicated data is not a backup, and retries need limits and backoff.

### Source excerpt

From Linux and Docker to Kubernetes, AWS, Terraform, DevSecOps, and Production Troubleshooting DevOps can look complicated when you first enter the field. You hear terms like Kubernetes, Terraform, CI/CD, observability, GitOps, and Infrastructure as Code, and it feels like you need to learn a hundred different technologies. But every concept exists to solve a particular problem. Think of an application as an online shopping website. Developers write its code, servers run it, networks connect it to users, databases store orders, security protects customer information, and monitoring helps the team identify problems. A DevOps Engineer helps these pieces work together reliably. Let's understand each concept in plain English. 1. Linux Fundamentals and System Administration Linux is an operating system, similar in purpose to Windows. It is widely used on cloud servers and in containerized environments. 1. Linux Fundamentals In simple terms: Learning how to use and manage a Linux computer through commands. You learn how to navigate folders, read files, inspect system information, and manage services. Example: Connecting to a cloud server and checking whether an application is running. 2. Shell Scripting (Bash / Python) In simple terms: Writing instructions that make a computer perform repetitive tasks automatically. Bash is commonly used for command-line automation. Python is useful for more complex scripts, data processing, and integrations. Example: Automatically checking disk space on 100 servers instead of checking each server manually. 3. Git and Version Control In simple terms: Git keeps a history of changes to your code and configuration files. It helps you see what changed, who changed it, and how to recover from unwanted changes. Example: A configuration update breaks a deployment. Git helps you identify and revert the change. 4. Networking Fundamentals In simple terms: Networking allows computers and applications to communicate with one another. It covers IP add

[Next page](<https://devfeed.tech/topics/devops.md?cursor=WyIyMDI2LTEwLTMwVDE4OjU5OjQ5KzAwOjAwIiwgIjU2MzU0ZDBkLTU0OTktNDM0ZC1iN2I4LWM5MjRiNDc4MjA5ZiJd>)