Amazon EMR and AWS Glue now enable you to enforce fine-grained access control (FGAC) on both read and write operations for AWS Lake Formation registered tables in your Apache Spark jobs. Previously, you could only apply Lake Formation’s table, column, and row-level permissions for read operations (SELECT, DESCRIBE). This simplifies data workflows by allowing both read and write tasks in a single Spark job, eliminating the need for separate clusters or applications. Organizations can now execute end-to-end data workflows with consistent security controls, streamlining operations and reducing infrastructure costs.
With this launch, administrators can control who is authorized to insert new data, update specific records, or merge changes through DML operations (CREATE, ALTER, INSERT, UPDATE, DELETE, MERGE INTO, DROP), ensuring that all data modifications adhere to specified security policies to mitigate the risk of unauthorized data modification, or misuse. This launch simplifies data governance and security frameworks by providing a single point for defining access rules in AWS Lake Formation and enforcing these rules in Spark for both read and write operations.
This feature is available in all AWS Regions where Amazon EMR (EC2, EKS and Serverless), AWS Glue and AWS Lake Formation are available. To learn more, visit the open table format support documentation.
Categories: general:products/amazon-emr,general:products/aws-glue,marketing:marchitecture/management-tools,marketing:marchitecture/analytics
Source: Amazon Web Services
Latest Posts
- Durable Objects, Workers – New `us` jurisdiction for Durable Objects
- (Updated) Upcoming change: disabling Teams meeting recording expiration notification emails [MC1245635]
- (Updated) Extending AI in SharePoint using custom skills [MC1269209]
- Microsoft OneNote: Multimodal recording in Copilot Notebooks on Windows [MC1405506]
