Thanks for your reply. You were indeed correct, it is in fact an IAM policy related issue. Even the AmazonSageMakerFullAccess Policy didn’t do the job actually. I had to create a separate overly permissive policy but ultimately was able to deploy it.
Thanks!