Spring Cloud微服务部署中的IP地址配置问题

Great question! Let's break this down based on whether you're deploying to AWS EC2 or ECS, since each has slightly different networking and service discovery considerations for your Spring Cloud stack (Zuul, Eureka, Hystrix).

For AWS EC2 Deployment #

Since EC2 is essentially a cloud-based virtual machine, the core idea is to replace localhost with reachable network addresses and lock down security properly.

1. Eureka Server Configuration #

• First, deploy your Eureka Server to an EC2 instance. Update its application.properties:

  # Replace <EC2_PRIVATE_IP> with your Eureka instance's private IP (use private IP for VPC-internal traffic, or Elastic IP if external access is needed)
  eureka.instance.hostname=<EC2_PRIVATE_IP>
  eureka.client.serviceUrl.defaultZone=http://<EC2_PRIVATE_IP>:8071/eureka/
  # Disable self-registration for standalone Eureka Server
  eureka.client.register-with-eureka=false
  eureka.client.fetch-registry=false
  

• Security Group Setup: Open port 8071 on the Eureka EC2 instance's security group, and restrict inbound traffic to only your other microservice instances (use their security group or VPC CIDR as the source).

2. Custom Microservice Clients #

Update their application.properties to point to the Eureka Server's EC2 address:

eureka.client.serviceUrl.defaultZone=http://<EC2_PRIVATE_IP>:8071/eureka/
# Critical for EC2: Register client IP instead of hostname (hostnames may not resolve reliably)
eureka.instance.preferIpAddress=true

3. Zuul Proxy & Turbine Dashboard #

• For Zuul:

  eureka.client.serviceUrl.defaultZone=http://<EC2_PRIVATE_IP>:8071/eureka/
  server.port=8090
  

  • Open port 8090 in Zuul's EC2 security group (allow inbound from an Application Load Balancer (ALB) or your test external IP).
• For Turbine Dashboard:

  eureka.client.serviceUrl.defaultZone=http://<EC2_PRIVATE_IP>:8071/eureka/
  server.port=8091
  turbine.app-config=<YOUR_MICROSERVICE_NAMES>
  

  • Open port 8091 in Turbine's security group (allow inbound from your admin IP or ALB for remote access).

Key EC2 Notes #

• Keep all services in the same VPC for private, low-latency communication. Avoid public IPs for internal traffic unless necessary.
• Use Elastic IPs for Eureka/Zuul/Turbine if you need stable public addresses (EC2 instances get dynamic public IPs on restart by default).

For AWS ECS Deployment #

ECS is a container orchestration service, so we'll leverage container networking and ECS Service Discovery instead of hardcoding IPs—this is more scalable and resilient for microservices.

1. Eureka Server Setup #

• Package your Eureka Server into a Docker image, then deploy it as an ECS Service.
• Enable ECS Service Discovery: Create a private Route 53 DNS namespace for your ECS cluster, then link it to the Eureka service. This gives you a stable domain like eureka-service.<your-namespace>.local.
• Update Eureka's configuration (use environment variables for flexibility instead of hardcoding):

  eureka.client.serviceUrl.defaultZone=http://eureka-service.<your-namespace>.local:8071/eureka/
  eureka.instance.preferIpAddress=true
  eureka.client.register-with-eureka=false
  eureka.client.fetch-registry=false
  

2. Microservice Clients, Zuul & Turbine #

For all other services, point their Eureka endpoint to the Service Discovery domain:

eureka.client.serviceUrl.defaultZone=http://eureka-service.<your-namespace>.local:8071/eureka/
eureka.instance.preferIpAddress=true

• ECS Task Definition: Map container ports (8090 for Zuul, 8091 for Turbine) to host ports (EC2 launch type) or use an ALB for port routing (Fargate launch type, which doesn’t expose host ports directly).
• ALB Integration: Create an ALB to expose Zuul and Turbine externally, with listener rules routing traffic to the respective ECS services.

Key ECS Notes #

• Use Fargate for serverless deployment (no EC2 instance management) if your traffic is variable.
• Store sensitive configs (like Eureka auth credentials) in AWS Secrets Manager or Parameter Store, then inject them as environment variables in ECS tasks.
• Restrict security groups: Allow Eureka port 8071 only for other ECS services, and Zuul/Turbine ports only for the ALB.

General Best Practices #

• Profile-Based Configs: Use Spring Profiles (application-dev.properties, application-prod.properties) to separate local and cloud settings. Activate the prod profile in AWS via spring.profiles.active=prod (set as an environment variable or command-line argument).
• Avoid Hardcoding: Never use fixed IPs/domains—rely on service discovery or environment variables instead.
• Health Checks: Configure Spring Boot Actuator's /actuator/health endpoint, and link it to ECS/EC2 health checks to auto-replace unhealthy instances.

内容的提问来源于stack exchange，提问作者Mr.DevEng