JFrog PrivateLink is a solution designed to assist customers in mitigating security risks associated with exposing their JFrog SaaS instances via the public Internet. JFrog PrivateLink enables you to establish an AWS PrivateLink connection, offering a more secure environment for your data.
It's important to note that while JFrog PrivateLink focuses on enhancing security, it does not directly impact data transfer costs. Our standard data transfer cost considerations include factors such as accumulated traffic within the billing period, covering downloads, uploads, replication between JPDs, distribution to edge nodes, and communication between services (e.g., Artifactory to Xray).
The calculation of data transfer encompasses two primary sources:
The calculation of data transfer costs is based on the total traffic consumed throughout the billing period, encompassing both uploads and downloads. This includes various types of traffic, such as communication between topology members (e.g., replication from JPD to JPD, distribution to edge nodes) and traffic between services (e.g., Artifactory to Xray).
For instance, whether 4 MB is consumed from a distant remote repository outside Azure or the same 4 MB via the Azure backbone, both scenarios are considered as 4 MB of data transferred. The billing accounts for the cumulative amount of traffic, irrespective of the source or route.
It's important to note that while JFrog PrivateLink focuses on enhancing security, it does not directly impact data transfer costs. Our standard data transfer cost considerations include factors such as accumulated traffic within the billing period, covering downloads, uploads, replication between JPDs, distribution to edge nodes, and communication between services (e.g., Artifactory to Xray).
The calculation of data transfer encompasses two primary sources:
- Artifactory Downloads & Uploads
- Object Storage Downloads for Redirected Traffic
The calculation of data transfer costs is based on the total traffic consumed throughout the billing period, encompassing both uploads and downloads. This includes various types of traffic, such as communication between topology members (e.g., replication from JPD to JPD, distribution to edge nodes) and traffic between services (e.g., Artifactory to Xray).
For instance, whether 4 MB is consumed from a distant remote repository outside Azure or the same 4 MB via the Azure backbone, both scenarios are considered as 4 MB of data transferred. The billing accounts for the cumulative amount of traffic, irrespective of the source or route.