AWS athena documentation change
Summary
Restructured content and added note about CVE scanning capability
Security assessment
Added documentation about transferring images to enable CVE scans, a security best practice. Enhances security visibility but doesn't fix a vulnerability.
Diff
diff --git a/athena/latest/ug/pull-ecr-customer-account.md b/athena/latest/ug/pull-ecr-customer-account.md index f3e5114f2..a854a9e91 100644 --- a//athena/latest/ug/pull-ecr-customer-account.md +++ b//athena/latest/ug/pull-ecr-customer-account.md @@ -5 +5 @@ -PrerequisitesImage transfer procedureCompletion +PrerequisitesHow to transfer an image @@ -7 +7 @@ PrerequisitesImage transfer procedureCompletion -# Pulling ECR images to your AWS account +# Pull ECR images to your AWS account @@ -13,3 +13 @@ Athena federation connector Lambda functions use container images that are store - * An Athena Federation Connector - - * The connector can be created through any source, provided it uses a container image + * An Athena Federation Connector – The connector can be created through any source, provided it uses a container image. @@ -30 +28 @@ To verify image deployment, check the Image tab in your Athena Federation Connec -## Image transfer procedure +## How to transfer an image @@ -71,0 +70 @@ Where `customer-registry` is your ECR registry (e.g., account_id_2.dkr.ecr.us-ea +The Athena federated connector image is now located in your account, which allows you to perform CVE scans on the image. @@ -75,3 +73,0 @@ Where `customer-registry` is your ECR registry (e.g., account_id_2.dkr.ecr.us-ea -## Completion - -The Athena federated connector image is now located in your account, enabling you to perform CVE scans on the image.