AWS re:Invent 2025 - New Era of Platform Engineering – Agentic AI-Powered Self-Service (AIM359)

Source: Dev.to

Overview

AWS re:Invent 2025 – New Era of Platform Engineering – Agentic AI‑Powered Self‑Service (AIM359)

In this session, Ruslan Kusov, Cloud COE Director at SoftServe and AWS Ambassador, explains how platform engineering is evolving with agentic AI integration. He describes SoftServe’s adaptive modernization framework built on AWS services such as EKS, ECS, and Lambda, and emphasizes customizable integration interfaces over one‑size‑fits‑all solutions.

Key highlights

• ADQ (AI‑driven enhanced engineering with Amazon Q) – combines self‑service platforms, AI agents, Amazon Bedrock, and MCP servers to automate end‑to‑end SDLC processes.
• A live demo of migrating on‑premises Java applications to AWS using containerization and managed services, showing how AI‑powered self‑service enables re‑platforming and re‑architecture at lift‑and‑shift costs while achieving 2–3× faster migration times with minimal cloud expertise.

This article is auto‑generated from the original presentation; minor typos or inaccuracies may be present.

Platform Engineering Fundamentals: From DevOps to the Adaptive Modernization Framework

Introduction

“Hi everyone, I’m Ruslan Kusov, Cloud COE Director at SoftServe, AWS Ambassador… today I’ll talk about a new era of platform engineering powered by agentic AI and self‑service.”

From DevOps to Platform Engineering

• DevOps introduced tools, people, and processes to help developers deliver software efficiently.
• Over time, organizations moved toward Internal Developer Platforms (IDPs)—self‑service platforms that standardize tooling and reduce operational overhead.

Adoption Landscape

Research (including data from Red Hat) shows:

• 85 % of customers are moving toward platform engineering.
• 18 % have advanced implementations, 14 % are exploring, and 27 %–41 % are in various intermediate stages.

Typical Journey Timeline

• From initial exploration to a mature platform engineering practice typically takes ~2 years.
• The journey is highly contextual: organizational culture, existing processes, and current tooling all influence the path.

SoftServe’s Adaptive Modernization Framework

Instead of prescribing a commercial platform, SoftServe built a framework that can be tailored to each organization’s needs.

Key principles

1. Core AWS services – EKS, ECS, Lambda (microservices‑centric).
2. Complementary components – runtime, observability, security, CI/CD, storage, databases, third‑party services.
3. Internal Developer Portal (IDP) – the unified interface for developers to interact with the platform.

Integration Interfaces

• Design integration drivers that abstract underlying services.
• Example: Switch from HashiCorp Vault to AWS Secrets Manager by updating the driver—no code changes required.

This approach underpins the Adaptive Modernization Platform (a framework, not a monolithic product).

Blueprint Architecture

• Leverages EKS Blueprints (Kubernetes reference architecture).
• Multi‑AZ clusters with critical and worker node groups.
• Uses Karpenter (instead of the default auto‑scaler) for efficient scaling.