Currently, when you define a trigger that uses the AWS Eventbridge via the UI it auto creates a realm App that links the DB change to the event bridge. However, with the mongodbatlas_event_trigger resource you have to manually defined an empty realm app and give the resource the app_id of that empty app. This is obviously not a 100% automated process. This could be, if the provider created the empty realm app by itself, then referencing the created app app_id. This would only be needed: 1. when the app_id is not provided 2. the following attribute was provided event_processors { aws_eventbridge { config_account_id = "AWS ACCOUNT ID" config_region = "AWS REGIOn" } } 3. otherwise use the provided app_id This would still support the case when the eventbridge even processor was used and a pre-existing realm app with custom logic was also defined. This would make the provision of an Eventbridge trigger totally automated.