Bridging the Gap: Accessing Private Artifactory from GitHub Actions Across the Network
Published on October 29, 2025 | Written by Andreas
Artifactory is a popular repository manager allowing teams to share artifacts. For example, Artifactory supports the following package types.
- Ansible
- CocoaPods
- Debian
- Docker
- Gradle
- Helm
- Maven
- npm
- PyPi
- RPM
- …
Typically, Artifactory is used to share internal packages within an organization. Often times, connectivity to private networks is required to access an Artifactory server. In the following blog post, you will learn how to ensure CI/CD jobs orchestrated by GitHub Actions can access an Artifactory server running in a private network.
The problem: GitHub-hosted runners can neither pull nor push artifacts from Artifactory
By default, GitHub Actions executes jobs on GitHub-hosted runners. Those runners come with connectivity to the Internet but cannot access resources in private networks. Therefore, pushing a new container image from GitHub Actions to an Artifactory server connected with a private network fails.
The solution: Deploy self-hosted runners into a VPC to access Artifactory
Use self-hosted runners instead of GitHub-hosted runners enables you to deploy runners into a VPC (Virtual Private Cloud), a virtual private network provided by AWS. Doing so enables CI/CD jobs to pull and push software packages from an Artifactory server.
The solution works in two scenarios:
- Artifactory is running in a VPC on AWS
- Artifactory is running in a private network that is connected with a VPC on AWS
But isn’t deploying self-hosted runners on AWS a lot of work? No, it takes about 10 minutes. Read on to learn more.
HyperEnv for GitHub Actions Runner
We designed a solution to deploy self-hosted GitHub Actions runners for AWS with ease: HyperEnv.
HyperEnv is a secure, highly scalable, and fault-tolerant solution that launches EC2 instances acting as ephemeral runners for GitHub Actions. The following figure provides insights into the architecture.
- Serverless backend: API Gateway, Lambda, Step Functions, and DynamoDB
- Powerful and cost-efficient compute: EC2 and EBS
Deploy the whole production-ready setup in just 10 minutes by following our setup guide.
Ensure you choose the Fulfilment Option named Bring Your Own VPC and configure the parameters VpcId and SubnetIds to deploy HyperEnv into an existing VPC, enabling connectivity with your Artifactory server.
Summary
Struggling because GitHub-hosted runners can’t access your Artifactory repository in a private network? The solution is simple: deploy self-hosted runners directly into your VPC for seamless connectivity! Get started quickly with HyperEnv, our secure, scalable, and ephemeral self-hosted runner solution that deploys into your existing VPC in about 10 minutes.