To execute metadata extraction AWS account should have enough access to fetch required data. The Bucket Policy in AWS requires at least these permissions:
diff --git a/openmetadata-docs/content/connectors/database/datalake/cli.md b/openmetadata-docs/content/connectors/database/datalake/cli.md index 543b6df5915..0064fe2cfd0 100644 --- a/openmetadata-docs/content/connectors/database/datalake/cli.md +++ b/openmetadata-docs/content/connectors/database/datalake/cli.md @@ -21,6 +21,12 @@ To deploy OpenMetadata, check the Deployment guides. To run the Ingestion via the UI you'll need to use the OpenMetadata Ingestion Container, which comes shipped with custom Airflow plugins to handle the workflow deployment. +To execute metadata extraction AWS account should have enough access to fetch required data. The Bucket Policy in AWS requires at least these permissions:
diff --git a/openmetadata-docs/content/connectors/database/datalake/index.md b/openmetadata-docs/content/connectors/database/datalake/index.md index 294561c153b..1e0ecccb921 100644 --- a/openmetadata-docs/content/connectors/database/datalake/index.md +++ b/openmetadata-docs/content/connectors/database/datalake/index.md @@ -40,6 +40,12 @@ To deploy OpenMetadata, check the Deployment guides. To run the Ingestion via the UI you'll need to use the OpenMetadata Ingestion Container, which comes shipped with custom Airflow plugins to handle the workflow deployment. +To execute metadata extraction AWS account should have enough access to fetch required data. The Bucket Policy in AWS requires at least these permissions: