- Newest
- Most votes
- Most comments
I apologize for the inconvenience you're experiencing with the Submit button in your Ground Truth labeling job. While the specific issue you're describing isn't directly addressed in the provided sources, there are a few things we can consider based on the information available about Ground Truth labeling jobs:
-
CORS Policy: Ensure that the S3 bucket containing your input image data has the correct CORS (Cross-Origin Resource Sharing) policy attached. Ground Truth requires this for all S3 buckets with labeling job input image data. An incorrect or missing CORS policy could potentially cause issues with submitting labels.
-
UI Template: If you're using a custom labeling job, double-check your UI template. Make sure it's properly configured and doesn't have any errors that might prevent the Submit button from functioning correctly.
-
Input Manifest and Output Path: Verify that you've correctly specified your input manifest location and output path when setting up the labeling job. Incorrect configurations here could potentially cause issues with submitting labels.
-
Browser Compatibility: Try using a different web browser to access the labeling UI, as sometimes browser-specific issues can occur.
-
Clear Cache and Cookies: Clear your browser's cache and cookies, then try accessing the labeling UI again.
If none of these suggestions resolve the issue, I recommend contacting AWS Support for further assistance. They can provide more specific troubleshooting based on your exact setup and configuration.
Sources
Create a Labeling Job - Amazon SageMaker AI
Accelerate custom labeling workflows in Amazon SageMaker Ground Truth without using AWS Lambda | AWS Machine Learning Blog
answered 2 years ago
Relevant content
- AWS OFFICIALUpdated 2 years ago
