Pattern steps with logic that calls AWS API might return "Status: 400 - Throttling - Rate exceeded" error - Known Error

Pattern steps with logic that calls AWS API might return "Status: 400 - Throttling - Rate exceeded" error Description During discovery, our patterns are making call to AWS API. Example: "Amazon AWS application ELB service" pattern. In this pattern, the steps that call AWS API might failed and return the following error: ==== Cloud request failed. URL: https://elasticloadbalancing.eu-west-1.amazonaws.com/?Action=DescribeLoadBalancers&Version=2015-12-01 Status: 400 Response: {"Error":{"Code":"Throttling","Message":"Rate exceeded","Type":"Sender"},"RequestId":"7a40cc00-d238-4e15-af42-95d8453fbb95"} (script_include:AwsApiCommand; line 137). Custom operation Failed to run script due to the following error: JAVASCRIPT_CODE_FAILURE: com.snc.sw.exception.CommandFailureException: Cloud request failed. URL: https://elasticloadbalancing.eu-west-1.amazonaws.com/?Action=DescribeLoadBalancers&Version=2015-12-01 Status: 400 Response: {"Error":{"Code":"Throttling","Message":"Rate exceeded","Type":"Sender"},"RequestId":"7a40cc00-d238-4e15-af42-95d8453fbb95"} (script_include:AwsApiCommand; line 137) ==== This is because the amount of requests we fired during scheduled discovery might exceeded the quota in AWS. Our logic should handle this exception and retry the AWS API call.

Steps to Reproduce

Install Discovery and Service Mapping plugin. 2. Create Service Map for application that hosted on Amazon AWS and has elastic load balancer service as part of it. 3. Run discovery on the service map and observe the "Amazon AWS application ELB service" pattern log. 4. Check the steps where pattern making a call to AWS API. In a big number of ELB service, there might be some that results in ---- Status: 400 Response: {"Error":{"Code":"Throttling","Message":"Rate exceeded" ---- issue. Workaround This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available.

Or, you can use attached file to replace AwsApiCommand MID Server script include (ecc_agent_script_include_8ecd32c2db211300d504788dbf96198c.xml).