Building and running Spring Cloud-based microservices on AWS ECS
summary
A Spring Cloud microservices stack runs in Docker on AWS ECS using Terraform for infra, CircleCI for CI and ECR for images; service discovery initially uses Consul service registration using EC2 host IP addresses and port numbers (requires querying EC2 metadata and ECS container metadata) and later moves toward internal ALBs and Route 53 service discovery. A custom Spring Cloud PropertySource integrates with AWS Parameter Store for encrypted secrets, and centralized logging/tracing uses Logback, logs.io and Sleuth; the setup works but exposes ECS networking and scaling quirks.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 2:45Architecture
- 4:29Project Setup
- 7:45Technology
- 11:17Expectations
- 12:43How ECS Works
- 13:31Scaling ECS vs EC2
- 19:21ECS Networking
- 21:16Discover Host
- 22:21Discover Port Binding
- 23:54Configuring Consul Instance ID
- 27:09AWS Systems Manager Parameter Store
- 28:06Spring Cloud Parameter Store support
- 28:43Spring Cloud Config Clients
- 29:39Implementing Parameter Store Support
- 30:49Wrapping up
- 32:07Health Checks in ECS
- 33:11AWS Advancements
- 35:40AWSVPC Small Print
- 36:39ECS Service Discovery
- 37:24Ribbon & Server-side Load Balancing
- 38:13Ribbon & Zuul Configuration
- 41:57Distributed Tracing
- 42:47SLF4J MDC Integration
- 43:09Brave vs. AMZN Trace IDs
- 44:31Bootstrap Logging
- 45:16Conclusion
- 46:57Bonus: shared HTTP client config
related talks
43mSpring Boot with the Amazon Web Services SDK: Interacting with Core Services
52mBuilding a typical Spring Cloud architecture application
32mDeploying TeamCity Cloud as a Service on AWS: Lessons Learned
15mHow to scale your app in minutes with container and AWS ECS
53mBooting your micro-services architecture with Spring and Netflix
39mExperiences and Lessons Learned Building a Multi-Cloud Spring Boot Backend
49mSpring Cloud *: Exploring Spring Cloud Implementations
54mRapid Development with