1 Answer
- Newest
- Most votes
- Most comments
0
Unfortunately it's not possible to directly add GuardDuty to SageMaker's local upload option. GuardDuty is mainly for monitoring AWS accounts and S3, not for scanning local uploads. Your best bet is still the S3 route if you want GuardDuty protection. But if you're trying to avoid that extra step, you could look into:
-Scanning files locally before upload
-Using SageMaker's built-in security features
-Creating a custom scanning pipeline
-Setting up VPC endpoints if you're using SageMaker in a VPC
What's driving this request? Any specific security concerns?
Relevant content
- AWS OFFICIALUpdated 4 years ago
We have users with limited access to AWS services, we want to enable SageMaker to these usersbut we don't want to create security problems, the local upload seemed like an easy way to import datasets but we are skeptical about it due to possible problems. We will disable that option, thank you for the help.