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

Requests from static IP getting slow from AWS

0

We have obtained static IP through our internet service provider for connecting to our secure client server as per their data security requirement. But our application development and hosting is happening on AWS. AWS is slowing down the incoming request coming from this static IP. Is AWS blacklisting the request coming from static IP. Please help resolving this issue.

    1. May I know how you are connecting to your application that is hosting on AWS from a static IP ?       Ans: - we have hosted our application on internal port of ec2 instance and serving with nginx on port 80 with reverser proxy.

    2. Are you using any VPN connection/Direct Connect ?       Ans: Direct connection

    3. Are you connecting directly over the internet ?       Ans:- Yes

    4. Are you trying to connect to your application via FQDN ? Ans :- Yes domain name ndd.roadathena.com

    5. If so, please run "nslookup <domain name>" on your source machine to validate DNS query time. Ans :- > ndd.roadathena.com ;; communications error to 172.27.208.1#53: timed out Server: 172.27.208.1 Address: 172.27.208.1#53

    Non-authoritative answer: Name: ndd.roadathena.com Address: 3.108.214.58

    1. mtr -n -c 10 -T -P <port number of application> <ip address> Ans:-
asked a year ago282 views
1 Answer
0

Hi Manav,

May I know how you are connecting to your application that is hosting on AWS from a static IP ?

  • Are you using any VPN connection/Direct Connect ?
  • Are you connecting directly over the internet ?
  • Are you trying to connect to your application via FQDN ? If so, please run "nslookup <domain name>" on your source machine to validate DNS query time. This will help rule out any latency issues with DNS query times.

Please be aware that AWS doesn't block any IP unless it is blocked in NACl's/SG's/OS level

Since you mentioned that you are seeing slowness with the application response, please validate the following -

  1. run bi-directional tcp based mtr - ### Command ### "mtr -n -c 10 -T -P <port number of application> <ip address>" The above command works only on linux machine. If your source/AWS machine is windows based, please install winMTR and run TCP based tests. This test will help rule out any latency/packet loss issues with the TCP connection.
  2. Please run iperf tests which will help rule out any network related throughput issues.
AWS
answered a year ago
profile picture
EXPERT
reviewed 8 months ago
    1. May I know how you are connecting to your application that is hosting on AWS from a static IP ?       Ans: - we have hosted our application on internal port of ec2 instance and serving with nginx on port 80 with reverser proxy.

    2. Are you using any VPN connection/Direct Connect ?       Ans: Direct connection

    3. Are you connecting directly over the internet ?       Ans:- Yes

    4. Are you trying to connect to your application via FQDN ? Ans :- Yes domain name ndd.roadathena.com

    5. If so, please run "nslookup <domain name>" on your source machine to validate DNS query time. Ans :- > ndd.roadathena.com ;; communications error to 172.27.208.1#53: timed out Server: 172.27.208.1 Address: 172.27.208.1#53

    Non-authoritative answer: Name: ndd.roadathena.com Address: 3.108.214.58

    1. mtr -n -c 10 -T -P <port number of application> <ip address> Ans:-

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions