aws / aws/amazon-sagemaker-feedback
JumpStart model file not found error tuning Meta-Llama-3.1-70B-Instruct
- Dominant language
- No language data
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
### Product Version
- [ ] Amazon SageMaker Studio Classic
- [X] Amazon SageMaker Studio
- [ ] Issue is not related to SageMaker Studio
### Issue Description
JumpStart throws an error when attempting to fine-tune Meta-Llama-3.1-70B-Instruct using ml.p4d.24xlarge.
No S3 objects found under S3 URL "s3://jumpstart-cache-prod-us-west-2/meta-training/train-meta-textgeneration-llama-3-1-70b-instruct.tar.gz" given in input data source. Please ensure that the bucket exists in the selected region (us-west-2), that objects exist under that S3 prefix, and that the role "arn:aws:iam::831875310015:role/service-role/AmazonSageMaker-ExecutionRole-20240812T070946" has "s3:ListBucket" permissions on bucket "jumpstart-cache-prod-us-west-2".
The only options are ml.p4d.24xlarge and ml.g5.48xlarge. The ml.g5 is too small to load the model so Meta-Llama-3.1-70B-Instruct is impossible to tune via JumpStart.

### Expected Behavior
_No response_
### Observed Behavior
No S3 objects found under S3 URL "s3://jumpstart-cache-prod-us-west-2/meta-training/train-meta-textgeneration-llama-3-1-70b-instruct.tar.gz" given in input data source. Please ensure that the bucket exists in the selected region (us-west-2), that objects exist under that S3 prefix, and that the role "arn:aws:iam::831875310015:role/service-role/AmazonSageMaker-ExecutionRole-20240812T070946" has "s3:ListBucket" permissions on bucket "jumpstart-cache-prod-us-west-2".
### Product Category
JumpStart, Models
### Feedback Category
Reliability and Stability
### Other Details
_No response_
Contributor guide
Research direction
Reproduce the JumpStart fine-tuning attempt in Amazon SageMaker Studio using Meta-Llama-3.1-70B-Instruct on ml.p4d.24xlarge. Start by checking the referenced S3 URL, selected us-west-2 region, and execution-role permissions. Done means the model artifact is available to the job and fine-tuning can start without the reported missing-object error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100