I saw that solution may be in the init script but it's not really essy to work with.

I mean, there's no log generated from the bash script, so this is not an easy way to solve my problem, maybe you have some advices about it?

Hi @axelboursin ,

I think this article will help you out: https://docs.databricks.com/aws/en/admin/workspace-settings/default-python-packages (option 1 below).

Recommended approaches (choose based on your environment):

• For broad, consistent behavior across clusters and notebooks, configure workspace-level default Python package repositories to point to CodeArtifact; this avoids per-notebook tokens and works for both serverless and classic compute.

• (The thing you mentioned) For classic clusters only, add a cluster-scoped init script that runs aws codeartifact login and writes pip config, so pip automatically resolves from your CodeArtifact repo at cluster start.

• For one-off installs or testing, use notebook-scoped %pip with --index-url (and --extra-index-url as needed) and credentials pulled from Databricks Secrets inside the notebook.

Hi @stbjelcevic,
actually we are still facing a mystery.
We created an init_script in order to generate a codeartifact token and change pip conf. Here isthe content:

pip install awscli

export AWS_CODEARTIFACT_TOKEN=$(aws codeartifact get-authorization-token \
     --domain $DOMAIN \
     --domain-owner $OWNER \
     --region $REGION \
     --query authorizationToken \
     --output text)

PIP_INDEX_URL="https://aws:${AWS_CODEARTIFACT_TOKEN}@${DOMAIN}-${OWNER}.d.codeartifact.${REGION}.amazonaws.com/pypi/${REPOSITORY}/simple/"
pip config set global.index-url $PIP_INDEX_URL
pip config set global.extra-index-url https://pypi.org/simple/