AWS greengrass: Greengrass log manager limit note for un-uploaded log files
Summary
Adds the same note to six component log size limit parameters explaining that the configured limit is enforced only after log files are uploaded to CloudWatch Logs, so files that are not uploaded (device offline or upload failures) are retained and total log size can exceed the configured limit.
Security assessment
The note is an operational clarification about disk-usage accounting: log deletion depends on successful CloudWatch Logs upload, so a device offline or failing uploads retains local logs and can exceed the configured size limit. It touches the logging pipeline but describes a capacity/disk-exhaustion caveat rather than a vulnerability, credential, or access-control fix.
Evidence
+The log manager component applies this limit only after it uploads a component's log files to CloudWatch Logs. For a component that writes its own log files, files that aren't uploaded (for example, while the device is offline or uploads fail) aren't deleted, so the total size can exceed this limit.
Diff
diff --git a/greengrass/v2/developerguide/log-manager-component.md b/greengrass/v2/developerguide/log-manager-component.md index deb2ece..2715e27 100644 --- a//greengrass/v2/developerguide/log-manager-component.md +++ b//greengrass/v2/developerguide/log-manager-component.md @@ -439,0 +440,4 @@ This parameter is related to the [log size limit](./greengrass-nucleus-component +###### Note + +The log manager component applies this limit only after it uploads a component's log files to CloudWatch Logs. For a component that writes its own log files, files that aren't uploaded (for example, while the device is offline or uploads fail) aren't deleted, so the total size can exceed this limit. + @@ -688,0 +693,4 @@ This parameter is related to the [log size limit](./greengrass-nucleus-component +###### Note + +The log manager component applies this limit only after it uploads a component's log files to CloudWatch Logs. For a component that writes its own log files, files that aren't uploaded (for example, while the device is offline or uploads fail) aren't deleted, so the total size can exceed this limit. + @@ -928,0 +937,4 @@ This parameter is related to the [log size limit](./greengrass-nucleus-component +###### Note + +The log manager component applies this limit only after it uploads a component's log files to CloudWatch Logs. For a component that writes its own log files, files that aren't uploaded (for example, while the device is offline or uploads fail) aren't deleted, so the total size can exceed this limit. + @@ -1154,0 +1167,4 @@ This parameter is related to the [log size limit](./greengrass-nucleus-component +###### Note + +The log manager component applies this limit only after it uploads a component's log files to CloudWatch Logs. For a component that writes its own log files, files that aren't uploaded (for example, while the device is offline or uploads fail) aren't deleted, so the total size can exceed this limit. + @@ -1355,0 +1372,4 @@ This parameter is related to the [log size limit](./greengrass-nucleus-component +###### Note + +The log manager component applies this limit only after it uploads a component's log files to CloudWatch Logs. For a component that writes its own log files, files that aren't uploaded (for example, while the device is offline or uploads fail) aren't deleted, so the total size can exceed this limit. + @@ -1557,0 +1578,4 @@ This parameter is related to the [log size limit](./greengrass-nucleus-component +###### Note + +The log manager component applies this limit only after it uploads a component's log files to CloudWatch Logs. For a component that writes its own log files, files that aren't uploaded (for example, while the device is offline or uploads fail) aren't deleted, so the total size can exceed this limit. +