AWS deadline-cloud documentation change
Summary
Updated terminology from 'S3 bucket' to 'Amazon S3 bucket' for branding consistency in two locations within package build automation documentation.
Security assessment
This is purely a branding/nomenclature change with no security implications. It updates terminology for consistency but doesn't alter security guidance, add security features, or address security issues.
Diff
diff --git a/deadline-cloud/latest/developerguide/automate-package-builds.md b/deadline-cloud/latest/developerguide/automate-package-builds.md index cf8cb467e..35e07f1f8 100644 --- a//deadline-cloud/latest/developerguide/automate-package-builds.md +++ b//deadline-cloud/latest/developerguide/automate-package-builds.md @@ -40 +40 @@ Follow the instructions in [Create a queue](https://docs.aws.amazon.com/deadline - * In step 5, choose an existing S3 bucket. Specify a root folder name such as `DeadlineCloudPackageBuild` so that build artifacts stay separate from your normal Deadline Cloud attachments. + * In step 5, choose an existing Amazon S3 bucket. Specify a root folder name such as `DeadlineCloudPackageBuild` so that build artifacts stay separate from your normal Deadline Cloud attachments. @@ -51 +51 @@ Follow the instructions in [Create a queue](https://docs.aws.amazon.com/deadline -To allow the package building queue to access the `/Conda` prefix in the queue's S3 bucket, you must modify the queue's role to give it read/write access. The role needs the following permissions so that package build jobs can upload new packages and reindex the channel. +To allow the package building queue to access the `/Conda` prefix in the queue's Amazon S3 bucket, you must modify the queue's role to give it read/write access. The role needs the following permissions so that package build jobs can upload new packages and reindex the channel.