Write permissions for sagemaker execution on 2605 coralnet bucket#692
Conversation
Signed-off-by: Greg Nieuwenhuis <26285069+gnieuwenhuis@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe PR modifies the SageMaker stack infrastructure code to grant the SageMaker execution role read/write access to the coralnet_feature_vectors S3 bucket. Previously, this role had read-only access. The inline comment is updated to document the bucket's dual role: storing feature-extraction outputs and serving as the source for training pipeline reads. ChangesSageMaker S3 Feature Vector Permissions
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
cdk-nag report✅ No unsuppressed errors. See |
|
In order to write new feature vectors to the 2605-coralnet-public-sources bucket using processing jobs, we need to give write permission.
Summary by CodeRabbit