Our most recent community show covered the migration from Native Lifecycle Actions (LCA) to cloud-native functions, along with a new self-service UI that gives customers full control over their Lambda-based LCAs. The session, led by Saurabh Agarwal, walked through the reasoning behind the change, the migration path, and a live demo of the new tenant management experience.
What Are Lifecycle Actions?
Lifecycle Actions let customers create custom code to handle functionality not natively supported in Reltio. During an entity's lifecycle — creation, update, merge, reference attribute changes, and deletion — customers can hook custom logic into roughly 35 defined points, such as before-save or before-delete, to run validations or operations the platform doesn't support out of the box.
Historically, Reltio supported two types of LCAs: Native LCA, which was Java-based code reviewed and hosted directly on Reltio's infrastructure, and cloud-native functions, hosted by the customer on AWS Lambda, Google Functions, or Azure Functions. Reltio has now stopped supporting Native LCA in favor of cloud-native functions exclusively.
Why the Shift to Cloud Functions
Native LCAs required Reltio's engineering team to review every submission to guard against performance and security issues in a shared environment, since a problem in one customer's LCA could affect other tenants. Cloud-native functions remove that bottleneck entirely: the code lives in the customer's own cloud, and Reltio is simply authorized to call it. This makes the model fully self-service — customers can deploy, redeploy, and extract logs on their own schedule without opening a support ticket.
LCAs remain synchronous operations by design, so they do add some latency to the entity lifecycle. Saurabh recommended exploring out-of-the-box capabilities first, and considering asynchronous alternatives like events before building an LCA. Java (JDK21) remains the primary supported language, with Python now supported via published documentation (no SDK yet), and additional language support planned for the future.
Migration Timeline and Support
Native LCA deprecation has been underway for some time: new native LCA onboarding stopped in October, and August 31 is the hard cutoff after which native LCAs will no longer run. Customers still on native LCA and without their original code can use Reltio's automated migration scripts; those with code can follow detailed doc portal guidance. Customers are encouraged to reach out to Reltio support, their CSM, or account manager for hands-on migration help — Reltio's support and engineering teams are available to assist directly.
Demo: The New Self-Service UI
Saurabh demonstrated the new Lifecycle Actions page within the tenant management application, which introduces a two-step setup:
-
Create a connection: Guided steps walk users through creating an IAM role in AWS, attaching the required permission policy, and requesting Reltio's IAM role so Reltio can assume the customer-created role. Once submitted, the connection moves to an authorize-and-validate step, where the trust policy is validated and applied.
-
Create a lifecycle action: Once connected, users define the LCA by naming the AWS Lambda function and selecting the hook that should trigger it — for example, running a "full name builder" function before “save” on the individual entity type.
In the live demo, creating a profile with only first and last name populated triggered the Lambda function before save, automatically generating the full name field — confirming the LCA executed successfully end to end.
Currently, only AWS Lambda functions are supported in the self-service UI, with Google Functions and Azure Functions support planned for a future release. Reltio is also working to automate IAM role approval so that connection requests complete within minutes rather than requiring manual processing.
Q&A Highlights
-
Customers with approved exceptions for native LCA will continue to be supported, though logging and redeployment support may be limited; migration to cloud-native functions is still strongly encouraged.
-
Partner tenant IAM requests that are delayed can be escalated directly to Saurabh with the tenant ID and environment for manual approval while the automated process rolls out.
-
New LCA development: Detailed documentation for building LCAs, including SDK guidance for Java, is available on the doc portal — new LCAs must be built as cloud-native functions, since native LCA is no longer supported.
What's Next
Two more community shows are coming up: Materialized Hierarchy Management on August 4, covering Reltio's new node-based hierarchy model, and Reference Data to Autopilot on August 19. Registration links have been shared in the community.
The recording of today's session will be posted to the community within the next few days. If you have questions that weren't addressed live, feel free to post them in the community for follow-up.