Adobe I/O Webhook Disabled with HTTP 429 During Bulk AEM as a Cloud Service Asset Updates

Hi guys,

                 We have a use case where we need to perform bulk updates on assets in AEMaaCS. For example, when we update around 100 assets in bulk, we expect the corresponding events to be triggered and received by our webhook.

Events for ref - Asset Delivery Ready, Asset processing completed

To support this, we have configured a project in the Adobe Developer Console (Adobe I/O) and registered an event for our development AEM as a Cloud Service environment, with a webhook configured to receive the events.

However, during bulk asset updates, we are encountering the following issues:

• The webhook requests are returning HTTP 429 (Too Many Requests)
• The response body contains the following error:
  “Too many webhook requests from this IP, please try again later”
• The response also includes “retryAfter: 15 minutes”
• Adobe I/O displays a warning that the webhook has been disabled because it is either unreachable or verification has failed
   

  Our questions:

• Is there a rate limit on Adobe I/O Events webhooks when a large number of AEMaaCS asset events are generated in a short period or simulatenously?
• Does Adobe impose a limit on the number of webhook requests from a particular IP address? If so, what are the applicable limits?
• What is the recommended approach for handling bulk asset updates that generate a large volume of events?
• Is there a recommended way to prevent the webhook from being disabled when the endpoint returns HTTP 429 responses?
• Are there any Adobe I/O Events configuration changes or best practices that we should follow for this scenario?
  
  Our goal is to reliably process events generated by bulk asset updates without hitting rate limits or having the webhook disabled
   

  Any guidance on the applicable limits and best practices for handling high-volume AEMaaCS asset events would be greatly appreciated.
  
  Thank you!