AWS greengrass documentation change
Summary
Added guidance about running AWS IoT Greengrass Core software as a non-root user and updated section title to reflect this security best practice.
Security assessment
The change adds documentation about security best practices (principle of least privilege by running as non-root user) but doesn't indicate a specific security issue being addressed. It's a proactive security recommendation rather than a response to a vulnerability.
Diff
diff --git a/greengrass/v2/developerguide/security-best-practices.md b/greengrass/v2/developerguide/security-best-practices.md index 38b03f1ff..017cf2885 100644 --- a//greengrass/v2/developerguide/security-best-practices.md +++ b//greengrass/v2/developerguide/security-best-practices.md @@ -16,0 +17,2 @@ Follow the principle of least privilege for your components by running them as u +You can also run the AWS IoT Greengrass Core software itself as a non-root user to further limit privileges on your device. For more information, see [Set up AWS IoT Greengrass V2 core devices as non-root](./setup-greengrass-non-root.html). + @@ -84 +86 @@ VPC endpoints (AWS PrivateLink) -Using AWS IoT Device Tester for AWS IoT Greengrass V2 +Run AWS IoT Greengrass V2 as non-root