← Financial Cloud Cloud Cloud Club · AWS Re:cap

Vertex Macro | Financial Cloud Cloud · AWS Re:cap

AWS Re:cap 11: Build New Modern Apps on AWS

Speaker: Tim Tong

Session: 11

Session
Summit Dev Lounge2026 Re:cap
01 Encode Architecture as Steering for AI Agents
02 Agent Harness Is the Real Engineering Moat
03 Ask Observability Data in Plain Language
04 Serverless AR Game with Bedrock AgentCore
05 Multi-Agent Quant Backtesting on AgentCore
06 Blog to Slides in Three Minutes with Kiro
AWS Community Day Hong Kong 2025 Re:cap
02 AWS Compliance with Terraform
03 Beginner to Builder An AWeSome Cloud Journey
04 Team-First Serverless Engineering with Laravel & Bref
05 Event Opening - AWS Community Day Hong Kong 2025
06 Agent-to-Agent: Building Interoperable AI on AWS
07 Utilize another telemetry data for faster improvement with AI agent
08 Graduating from Vibe Coding: Spec-Driven Development with Kiro
09 Automated Testing using MCP & AI Agents
10 Modernizing Telecom Security ML Powered Approach
11 Rethinking GenAI Agent: RAG & MCP
12 Disaster and Emergency Response with TAK and AWS
13 Rethinking Serverless Application Workflows from a Testing Perspective
14 Practical AWS FinOps for Cloud Success
15 AI-Powered Global Pure-Alpha Macro Trades on AWS: Revolutionizing Risk-Adjusted Asset Returns
FSI Recap
01 Modern Trade Lifecycle: Trading to Settlement
02 Goldman Sachs: Fast Track your applications onto Cloud - AWS Re:cap Q1/2023
03 Zurich Insurance Group: Building an Effective Log Management Solution on AWS
04 FSI Meetup 2025 Q4 - Brex Database Disaster Recovery
05 FSI Meetup 2025 Q4 - A Graviton Migration Success Story
06 FSI Meetup 2025 Q4 - Stifel Modern Data Platform
07 FSI Meetup 2025 Q4 - Financial Transaction Data Reconciler PayPal
08 FSI Meetup 2025 Q4 - Scaling Resilience
09 Maximizing AI Inference Cost Efficiency: Strategic Adoption of AWS GPU Instances
10 Advanced Agentic AI Design Patterns
11 Build New Modern Apps on AWS
AWS re:Invent 2025
01 Coinbase re:Invent Recap (IND3312)
02 Building the Future Trading Platform Leveraging AI and AWS
03 Trading Innovation: Jefferies' AI Assistant on Amazon Bedrock (IND3315)
04 How FSI Revolutionized HFT Analytics with Agentic AI (GBL302)
05 Improving Distributed Systems with Amazon Time Sync Featuring Nasdaq
06 Amazon Aurora HA and DR Design Patterns for Global Resilience (DAT442)
07 Building Agentic AI: Amazon Nova Act and Strands Agents in Practice (DEV327)
08 Deep Dive into Amazon Aurora and Its Innovations (DAT441)
09 Deep dive on Amazon S3 (STG407)
10 Nasdaq: Build Resilient Infrastructure for Global Financial Services (HMC327)
11 What's New with AWS Lambda (CNS376)
12 Spec-Driven Development with Kiro (DEV314)
13 Amazon's finops: Cloud cost lessons from a global e-commerce giant (AMZ308)
14 Tick to trade latency trading platforms on aws
Government data
01 The AI Era: The Boundary Between Development and Design Is Disappearing
02 On-Device Multimodal AI and Smart-City Practice
03 Large-Model Capability Evaluation and a Method for Landing AI Projects
04 Controlled End-to-End Automation of Government Development with Cloud Agents
05 A New Software Ecosystem for the Agent Era, Seen Through Multi-Agent Systems
06 AI-Driven Macro Quantitative Research and Smart Governance
07 Authorized Operation of Public Data and Smart-Government Practice
08 Putting Data Assetization into Practice: Rights, Compliance, Engineering Governance, and Digital-Government Cases
09 AI for Mental-Health Public Welfare: Governance, Architecture, and Practice of a Trustworthy Platform
Amarathon 2025 Recap
01 A Developer’s Roadmap to Architecting for Agents
02 Amazon Bedrock Data Automation
03 Multi-Agent on AgentCore
04 Building Agentic AI Nova Act and Strands Agents in Practice
04 Accelerating Migration Projects with Kiro using Spec-Driven Development
06 From Matching to Understanding: Personalized AI Search Practice Driven by AgentCore Memory
07 Observe to Optimize – LLM Observability to AIOps Turning real-time insights into intelligent automation
08 Deploying TEAM and Building the Best Engineering Team
09 Five Hard Lessons from Five Years of So-Called Serverless Databases
14 What if AI does my job How Q Developer CLI and Kiro have changed my daily routine
16 Velocity with Vigilance: Security Essentials for Amazon Bedrock Agent Development
26 Run OSS LLMs on a Single H100 Smarter, Cheaper, Faster
28 A Modern Unified Metadata Architecture: New Approaches to Breaking Down Data Silos
29 Serverless MediaOps: Automating Video Workflows with AI on Amazon Web Services
30 Architecting for Efficiency and Reliability with Performance Testing at Scale
31 Connecting the World Through Open Source: Practical Journey of Technology, Community and Global Developer Relations
33 Building Streaming Iceberg Tables for Real-Time Logistics Analytics
34 Accelerating Large-Scale Robot Strategy Training: An Automated Closed-Loop Architecture Based on Kiro, Trainium, and EKS
35 From Vibe to Viable with spec driven development
36 Making Cloud Cost Analysis Smarter: Building FinOps Intelligent Agents with Strands and AgentCore
37 Transform Conversational Agentic AIOps for K8s Using CNCF Kagent, K8sGPT, and Nova Sonic

@ AWSome Day Hong Kong 2025

This session explained what makes an application modern, why organizations modernize, and how AWS container, serverless, developer, and observability services support that journey. It also compared serverless and Kubernetes operating models and presented practical starting points for modernization.


What Is a Modern Application?

Modern applications combine:

● Modern technologies.

● Modular architectures.

● Agile software delivery practices.

● Automated operational processes.

Together, these capabilities help teams deliver customer value more quickly, frequently, reliably, and consistently.


Why Customers Build Modern Applications

Growth and Innovation:

● Reach the market faster.

● Enter new markets.

● Increase capacity to meet customer demand.

Scalability and Agility:

● Stay ahead of competitors.

● Release features and security patches faster.

● Increase customer loyalty and reduce churn.

Efficiency and Cost Optimization:

● Reduce operational inefficiencies.

● Lower infrastructure and licensing costs.

● Improve resource utilization.


What Drives Modern Application Success?

Organizational Foundations:

● Build a culture of innovation.

● Focus engineering effort on business differentiators.

Application Models:

● Containers.

● Serverless computing.

Supporting Infrastructure:

● Storage and data.

● Networking.

● Compute.

● Infrastructure orchestration.


Modern Application Components

Modular Architecture Patterns:

● Microservices.

● Containers and serverless functions.

Agile Developer Processes:

● DevOps.

● Continuous integration and continuous delivery.

● End-to-end security.

Serverless Operational Models:

● Event-driven architectures.

● Automated IT operations.


Approaches to Building Modern Applications

Serverless Operational Model:

● Automates infrastructure through AWS APIs.

● Supports autonomous development teams.

● Abstracts and simplifies infrastructure.

● Requires less infrastructure management.

● Can provide the lowest total cost of ownership for suitable new applications.

Kubernetes Operational Model:

● Automates infrastructure through Kubernetes APIs and tooling.

● Often uses a central platform team.

● Supports internal developer platforms.

● Provides flexibility, portability, and customization.

● Benefits from a broad open-source ecosystem.

Many organizations use both models and select the right one for each workload.


Reducing Operational Overhead

Modern managed services reduce the effort required for:

● Capacity planning and scaling.

● Software installation and maintenance.

● Infrastructure provisioning.

● Security and network configuration.

This allows development teams to spend more time on:

● Application code.

● Data-source integrations.

● Features that differentiate the business.


Modern Software Delivery on AWS

Application Authoring:

● Developers manage application code.

● AWS IDE Toolkits, Visual Studio Code, IntelliJ IDEA, and AWS CodeArtifact support development workflows.

Source and Artifacts:

● Amazon Elastic Container Registry and Amazon ECR Public store and distribute container images.

Build:

● AWS CodeBuild provides managed build capacity.

Test:

● AWS CodeBuild can run automated tests.

● Third-party tools can be integrated, including GitLab, CircleCI, Jenkins, Travis CI, SonarQube, Prometheus, and Grafana.

Deploy:

● AWS CodeDeploy supports managed deployments.

● Deployment workflows can also integrate with GitLab, Spinnaker, and Argo CD.

Monitor:

● AWS X-Ray and Amazon CloudWatch provide tracing, metrics, logs, and operational visibility.

● Prometheus, Grafana, Container Insights, and OpenTelemetry can extend observability.


What Customers Are Building

Consumer-Facing Applications:

● Web and mobile applications.

● Interactive websites.

● Mobile games.

● Ecommerce applications.

● Telehealth services.

Generative AI:

● Chatbots, virtual assistants, and personalization.

● Applications that integrate with and invoke foundation models.

● Model training and inference workloads.

Data Processing:

● Media streaming.

● Fraud detection.

● Object tracking and sensor fusion.

● Autonomous vehicle and advanced driver-assistance simulations.

● Internet of Things and robotics workloads.

IT Automation:

● Standardized developer platforms.

● Application integrations.

● Workflow automation.


Industry Applications

Financial Services:

● Consumer and mobile banking.

● Trading and exchange platforms.

● Risk and financial modeling.

Healthcare and Life Sciences:

● Patient-care applications and portals.

● Remote-care systems.

● Payment and claims processing.

● Image and data processing.

● Genomic sequencing.

Media, Entertainment, and Games:

● Direct-to-consumer streaming.

● Broadcasting.

● Mobile games.

● Virtual reality platforms.

Software and Internet Independent Software Vendors:

● Customer-facing products and services.

● Multi-tenant applications.

● AI applications.

● Media and data streaming.


Why AWS for Modern Applications?

● AWS offers a broad set of container and serverless compute services.

● More than 1.5 million customers use AWS database, analytics, machine learning, container, or serverless services.

● AWS provides a deep set of cloud security tools.

● AWS supports 143 security standards and compliance certifications.

● More than 200 cloud-native services are available to help modernize development, operations, applications, and business processes.


Common Modernization Challenges and Solutions

Challenge:

● Developers wait days or weeks for infrastructure.

Modern Approach:

● Developers provision infrastructure on demand and deploy in minutes.

Challenge:

● Software is deployed manually and inconsistently.

Modern Approach:

● Continuous delivery pipelines automate software delivery.

Challenge:

● Security is configured separately for each application.

Modern Approach:

● Security best practices are built into every application and service.

Challenge:

● Developers lack visibility into production systems.

Modern Approach:

● Applications are instrumented to collect metrics, traces, and logs.

Challenge:

● Teams and business units use inconsistent tools.

Modern Approach:

● Organizations standardize tools, platforms, and engineering practices.


Modernization Is a Journey

Application modernization is commonly a two- to three-year journey across the application estate:

1. Assess the application landscape.

2. Build new modern applications while managing legacy and migrated systems.

3. Modernize more of the existing application portfolio.

4. Continue optimizing cloud-native applications.

Over time, this journey should:

● Reduce the cost of IT.

● Increase business velocity.

● Improve the percentage of the application estate using modern practices.


Modernization Pathways

Organizations can streamline modernization by moving toward:

● Cloud-native architectures.

● Managed databases.

● Open-source technologies.

● Modern DevOps practices.

● Modern analytics platforms.


Where to Start

Technical Signals:

● Technology is old or no longer supported.

● Applications have performance or scalability problems.

● Required skills or institutional knowledge have been lost.

● The codebase has too many defects or tightly coupled "spaghetti code."

● Integration is expensive and difficult.

Business Signals:

● The application is critical to business success.

● It directly serves customers.

● It has a significant effect on revenue.

● It provides market differentiation.

● Its expected value exceeds the modernization cost.

The best starting point is usually an application with both a clear technical need and meaningful business value.


Customer Example: BILL

Challenge:

● BILL needed to accommodate growth and scale over time.

● Its on-premises platform architecture constrained speed and efficiency.

Solution:

● BILL refactored its infrastructure using Amazon Elastic Container Service and AWS Fargate.

● The architecture improved elasticity.

● AWS took on more server-management responsibility.

● Development teams gained more time for growth and innovation.

Outcome:

● Significant reduction in operational costs.

● Capacity to handle approximately 150,000 to 200,000 requests per minute.

● New environments could be created within weeks instead of months.

● Developer productivity improved through better tools.


Key Takeaways

● Modern applications combine modular architecture, agile delivery, security, automation, and observability.

● Serverless and Kubernetes are complementary operating models that suit different workload and organizational needs.

● Managed AWS services reduce infrastructure work and allow teams to focus on business value.

● Modernization should be treated as an incremental journey rather than a one-time migration.

● Organizations should prioritize applications where technical pressure and business value intersect.

● Standardized delivery pipelines, built-in security, and production observability are central to sustainable modernization.