AWS clean-rooms documentation change
Summary
Updated script validation steps to allow flexible filenames and corrected formatting
Security assessment
The changes improve clarity and configuration guidance but do not directly address security vulnerabilities or document new security features.
Diff
diff --git a/clean-rooms/latest/userguide/troubleshooting-pyspark-analysis-templates.md b/clean-rooms/latest/userguide/troubleshooting-pyspark-analysis-templates.md index 3e69a0d72..28dc80c65 100644 --- a//clean-rooms/latest/userguide/troubleshooting-pyspark-analysis-templates.md +++ b//clean-rooms/latest/userguide/troubleshooting-pyspark-analysis-templates.md @@ -69 +69 @@ Analysis template jobs can fail immediately at startup due to three main configu - * Missing or incorrectly formatted entry point function in the Python script + * Missing or incorrectly formatted entrypoint function in the user script @@ -71 +71 @@ Analysis template jobs can fail immediately at startup due to three main configu -Incompatible Python version in the virtual environment + * Incompatible Python version in the virtual environment @@ -80 +80 @@ Incompatible Python version in the virtual environment - 1. Verify your script name: + 1. Verify your user script: @@ -82 +82 @@ Incompatible Python version in the virtual environment - 1. Check that your Python script is named exactly `user_script.py`. + 1. Check that your user script has a valid Python filename. @@ -84 +84 @@ Incompatible Python version in the virtual environment - 2. If named differently, rename the file to `user_script.py` . +Valid Python filenames use lowercase letters, underscores to separate words, and the .py extension. @@ -86 +86 @@ Incompatible Python version in the virtual environment - 2. Add the required entry point function: + 2. Verify the entrypoint function. If your user script doesn't have an entrypoint function, add one. @@ -88 +88 @@ Incompatible Python version in the virtual environment - 1. Open your Python script. + 1. Open your user script. @@ -246 +246 @@ Virtual environment configuration failures commonly occur due to: - 3. Verify all dependencies are listed in requirements.txt. + 3. Verify all dependencies are listed in `requirements.txt`.