Every new Amazon SageMaker notebook instance must have a custom script installed automatically. Which approach achieves this with the LEAST operational overhead?

Creating a lifecycle configuration script is the most efficient method because it's purpose-built for automating setup tasks on SageMaker notebook instances. You define the script once, and it automatically runs when a notebook starts or creates, ensuring consistent installation with minimal manual intervention. Building a custom ECR image is more complex and intended for custom environments or dependencies, not just script installation. Using CodeArtifact with PrivateLink is overkill for a simple script and adds significant overhead for package management. Storing the script in S3 and using Lambda/EventBridge introduces unnecessary complexity and additional services for a task natively handled by SageMaker lifecycle configurations.