I’ve been exploring SageMaker Lifecycle Configurations, particularly in reference to the setting default LCC in the AWS documentation . According to the documentation, it’s possible to attach multiple Lifecycle Configuration (LCC) scripts to a single source and set a default LCC for both the Jupyter Server app (Studio app) and the Kernel Gateway app.
In my scenario, I have set up an auto-shutdown-lcc as the default for the Studio app (Jupyter Server app). Additionally, I’ve created another LCC script called code-whisperer-lcc designed to automatically install and enable the Code Whisperer extension for the Studio app.
- if there are multiple LCC scripts, can we define the order in which these scripts are executed when launching the Studio app?
- If specifying the execution order is not possible, what would be the best practice for achieving this task without disrupting the functionality of the auto-shutdown-lcc script?