Troubleshooting querying in Amazon Athena
Use the following information to help you diagnose and fix common issues that you might encounter when using Athena to query objects that are stored in your Security Lake S3 bucket. For more Athena troubleshooting topics, see the Troubleshooting in Athena section of the Amazon Athena User Guide.
Querying isn't returning new objects in the data lake
Your Athena query may not return new objects in your data lake even when the S3 bucket for Security Lake contains those objects. This may occur if you've disabled Security Lake and then enabled it again. As a result, the AWS Glue partitions may not properly register the new objects.
To resolve the error, follow these steps:
Open the AWS Lambda console at https://console.aws.amazon.com/lambda/
. From the navigation bar, on the Regions selector, choose the Region in which Security Lake is enabled but the Athena query isn't returning results.
From the navigation pane, choose Functions, and select the function from the following list depending on the source version:
-
Source version 1 (OCSF 1.0.0-rc.2)– SecurityLake_Glue_Partition_Updater_Lambda_≪region>function. Source version 2 (OCSF 1.1.0)– AmazonSecurityLakeMetastoreManager_≪region>function.
-
On the Configurations tab, choose Triggers.
Select the option next to the function, and choose Edit.
Select Activate trigger, and choose Save. This will turn the function state to Enabled.
Unable to access AWS Glue tables
A query access subscriber may not be able to access AWS Glue tables that contain Security Lake data.
First, ensure that you've followed the steps outlined in Setting up cross-account table sharing (subscriber step).
If the subscriber still doesn't have access, follow these steps:
Open the AWS Glue console at https://console.aws.amazon.com/glue/
. From the navigation pane, choose Data Catalog and Catalog settings.
Give permission to the subscriber to access the AWS Glue tables with a resource-based policy. For information about creating resource-based policies, see Resource-based policy examples for AWS Glue in the AWS Glue Developer Guide.
