- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
It would be (quite!) difficult to avoid using the Amazon backbone network when communicating between regions.
VPC peering is definitely the lowest latency connection type that you can use; the additional latency you're experiencing is probably due to AWS encrypting all traffic between regions.
If you moved to using public IP connectivity (by putting an Internet Gateway in each VPC and communicating using Elastic IPs in each region) the traffic would still use the AWS backbone (this is called out in VPC FAQ). It's the same network with the same performance characteristics.
Given that the communication you're doing is between two EC2 instances (in separate regions), services such as CloudFront and Global Accelerator are not appropriate here as they are more for internet-based clients connecting to your applications in AWS. Direct Connect is also not a useful service as that is for private connectivity from on premises networks to AWS.
If you are experiencing packet loss and latency above what you'd expect, I strongly encourage you to create a support case so that the network team can troubleshoot this with you.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
thanks a lot for your response, i am trying to mitigate the jitter cause indeed unsuccessfully It does not seem like decryption latency because it is not a constant latency rather then a jitter as you can see in the plot i added to the question
i also tried to see if the jitter is a cause of packet loss but thats also does not seem the cause we are now working to be able to open a support case thanks!