ECS Fargate + Service Discovery + ALB
A customer wants to use ECS Fargate to run tasks with AWS Service Discovery front-ended by an ALB (to manage scaling and TLS). In testing, Service Discovery bypasses the ALB and just sends requests to the tasks.
Is the Service Discovery -> ALB pattern just not supported? They're trying to avoid deploying something else to manage (Consul for example).
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Service Discovery is an alternative to ALB, and makes use of Route 53 hosted zones. As new tasks are started, they are automatically registered into the Route 53 hosted zone under the 'friendly' service name, and other services can then use this name when contacting their dependencies.
ALB can be used either simple to balance incoming traffic from customers to your first tier of services, or as an alternative to Service Discovery by providing your applications with a DNS endpoint to use when they need to contact their dependencies.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 9 Monaten