eventDriven replication :Use Google Directory changes to trigger updates based on the events, and reduce frequency of 'full sync' based execution.

To reduce the frequency of need less execution and avoid provisioning delays between Google Directory and AWS IAM Identity Center. Implement an event drive architecture between the two platforms.

Rough outline:
1. **Google Directory Change Monitoring: **
Use Google Cloud Endpoints (GCE) to listen for events related to changes in your Google Directory.
Configure GCE to notify an AWS API Gateway when a change occurs.
2. **AWS API Gateway:**
Create an API Gateway endpoint in AWS that will receive notifications from GCE.
Configure the API Gateway to trigger a Lambda function when a notification is received.
3. **AWS Lambda Function:**
Trigger the API Gateway.

It may be desirable to retain a schedule trigger but at much lower frequency, e.g. daily in case event driven calls fail.

Start by inspecting the existing scheduled full-sync path and AWS Lambda entry point, then trace how updates reach AWS IAM Identity Center. Map the Google Directory event, API Gateway, and Lambda flow, including a lower-frequency fallback schedule; done means event-driven updates and fallback behavior are defined and working.

Written by the indexing model from the issue text.