> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/saas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/saas/configuration/integrations/aws-lake-formation/reference-guides.md). # Reference Guides - [AWS Lake Formation](https://documentation.immuta.com/saas/configuration/integrations/aws-lake-formation/reference-guides/aws-lake-formation.md): Learn about how the AWS Lake Formation integration works and what Immuta creates in your environment to enforce object-level access controls - [Security and Compliance](https://documentation.immuta.com/saas/configuration/integrations/aws-lake-formation/reference-guides/security-and-compliance.md): Understand the authentication methods and audit features supported by the AWS Lake Formation integration to ensure you are meeting your organization's security and compliance needs - [Protecting Data](https://documentation.immuta.com/saas/configuration/integrations/aws-lake-formation/reference-guides/protecting-data.md): Learn how Immuta enforces subscription policies on data registered in the Glue Data Catalog - [Accessing Data](https://documentation.immuta.com/saas/configuration/integrations/aws-lake-formation/reference-guides/accessing-data.md): Learn how end users can access policy-enforced data using Amazon Athena, Amazon EMR Spark, or Amazon Redshift Spectrum --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.immuta.com/saas/configuration/integrations/aws-lake-formation/reference-guides.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.