SageMaker Studio launch stuck on loading screen

Looks like it's something to do with networking, if a domain set up with Quick Setup is working as expected. Here's a troubleshooting guide - https://docs.aws.amazon.com/sagemaker/latest/dg/studio-troubleshooting.html

I'd also recommend creating a SageMaker notebook instance with the same VPC/subnet configuration as the Studio domain, and check if that spins up and if you're able to access the notebook.

Given the information you provided, it seems like the issue might be related to the VPC configurations, especially since the domain created through Quick Setup works fine within the same VPC.

Subnet Configuration: Double-check that the subnet in which SageMaker Studio is launched has routes to the internet. SageMaker Studio requires internet connectivity, usually through a NAT Gateway or NAT Instance, to pull necessary container images and other resources.

NAT Configuration: Ensure the NAT Gateway or Instance is properly set up and functioning. It should be in a subnet that itself has a route to an internet gateway. Check if other resources within the same subnet can access the internet.

Security Groups: Double-check the security group attached to the SageMaker Studio domain. It should allow all outbound traffic. It's also worth checking inbound rules, especially if you have specific rules set for resources within the VPC.

Service Endpoints: When using SageMaker within a VPC, ensure that you have created the necessary VPC endpoints for SageMaker services, and that they are associated with the correct subnets.

IAM Policies: Ensure the SageMaker Studio domain has the necessary IAM permissions. Sometimes, the issue might be a missing IAM permission, which might not be as intuitive to diagnose when dealing with VPCs. Ensure the execution role associated with SageMaker Studio can make calls to other AWS services that it needs to.

After making any changes, try to relaunch SageMaker Studio. If the issue persists, consider checking CloudWatch logs or SageMaker logs for more specific error messages, which can guide further troubleshooting.