Datalabs
Datalabs provide managed development environments for interactive analytics and data science workflows.
Below is the sample resource definition file for Datalab:
{
"rDatalab": {
"Type": "Datalab",
"Properties": {
"DatalabName": "cicd-test-datalab",
"Description": "Base datalab for CICD QA creation testing",
"AdditionalMetadata": {
"Keywords": [
"cicd",
"qa"
],
"IsSessionsEnabled": true,
"IsAutoTerminateEnabled": false
},
"DatalabType": "sagemaker-notebook",
"ComputeMetadata": {
"VolumeSizeInGB": "10",
"InstanceList": [
"ml.t3.medium"
],
"RootAccess": "Disabled",
"DirectInternetAccess": "Enabled"
},
"ResourceAccessMetadata": {
"DomainAccess": {
"Owner": [],
"ReadOnly": []
},
"ParameterAccess": [],
"DatasetAccess": {
"ReadOnlyFileLevel": []
},
"CodeRepositoryAccess": {}
}
}
}
}
We do not stop datalabs during updates. Datalabs are stopped only during deletion. If an update includes a key that cannot be applied without stopping the datalab, the backend returns an error and the CICD flow stops.
Datalab has dependencies on Tag.
Dependent resources should not be deleted before the primary resource; attempting to do so may lead to failures or inconsistencies during the deletion process.
Referencing this Resource
Below are the common keys that can be used in the DependsOn function to retrieve details of this resource.
Supported Keys
| Key | Description |
|---|---|
| DatalabName | Returns the DatalabName value of this resource |
| DatalabId | Returns the DatalabId value of this resource |
For additional supported keys, refer to the API definition document for the respective resource type.
Example
To reference this schedule from another resource, use !DependsOn with logical name and property in the format <logicalResourceName>.<PropertyName>.
Example: {"!DependsOn": "rDatalab.DatalabId"}