Understanding the architecture
The architecture for the protector.
The Amazon EMR Protector on ARM64 architecture extends the Protegrity Big Data Protector capabilities to environments powered by ARM-based processors, such as AWS Graviton instances. This deployment model enables organizations to secure sensitive data in large-scale analytics workloads while benefiting from the cost efficiency and performance characteristics of ARM64-based infrastructure.
Built on the standard Protegrity Big Data Protector framework, the EMR Protector integrates directly with Amazon EMR clusters. This enables policy-driven data protection across distributed processing engines, such as, Apache Spark and Hive. Like its x86_64 counterpart, the protector is deployed on each cluster node, ensuring consistent enforcement of security policies across master, core, and task nodes.
On ARM64 platforms, the protector leverages architecture-compatible libraries and runtime components. This enables the protector to deliver seamless encryption, tokenization, and de-tokenization through User Defined Functions (UDFs) and APIs embedded within data processing workflows. This allows organizations to protect sensitive data in motion and at rest without modifying existing application logic.
By combining Protegrity’s centralized policy management with ARM64-based compute infrastructure, the EMR Protector supports scalable, high-performance data processing environments while maintaining compliance with data privacy and security requirements.
The Big Data Protector on EMR utilizes the following components to process and protect data:
The architecture for the protector.
Completing the requirements for installing the protector.
Steps for installing the protector.
Updating the Configuration Parameters.
Perform operations on the cluster using the utility scripts.
Steps to remove the protector from the system.
Was this page helpful?