> ## Documentation Index
> Fetch the complete documentation index at: https://levelblue-final.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloud Connectors System Events

| | | | | |
| - | - | - | - | - |
| **Role Availability** | **Read-Only** | **Investigator** | **Analyst** | **Manager** |

USM Anywhere generates system events when your Amazon Web Services (AWS) (Suite of cloud computing services from Amazon that make up an on-demand computing platform.) Cloud Connector fails and there is an error in an Amazon Simple Storage Service (S3) or Amazon Inventory file. These event names display as *Error Processing S3 Bucket Notification* and *Error Processing AWS Inventory Notification*. For an Amazon S3 collector error, you have the option of retrying to process the Amazon S3 file.

**To retry an Amazon S3 collector error**

1. Go to **Settings > System Events** to open the System Events main page.

2. Use the Event Name filter to search the AWS S3 collector error.

   See [Searching System Events](https://levelblue-final.mintlify.site/documentation/usm-anywhere/user-guide/system-events/searching-system-events.md) for more information.

   ![](https://mintcdn.com/levelblue-final/uEuk8g2TBjXc6sIM/images/usm-anywhere/systemeventsfilter.webp?fit=max\&auto=format\&n=uEuk8g2TBjXc6sIM\&q=85\&s=3d82f7f85ac7eb8a42c56c81179b6f78)

3. Click the **Error Processing S3 Bucket Notification** event name.

   The result of your search displays with the errors identified.

   ![](https://mintcdn.com/levelblue-final/uEuk8g2TBjXc6sIM/images/usm-anywhere/systemeventslist.webp?fit=max\&auto=format\&n=uEuk8g2TBjXc6sIM\&q=85\&s=ecd8924526f0a497b2e298017e3763bd)

4. Select the error you want to retry.

   The specific error dialog box opens.

5. Click **Retry**.

   ![](https://mintcdn.com/levelblue-final/uEuk8g2TBjXc6sIM/images/usm-anywhere/systemeventretry.webp?fit=max\&auto=format\&n=uEuk8g2TBjXc6sIM\&q=85\&s=efbe5e8f70fec015965e092b3a330086)

   > [!NOTE]
   >
   > **Note:** After clicking **Retry**, USM Anywhere tries to process the file again. If the file can't be read, a new system event is generated.
