Microservice tasks scale in and out, so their IP addresses change.
Clients must connect to currently available tasks by service name.
Which service is most appropriate?
Register services and instances in AWS Cloud Map so clients can discover changing task locations by service name.
Detailed explanation
S3 does not provide service registration or health-aware discovery.
S3 does not provide service registration or health-aware discovery.
Cloud Map registers service names with instance locations and status to support dynamic discovery.
Cloud Map registers service names with instance locations and status to support dynamic discovery.
A KMS key ID is not a service-discovery registration or name-resolution record.
A KMS key ID is not a service-discovery registration or name-resolution record.
Task replacement and scaling make hard-coded addresses stale.
Task replacement and scaling make hard-coded addresses stale.
Check official documentation
Compare the following points with the official documentation.
AWS Cloud Map service discoveryの公式説明を確認する。
What to confirm
動的なコンテナサービスの接続先をサービス名から発見できる。
Key points
- AWS Cloud Map
- Service discovery
- Instance registration
Notes
- Environment: AWS公式Cloud Mapドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Dynamic endpoints
Scaling and replacement require discovery data to be updated with the task lifecycle.
Health-aware access
Discovery can be combined with health information so clients avoid unusable instances.