- Newest
- Most votes
- Most comments
It seems you're encountering two separate issues with your SageMaker domain setup. Let's address each problem:
-
ValidationException during domain creation: This error suggests there's an issue with the configuration of the generative AI models, specifically with the input modalities. The error indicates that 'SPEECH' is not a valid input modality for one of the models. This could be due to an incompatibility between the selected models and their supported input types. To resolve this, you may need to review and adjust the generative AI settings in your domain configuration. Ensure that the input modalities specified for each model are compatible with what the model supports.
-
"No data to show" in Project Profile: This issue could be related to the domain setup or permissions. Even after successfully creating a domain, if project profiles are not appearing, it might indicate a problem with the domain's configuration or the associated roles and permissions. Here are a few steps to troubleshoot:
a) Verify that your domain is in the "InService" status. You can check this in the SageMaker console under the Domains section.
b) Ensure that the necessary IAM roles and permissions are correctly set up for your domain and user profile. The domain execution role and user profile roles should have the appropriate permissions to create and manage projects.
c) Check if there are any failed updates or configurations in your domain. You can do this by calling the DescribeDomain API or checking the domain details in the console.
d) Make sure your AWS account is properly set up to use the SageMaker projects feature. There might be additional configurations or allowlisting required for your account in the specific AWS region you're using.
If these steps don't resolve the issue, you may need to contact AWS Support for further assistance. They can help investigate any account-specific issues or regional limitations that might be preventing the project profiles from appearing.
Remember to double-check all configurations and permissions, and consider recreating the domain if the issues persist after troubleshooting.
Sources
Troubleshoot connectivity issues between SSM and my SageMaker endpoint | AWS re:Post
Amazon SageMaker AI domain entities and statuses - Amazon SageMaker AI
Create a Amazon SageMaker Unified Studio domain - quick setup - Amazon SageMaker Unified Studio
Relevant content
- AWS OFFICIALUpdated 9 months ago
After reading this, I think it'll be faster to erase everything. Thank you