Verify the accuracy of the Git repository URLīe sure that the Git repository URL that you're adding is in the following format: If you use a VPC, be sure that the subnets, security groups, network access control Lists (ACLs), NAT gateway, internet gateway, and route tables are configured correctly. Your VPC doesn't have direct internet access.Your Amazon VPC has direct internet access.The instance isn't attached to an Amazon Virtual Private Cloud (VPC).The notebook instance might have one of the following network configurations: This repository might be located either on an on-premises Git repository server or a public cloud server, such as GitHub, Bitbucket, or GitLab.Ĭheck the network configuration that your notebook instance is using. Verify the notebook instance connectivityīe sure that notebook instance has successfully connected to the Git repository. Verify the accuracy of the Git repository URL.Verify the notebook instance connectivity.To resolve these errors, do the following: "fatal: unable to access could not resolve the host: …". ![]() "fatal: unable to access : failed to connect to …: port 443: connection timed out"."fatal: unable to access : the requested URL returned error: 403".If there are connectivity issues, you might get one of the following errors: If you're trying to add a Git repository that's not hosted on AWS CodeCommit, you might get the following errors. To add a new Git repository to your SageMaker notebook instance, see Add a Git repository to your Amazon SageMaker account.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |