AWS clean-rooms documentation change
Summary
Generalized references to user script filenames in hash validation instructions
Security assessment
The changes clarify instructions for generating hashes but do not address a security vulnerability or add new security documentation. The security implications (data integrity checks) were already present.
Diff
diff --git a/clean-rooms/latest/userguide/review-pyspark-analysis-template.md b/clean-rooms/latest/userguide/review-pyspark-analysis-template.md index 4ed8f5d80..75a73274a 100644 --- a//clean-rooms/latest/userguide/review-pyspark-analysis-template.md +++ b//clean-rooms/latest/userguide/review-pyspark-analysis-template.md @@ -48 +48 @@ To validate that the user script and libraries shared are the same as those refe - * File you want to hash (`user_script.py`) + * User script file you want to hash @@ -77 +77 @@ To validate that the user script and libraries shared are the same as those refe -You can generate a hash by navigating to the directory containing the `user_script.py` file and then running the following command: +You can generate a hash by navigating to the directory containing your user script file and then running the following command: @@ -79 +79 @@ You can generate a hash by navigating to the directory containing the `user_scri - sha256sum user_script.py + sha256sum your_script_filename.py @@ -83 +83 @@ Example output: - e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 user_script.py + e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 my_analysis.py