Skip to content

Commit 839d308

Browse files
authored
Update aws-sagemaker-persistence.md
1 parent 4ee987a commit 839d308

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

src/pentesting-cloud/aws-security/aws-persistence/aws-sagemaker-persistence.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,11 @@
11

22
# AWS - SageMaker Lifecycle Configuration Persistence
33

4+
## Overview of Persistence Techniques
5+
6+
This section outlines methods for gaining persistence in SageMaker by abusing Lifecycle Configurations (LCCs), including reverse shells, cron jobs, credential theft via IMDS, and SSH backdoors. These scripts run with the instance’s IAM role and can persist across restarts. Most techniques require outbound network access, but usage of services on the AWS control plane can still allow success if the environment is in 'VPC-only" mode.
7+
#### Note: SageMaker notebook instances are essentially managed EC2 instances configured specifically for machine learning workloads.
8+
49
## Required Permissions
510
* Notebook Instances:
611
```
@@ -17,7 +22,7 @@ sagemaker:UpdateUserProfile
1722
sagemaker:UpdateSpace
1823
sagemaker:UpdateDomain
1924
```
20-
#### Note: SageMaker notebook instances are essentially managed EC2 instances configured specifically for machine learning workloads.
25+
2126

2227
## Set Lifecycle Configuration on Notebook Instances
2328

0 commit comments

Comments
 (0)