AWS athena documentation change
Summary
Updated links to AWS managed policies documentation from 'managed-policies.html' to 'security-iam-awsmanpol.html'
Security assessment
The change only updates hyperlinks to IAM policy documentation without altering security-related content or addressing vulnerabilities. No evidence of security issue remediation.
Diff
diff --git a/athena/latest/ug/hive-metastore-iam-access-lambda.md b/athena/latest/ug/hive-metastore-iam-access-lambda.md index c384991bf..1481dc67b 100644 --- a//athena/latest/ug/hive-metastore-iam-access-lambda.md +++ b//athena/latest/ug/hive-metastore-iam-access-lambda.md @@ -13 +13 @@ To invoke a Lambda function in your account, you must create a role that has the - * `AmazonAthenaFullAccess` – The [AmazonAthenaFullAccess](./managed-policies.html#amazonathenafullaccess-managed-policy) managed policy grants full access to Athena. + * `AmazonAthenaFullAccess` – The [AmazonAthenaFullAccess](./security-iam-awsmanpol.html#amazonathenafullaccess-managed-policy) managed policy grants full access to Athena. @@ -44 +44 @@ Because Athena uses the AWS Serverless Application Repository to create Lambda f -For API access to catalog registration and metadata operations, you can use the [AmazonAthenaFullAccess managed policy](./managed-policies.html#amazonathenafullaccess-managed-policy). If you do not use the `AmazonAthenaFullAccess` policy, add the following API operations to your Athena policies: +For API access to catalog registration and metadata operations, you can use the [AmazonAthenaFullAccess managed policy](./security-iam-awsmanpol.html#amazonathenafullaccess-managed-policy). If you do not use the `AmazonAthenaFullAccess` policy, add the following API operations to your Athena policies: