2 Answers
- Newest
- Most votes
- Most comments
0
You are taking properties from "connectionName", since you have "useConnectionProperties" enabled, seems that connection points to a relative certificate, so the engine is looking for it in the local filesystem instead of s3.
If normally you provide the certificate file to Glue via --extra-files, you would need to put that file inside the container manually so Glue can find it.
-1
This is how I run my local env. On the command prompt , run :
- Note the MyProfile is your AWS profile set in your local system
- Replace the path and all other paths containing <UserName> as appropriate
PROFILE_NAME="MyProfile"
JUPYTER_WORKSPACE_LOCATION=/Users/<UserName>/WorkSpace/jupyter_workspace/
WORKSPACE_LOCATION=/Users/<UserName>/WorkSpace/jupyter_workspace/
docker run -it -v ~/.aws:/home/glue_user/.aws -v $JUPYTER_WORKSPACE_LOCATION:/home/glue_user/workspace/jupyter_workspace/ -e AWS_PROFILE=$PROFILE_NAME -e DISABLE_SSL=true --rm -p 4040:4040 -p 18080:18080 -p 8998:8998 -p 8888:8888 --name glue_jupyter_lab amazon/aws-glue-libs:glue_libs_3.0.0_image_01-arm64 /home/glue_user/jupyter/jupyter_start.sh
Also follow : https://aws.amazon.com/blogs/big-data/develop-and-test-aws-glue-version-3-0-jobs-locally-using-a-docker-container/ Make a note of the system that you are running on . I run it on Mac M1 chip , and find the arm64 image appropriate
answered a year ago
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago