By using AWS re:Post, you agree to the Terms of Use

Questions tagged with Monitoring

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Slowness within the AWS (EC2 and Workspaces) in Internet browsing itself, sometimes almost impossible to access a simple website.

Hello, We are experiencing browsing internet related slowness within the AWS (EC2 and Workspaces), browsing in simple websites itself is slow. We had the same problem on 03/2022, we hired support business, but they didn't solve the problem and it went back to normal on its own. Monitoring via CloudWatch, we noticed that the slowness is related to the NAT Gateway, as the documentation says the following: "If the value of ConnectionEstablishedCount is less than the value of ConnectionAttemptCount, clients behind the NAT gateway tried to establish new connections for which there was no response." And as you can see in the attached graphs, whenever there is a slowdown, the ConnectionEstablishedCount metric is lower than the ConnectionAttemptCount metric ![Enter image description here](/media/postImages/original/IMC0Zk8ExYSuC6nJVZkwPIWw) Internet browsing itself is slow, sometimes almost impossible to access a simple website, and this is directly impacting our internal use and customer service, as all our internal and support applications require the internet. It is also worth mentioning that we migrated our entire On-Premise structure to AWS in October/2021, and this is the second time this has happened. We even set up a new NAT Gateway in another AZ but it didn't work and it was still slow. Today we have 6 EC2 servers and 20 Workspaces in the same VPC and using the same NAT Gateway, and at night I transfer backups from EC2 to S3. Has anyone ever experienced this? Do you know what it could be and how to fix it? Thanks
1
answers
0
votes
22
views
asked a month ago

Slowness within the AWS (EC2 and Workspaces) in Internet browsing itself, sometimes almost impossible to access a simple website.

Hello, We are experiencing browsing internet related slowness within the AWS (EC2 and Workspaces), browsing in simple websites itself is slow. We had the same problem on 03/2022, we hired support business, but they didn't solve the problem and it went back to normal on its own. Monitoring via CloudWatch, we noticed that the slowness is related to the NAT Gateway, as the documentation says the following: [*"If the value of ConnectionEstablishedCount is less than the value of ConnectionAttemptCount, clients behind the NAT gateway tried to establish new connections for which there was no response."*](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway-cloudwatch.html) And as you can see in the attached graphs, whenever there is a slowdown, the ConnectionEstablishedCount metric is lower than the ConnectionAttemptCount metric ![Enter image description here](/media/postImages/original/IM4BtTaWe7TFqUgYfQiDmSsA) Internet browsing itself is slow, sometimes almost impossible to access a simple website, and this is directly impacting our internal use and customer service, as all our internal and support applications require the internet. It is also worth mentioning that we migrated our entire On-Premise structure to AWS in October/2021, and this is the second time this has happened. We even set up a new NAT Gateway in another AZ but it didn't work and it was still slow. Has anyone ever experienced this? Do you know what it could be and how to fix it? Thanks
1
answers
0
votes
69
views
asked a month ago

RDS: Difference between RX and NetworkReceiveThroughput?

I was analyzing the network performance of the Database we have on RDS, which has enhanced monitoring turned on. I am confused with two metrics (one from enhanced monitoring, another from CloudWatch), that theoretically mean the same, but are showing different values. For a given time range, 'RX' graph under Enhanced Monitoring says that 3.27 GiB (approximately). And according to the [AWS documentation](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Monitoring-Available-OS-Metrics.html), RX means "The number of bytes received per second.". ![RDS-Console-RX-Value-In-GiB](https://repost.aws/media/postImages/original/IMrOSJwCBaQ9uAoZEfHjNf_Q) But for the same time range, if you plot 'NetworkReceiveThroughput' in CloudWatch, I see 3.6 million bytes per second (approximately), which is close to 3.6MB per second. And if you look up the [documentation](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-metrics.html) on this term, it says "The incoming (receive) network traffic on the DB instance, including both customer database traffic and Amazon RDS traffic used for monitoring and replication." ![CloudWatch-NetworkReceiveThroughput-Bytes-per-Second](https://repost.aws/media/postImages/original/IMN-ChqNTKQdiG7DZDA0GrEw) Though NetworkReceiveThroughput is slightly different from RX since it includes AWS internal traffic that transmits monitoring data as well, I should have seen a higher value than RX in my case. Why are these values different by a huge margin? What am I getting wrong?
1
answers
0
votes
69
views
asked 2 months ago