[Integration][AWS] | Fix an issue where the integration enters an endless loop on region permission error

[mk-armah]

Description

What:

Fixed an issue where the integration would enter an endless loop upon encountering a permission error when querying resources in a particular region. The code now raises the permission error instead of skipping it, allowing downstream code to handle it appropriately.

Why:

Previously, when a permission error occurred, the integration skipped the error without proper handling, causing it to get stuck in an infinite loop. By raising the error, we ensure that the integration does not loop endlessly and that the error can be managed correctly by downstream processes.

How:

• Updated the error handling logic to raise the permission error instead of skipping it.
• Verified that downstream code is capable of handling the raised exception without adverse effects.
• Tested the integration to confirm that it no longer enters an endless loop on permission errors.

Type of change

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

• 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)

All tests should be run against the port production environment(using a testing org).

Core testing checklist

• Integration able to create all default resources from scratch
• Resync finishes successfully
• Resync able to create entities
• Resync able to update entities
• Resync able to detect and delete entities
• Scheduled resync able to abort existing resync and start a new one
• Tested with at least 2 integrations from scratch
• Tested with Kafka and Polling event listeners
• Tested deletion of entities that don't pass the selector

Integration testing checklist

• Integration able to create all default resources from scratch
• Resync able to create entities
• Resync able to update entities
• Resync able to detect and delete entities
• Resync finishes successfully
• If new resource kind is added or updated in the integration, add example raw data, mapping and expected result to the examples folder in the integration directory.
• If resource kind is updated, run the integration with the example data and check if the expected result is achieved
• If new resource kind is added or updated, validate that live-events for that resource are working as expected
• Docs PR link here

Preflight checklist

• Handled rate limiting
• Handled pagination
• Implemented the code in async
• Support Multi account

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.

[PeyGis]

lgtm

[shalev007]

Let's also remove the warning log since it's kind of confusing

Suggested change

	raise e
	except Exception as e:
	logger.error(
	f"Error resyncing {kind} in region {region} in account {account_id}, {e}"
	)
	raise e

[shalev007]

Let's push it after you remove the log