From 40833feb567c9af2f28cd0beffef472c30baf241 Mon Sep 17 00:00:00 2001 From: Nic Klaassen Date: Tue, 19 Dec 2023 13:14:57 -0800 Subject: [PATCH] docs: remove athena warning (#35908) This commit removes a warning not to use the Athena backend if using an event exporter due to high resource usage. This issue was fixed in https://github.com/gravitational/teleport/pull/32547 --- docs/pages/reference/backends.mdx | 18 +----------------- 1 file changed, 1 insertion(+), 17 deletions(-) diff --git a/docs/pages/reference/backends.mdx b/docs/pages/reference/backends.mdx index 31f7e7cbbf3..d19faa71659 100644 --- a/docs/pages/reference/backends.mdx +++ b/docs/pages/reference/backends.mdx @@ -952,26 +952,10 @@ Config option priority is applied in the following order: are not supported in certain regions or environments or are only supported in GovCloud. -## Athena +## Athena The Athena audit log back-end is available starting from Teleport v14.0. - - -If you are using the -[Teleport-event-exporter](../management/export-audit-events/fluentd.mdx) -or any other mechanism for polling of [SearchEvents -API](https://pkg.go.dev/github.com/gravitational/teleport/api/client#Client.SearchEvents), -you should not use the Athena audit back-end, as the preview release of this -back-end is especially resource intensive when polling the Teleport Auth -Service for audit events. - -A new version of the Teleport event handler is under development to address this -issue. - - - - If you are running Teleport on AWS, you can use an [Athena](https://aws.amazon.com/athena/)-based audit log system that manages [Parquet files](https://parquet.apache.org/) stored on