- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello.
I installed self-hosted GitLab Community Edition on an EC2 instance and tried connecting with Glue.
As a result, I was unable to connect.
I'm guessing that you probably won't be able to connect to self-hosted GitLab.
I tried issuing an access token with the necessary permissions, but I cannot select the repository as shown in the image below.
It's possible that my settings are incorrect, so please try it yourself.
Yes, AWS Glue Studio's Git integration feature supports GitLab running on an organization's host (self-managed GitLab) as long as it is accessible via a public or private URL. The URL does not need to be https://gitlab.com/; it can be any valid GitLab instance URL that your organization uses.
To integrate a self-managed GitLab instance with AWS Glue Studio, you'll need to provide the appropriate Git repository URL and ensure that Glue Studio can access it. Authentication methods such as SSH keys or personal access tokens should be correctly configured to allow AWS Glue to interact with the repository.
Make sure that your self-managed GitLab instance meets the necessary network and security configurations to be accessible from AWS Glue.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
If you used the access token set at gitlab.com, you could set up the repository as follows. Based on this result, we determined that it cannot be used with self-hosted GitLab.
I tried setting the repository owner name and repository domain name for self-hosted GitLab, but I was unable to connect to any of the settings.