The process of setting up an AWS PrivateLink connection is split between AWS and JFrog. These are the high-level steps you will need to complete for this procedure.
If you want to use your own custom domain to access your JFrog Platform instance (e.g., jfrog.your-company-domain.com), but have not yet set one up, do so now before beginning the process detailed below. Contact JFrog support to set up this configuration for you.
|JFrog Cloud||AWS Console|
|Step 1: Create an endpoint in your AWS account|
|Step 2: Create an AWS PrivateLink in MyJFrog|
|Step 3: Set up your DNS in AWS|
|Step 4: Validate the private connection|
|Step 5 (Optional): Block public access|
|Step 6 (Recommended): Set up a Gateway VPC Endpoint for Amazon S3|
Create an endpoint in your Virtual Private Cloud (VPC) (see the AWS instructions for additional details on creating an interface endpoint to an endpoint service).
In the table below, locate the Service Name values for the region you are setting up. The PrivateLink is set up by JFrog in the supported AWS regions under the following service names:
AWS Public Regions
|Supported Availability Zones|
VPC Service Name
In the AWS Console, go to Endpoints > Create Endpoint.
Select the option Find service by name.
Enter the service name for your region and click Verify.
The endpoint you create in AWS must be in the same region as the PrivateLink you create in JFrog.
AWS verifies the service name you entered.
Scroll down to the VPC dropdown list and select the relevant VPC.
Scroll to the bottom of the window and click Create endpoint.
AWS creates the endpoint and displays the VPC Endpoint with the VPC Endpoint ID.
The ID will be in the following format:
Log in to MyJFrog.
Click the Actions dropdown menu and select PrivateLinks.
This opens the Manage Private Connections window. Any previously configured PrivateLinks will appear here.
Click +Create New and then choose the provider you wish, in this case AWS PrivateLink.
This displays the Create AWS PrivateLink window.
In the Endpoint ID field, enter the ID you copied from AWS in step 1.
Verify that the endpoint ID you enter is an alphanumeric lowercase string that begins with
vpce-, for example:
In the Select Region dropdown, select the relevant region.
The instances for this region will appear in the Select Instances field. Select one or more instances you want to connect. You can also choose to Select All instances.
In the Manage Private Connections table you will see the current status of the configured endpoints (this process may take a while). Once a PrivateLink has been set up, you will receive a confirmation email and the status in the Manage Private Connection table will change to Connected.
To add additional endpoints to the instance, you will need to verify that all failed endpoints are fixed.
The purpose of this procedure is to ensure that all traffic originating from your own AWS VPC, going out to your JFrog JPD (residing in the same region) will be routed automatically via the PrivateLink, rather than via public Internet. Traffic going out to other JFrog domains, such as remote JPDs located in other regions, or to other JFrog services such as releases.jfrog.io, will continue to be routed via public Internet.
Once you set up an AWS PrivateLink via MyJFrog, JFrog automatically creates an additional domain name that reaches your instance, in the format acme.pe.jfrog.io. This domain will be used by your PrivateLink setup. For example, if your standard public JFrog domain is myservername.jfrog.io, then the additional domain will be myservername.pe.jfrog.io.
How you choose to set up your DNS in AWS depends on your organization's architecture, in which there are two factors:
To better understand these options, they have been broken down into the section below, with diagrams to illustrate how they work.
If you are already using your own custom domain name to access your JFrog instance (e.g., ), follow these steps to configure your private DNS. How you set up depends on the type of connection.
In this configuration, you will set up a CNAME that points your company domain name, e.g., jfrog.acme.com, to the PrivateLink DNS name. If you are accessing your Docker repositories using the Docker subdomain method (e.g., docker-reponame.myservername.acme.com), set up another CNAME that points the docker subdomains (e.g., *.myservername.acme.com), to the PrivateLink DNS name.
In the diagram below, you can see the steps required to map the custom domain to the DNS of the endpoint.
In this flow, the DNS resolution is not performed through the AWS service but from your corporate data center. Your data center DNS resolution will, therefore, need to know to point from the custom domain name to the DNS.
Set up a private hosted zone for pe.jfrog.io, and create a DNS CNAME record that points *.pe.jfrog.io (or, if you need to reach multiple Artifactorys in multiple PrivateLinks, for example, yourcompanyname.pe.jfrog.io) into the PrivateLink's DNS name. Once the DNS record is ready, configure your clients to hit the PrivateLink JFrog domain name (e.g., acme.pe.jfrog.io), so that they reach your endpoint (remember to use a hosted zone here).
As with the custom domain option, how you set up depends on the type of connection.
In this flow, you will set up the DNS to reach your JFrog PrivateLink domain name from your VPC (via Route 53 private zone DNS) directly to the JFrog VPC via the Service Endpoint.
In this flow, the DNS resolution is not performed through the AWS service but from your corporate data center. Your data center DNS resolution will, therefore, need to know to point from the JFrog domain name to the DNS.
This flow, which involves multiple jumps, will likely be the preferred option for most customers.
In this step, you will need to validate that the connection goes through the private connection rather than public Internet. To verify that your connection is indeed private, connect from your VPC to the JFrog instance by opening a command prompt and entering the following command to ping the server.
curl -v https://<customer fqdn>/artifactory/api/system/ping
curl -v https://acme.pe.jfrog.io/artifactory/api/system/ping
Verify that you are able to access the JFrog Platform. If you are able to access the Platform, your setup is complete. You should now see your next hop IP prefix with the same IP prefix as your local VPC.
The PrivateLink connection itself does not block public access to your site. To block access, you will need to add your public IPs to the Allow List. Contact JFrog Support for more information.
When performing a download request against your JFrog platform, your download may be served via a redirect to an AWS S3 bucket. Therefore, while your initial request to the JFrog platform will be routed via the PrivateLink you created in step 2 and will reach the JFrog VPC, the redirect to S3 will reach S3 via public Internet.
If your AWS VPC network policy allows egress traffic into S3 via public internet (e.g., via NAT gateway), then the download can be completed without taking any further steps. However, if your network does not allow egress traffic via public internet, or if you would like to enjoy better performance and lower data transfer costs when working against S3, follow the instructions in the AWS documentation (when creating the gateway VPC endpoint, under Policy, select the default option "Full Access").