…886)

What - Ingest issues that are open, or were created/updated in the past
week
Why - Support better metrics out of the box
How - Update JQL

Please leave one option from the following and delete the rest:

- [ ] Bug fix (non-breaking change which fixes an issue)
- [X] New feature (non-breaking change which adds functionality)
- [ ] New Integration (non-breaking change which adds a new integration)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Non-breaking change (fix of existing functionality that will not
change current behavior)
- [ ] Documentation (added/updated documentation)

Include screenshots from your environment showing how the resources of
the integration will look.

Provide links to the API documentation used for this integration.

# Description

What - 
Fixed an issue in the AWS integration where S3 buckets were not synced
for all accounts.

Why - 
S3 buckets are a global resource type, meaning we only search for the
first region showing these buckets and then stop searching to avoid rate
limiting with AWS and wasting time. This caused users with multi-account
setups to only list their first account's buckets.

How - 
Added an iteration of accounts on top of the existing process to ensure
that S3 buckets are synced across all accounts.

## Type of change

Please leave one option from the following and delete the rest:

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] New Integration (non-breaking change which adds a new integration)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Non-breaking change (fix of existing functionality that will not
change current behavior)
- [ ] Documentation (added/updated documentation)

## Screenshots

Include screenshots from your environment showing how the resources of
the integration will look.

## API Documentation

Provide links to the API documentation used for this integration.

---------

Co-authored-by: Shalev Avhar <[email protected]>

# Description

What - We have implemented blacklist error handling for AWS errors in
our system. This ensures that certain AWS error types are specifically
caught and handled differently from other errors.

Why - Each AWS resource handles "not found" errors differently, making
it challenging to distinguish between a resource not being found and an
actual error in the system. This inconsistency can lead to
misinterpretation of errors and inappropriate error handling. By adding
blacklist error handling, we can provide more accurate and consistent
error handling across different AWS resources.

How - We have introduced a blacklist mechanism that explicitly catches
specific AWS error codes related to "not found" scenarios. These error
codes are then handled separately from other types of errors, allowing
us to treat them as non-critical issues and proceed accordingly. This
ensures that our system can gracefully handle situations where AWS
resources are legitimately not found without mistaking them for system
errors. This approach improves our system's robustness and reliability
in interacting with AWS services.


## Type of change

Please leave one option from the following and delete the rest:

- [X] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] New Integration (non-breaking change which adds a new integration)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Non-breaking change (fix of existing functionality that will not
change current behavior)
- [ ] Documentation (added/updated documentation)

## Screenshots

Include screenshots from your environment showing how the resources of
the integration will look.

## API Documentation

Provide links to the API documentation used for this integration.

---------

Co-authored-by: Shalev Avhar <[email protected]>