← Financial Cloud Cloud Cloud Club · Amarathon 2025 Recap

Vertex Macro|Financial Cloud Cloud · AWS Amarathon 2025

Vertex Macro|Amarathon 2025 Recap 31:Connecting the World Through Open Source: Practical Journey of Technology, Community and Global Developer Relations

Speaker: Richard Lin

Session: 31

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

Open source

● Open source is characterized as a cross-border collaboration method rather than a mere technical option.

● Engineers from different parts of the world can become collaborators through open source, despite never having met.

● For hackers, open source represents a shared journey and a means to contribute to a collective effort.

● For commercial projects, open source signifies an opportunity to engage with a global community and enhance product-market fit.

● The globalization of technology is driven by reputation, relationships, and trust, emphasizing "actions speak louder than words."

● The concept of "Community Over Code" highlights the importance of long-term community building.

● Developers are influenced more by neutral, transparent, and credible sources rather than marketing efforts.

● Free access is a critical factor in the success and adoption of open source projects.

● A truly open source project allows for global participation by strangers, making it inherently international.

● Open source is presented as an invitation to collaborate on building the future, combining technical transparency, clear governance, and low barriers to participation.

● The discussion questions whether community size is more important than community structure in the context of growth and governance.

● The acronym M (Market Demand) signifies unmet needs, while P (Product/Service) indicates a lack or mismatch of existing solutions.

● PMF (Product-Market Fit) is crucial for initiating or engaging in open source projects to address demand.

● The combination of PMF and open source creates a flywheel effect, leading to increased market share.

● Acknowledging one's position as "no one" in the market can lead to omnipotence through open source contributions.

● Community adoption is driven by PMF rather than mere numbers, and community productivity is a result of structure, not size.

● The value of 30 core contributors is emphasized over 3000 passive spectators in the context of open source projects.

An open source contribution starter roadmap is provided with the following steps

● Identify an open source project of interest to participate in.

● Fork the project and set it up to run locally.

● Ensure a genuine interest and willingness to invest in the chosen project.

● Begin contributing with minor modifications such as bug fixes, documentation enhancements, comment optimizations, and submitting Pull Requests.

● Verify the project's open source license and understand its contribution rules, as different licenses may have varying requirements.

● Gain an understanding of the project's background and structure by reading the README, documentation, and contribution guidelines.

● Create a GitHub account and become comfortable with its basic functionalities.

● Be open to feedback and willing to make changes based on community suggestions.

● Keep the forked project and the main repository in sync by regularly updating with the latest changes from the upstream project.