AWS deadline-cloud documentation change
Summary
Added 'content-addressable storage' clarification for S3 upload deduplication
Security assessment
Technical clarification about storage mechanics rather than security controls. No security impact mentioned.
Diff
diff --git a/deadline-cloud/latest/developerguide/what-job-attachments-uploads-to-amazon-s3.md b/deadline-cloud/latest/developerguide/what-job-attachments-uploads-to-amazon-s3.md index 0c3052216..f126967d1 100644 --- a//deadline-cloud/latest/developerguide/what-job-attachments-uploads-to-amazon-s3.md +++ b//deadline-cloud/latest/developerguide/what-job-attachments-uploads-to-amazon-s3.md @@ -70 +70 @@ When you submit the job, Deadline Cloud first hashes the `script.sh` file and th -Deadline Cloud treats the S3 bucket as content-addressable storage. Files are uploaded to S3 objects. The object name is derived from a hash of the file’s contents. If two files have identical contents they have the same hash value regardless of where the files are located or what they are named. This enables Deadline Cloud to avoid uploading a file if it is already available. +Deadline Cloud treats the S3 bucket as content-addressable storage. Files are uploaded to S3 objects. The object name is derived from a hash of the file’s contents. If two files have identical contents they have the same hash value regardless of where the files are located or what they are named. This content-addressable storage enables Deadline Cloud to avoid uploading a file if it is already available.