Sagemaker Code Editor Space can't attach a Lifecycle Configuration

[cwzkevin]

Product Version

• [ ] Amazon SageMaker Studio Classic
• [X] Amazon SageMaker Studio
• [ ] Issue is not related to SageMaker Studio

Issue Description

Trying to install some example packages such that when the code editor space are restarted the packages are still there.

1. Added a life cycle configuration to the CodeEditor Application of the domain as below:

   
   #!/bin/bash
   set -eux

pip install elasticsearch sidetable git-remote-codecommit

2a.  Attach the created lcc to the corresponding space user profile (update the user-profile) and restarted the code editor space (ref: [https://docs.aws.amazon.com/sagemaker/latest/dg/code-editor-use-lifecycle-configurations.html](https://docs.aws.amazon.com/sagemaker/latest/dg/code-editor-use-lifecycle-configurations.html))

Update a UserProfile

aws sagemaker update-user-profile \ --domain-id domain-id \ --user-profile-name user-profile-name \ --user-settings '{ "CodeEditorAppSettings": { "LifecycleConfigArns": [lifecycle-configuration-arn-list] } }'

Expected the packages will be in the base env once the code editor started. Code Editor starts normal, but the packages are not there.

2b.  Attached the created lcc for the space under the GUI (Space Settings)

![image](https://github.com/aws/amazon-sagemaker-feedback/assets/21072230/fe036263-2370-4f5c-ac2e-c7142afdcb1f)

Expected the packages will be in the base env once the code editor started. Code Editor failed to start. Seems the system is trying to do something else?

![image](https://github.com/aws/amazon-sagemaker-feedback/assets/21072230/04b5680d-a768-4368-92c6-5a8b236a432b)

### Expected Behavior

Expected the packages will be in the base env once the code editor started.

### Observed Behavior

either has no effect 2a, or failed to start 2b.

### Product Category

Code-Editor

### Feedback Category

Configuration and Setup

### Other Details

_No response_

[poojak13]

@arkaprava08 @chirpio76 can you help here?