feat(event-bridge): api destinations (SSPROD-53939) #49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes significant updates to the AWS Event Bridge integration module to enhance its functionality and improve security. The main changes involve updating the module to use EventBridge API Destinations, adding new IAM roles and policies, and updating documentation to reflect these changes.
Enhancements to EventBridge Integration:
README.md
to describe the use of EventBridge API Destinations and the new resources created, includingEventBridge API Destination
andEventBridge Connection
.Documentation Updates:
README.md
to reflect the changes in the module, including new resource descriptions and updated requirements and providers. [1] [2]api_dest_rate_limit
to control the rate limit for API Destinations.Code Refactoring:
main.tf
to include new data sources and local variables for the EventBridge API Destination configuration. [1] [2]Deprecation Notices:
org_units
input as deprecated, advising users to migrate toinclude_ouids
.These changes enhance the module's capabilities for log ingestion and threat detection, making it more robust and secure.