- 최신
- 최다 투표
- 가장 많은 댓글
Based on the situation you've described, here are some insights and recommendations:
-
TCP Socket Communication without SSL/Handshake: Yes, it is possible to set up plain TCP socket communication in AWS without SSL/Handshake. However, the issues you're experiencing suggest that your current configuration might be set up for HTTPS traffic.
-
ELB Configuration for TCP: When using an Elastic Load Balancer (ELB) for TCP traffic, you need to ensure it's configured correctly:
- Check if you're using a Network Load Balancer (NLB) instead of an Application Load Balancer (ALB). NLBs are designed to handle TCP traffic at the transport layer.
- Verify that the ELB listener is configured for TCP and not HTTPS.
- Ensure that the security groups associated with your ELB and EC2 instances allow the necessary TCP ports.
-
Health Checks: The ELB-HealthChecker/2.0 packets you're seeing are normal. Load balancers use these to verify if your instances are healthy. For TCP, you can configure a TCP health check instead of an HTTP one.
-
HTTP 400 Error: Receiving an HTTP 400 error suggests that somewhere in your stack, the traffic is being interpreted as HTTP. This could be due to:
- Misconfiguration of the ELB (e.g., using an ALB instead of an NLB)
- A web server running on your Windows Server that's intercepting the traffic
- Incorrect routing rules
- Additional Steps:
- Review the ELB type and configuration
- Check the Windows Server configuration to ensure no web server is unintentionally handling the traffic
- Verify network ACLs and security group rules
- Consider using AWS VPC flow logs to trace the path of your traffic
When communicating with your partner company, request:
- Confirmation of the ELB type (it should be a Network Load Balancer for raw TCP)
- Verification of the listener configurations on the ELB
- Review of security groups and network ACLs
- Confirmation that the Windows Server is not running any web server software that might intercept the TCP traffic
Remember, changing these configurations may require careful planning to avoid service disruptions. Always test changes in a non-production environment first if possible.
Sources
PERF04-BP05 Choose network protocols to improve performance - AWS Well-Architected Framework
PERF04-BP05 Choose network protocols to improve performance - AWS Well-Architected Framework
Networking 101 - Part 1 | AWS re:Post
PERF05-BP05 Choose network protocols to improve performance - AWS Well-Architected Framework (2023-04-10)
관련 콘텐츠
- 질문됨 일 년 전
- AWS 공식업데이트됨 8달 전
- AWS 공식업데이트됨 3달 전
- AWS 공식업데이트됨 3년 전