Reachability analyzer with boto3 result in throttling errors from ELB

0

Whenever I tried to create multiple network path insights, for example, 3 sources and each targets to 3 destinations (9 possible permutations), I would get "The request failed due to throttling errors from Elastic Load Balancing." in the response of "describe_network_insights_analyses".

I've tried A) from "Instances" (source type) to "Instances" (destination type) and B) from "Instances" (source type) to "Network Interfaces" (destination type) All resulted in throttling errors as described above.

These are the APIs we use:

Can someone advise any strategy for testing network paths involving NLB without hitting the throttling errors?

Gilbert
asked 9 months ago250 views
1 Answer
0

Hello there,

Thank you for reaching out to us.

I understand that you would like to know what is the strategy for testing network paths which involve NLB without facing throttling errors.

Firstly to mention there is no specific best practice here. You can test the IPs of the NLB as its the first node the request will reach and only then the target backend.

The 3 APIs which you have shared with us are EC2 API references and they would need more looking into from a backed perspective as to why it could have throttled.

  1. We will need details like the complete Cloud trail ERROR to further troubleshoot this issue which you are facing.
  2. We will need to look into the Event ID for the Cloud trail.
  3. Also I would suggest you to check Cloud trail to see if there are any parallel API calls running simultaneously, which might be causing this issue.

Having said that, I would like to share with you this Limit Documentation of Reachability Analyzer : https://docs.aws.amazon.com/vpc/latest/reachability/reachability-analyzer-limits.html

Hence, to have a more clearer understanding to this issue and troubleshoot further, we require details that are non-public and account specific information. Please open a support case with AWS using the following : https://console.aws.amazon.com/support/home#/case/create

Thank you!

AWS
SUPPORT ENGINEER
Sagar_T
answered 9 months ago

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