An artifact repository is one of the important components of the CI/CD flow storing artifact collections and metadata. Artifactory as a Service is a cloud-based platform service which, together with Jenkins, Gerrit and SonarQube, forms a consistent CI/CD environment.
Artifactory as a Service is based on Artifactory version 4.15.0.
For more details on working with Artifactory, visit the official Artifactory website.
This topic contains the following sections:
The current page gives the general information on the service and the main workflows. However, while working with the services, our users encounter new questions they need assistance with. The most frequently asked questions on EPAM Cloud Services are gathered on the Cloud Services FAQ page. Visit the page to check whether we have a ready answer for your question.
The table below provides the list of service-related commands and their descriptions:
| Command | Short Command | Description |
| or2-manage-service...-s artifactory -a | or2ms | Activates the Artifactory service in the specified project and region |
| or2-describe-instances...-S artifactory | or2din | Displays the details of VMs created during the service activation |
| or2-describe-services...-s artifactory | or2dser | Describes the Artifactory service activated in the specified project and region |
Further on this page, you can find more details on the Artifactory service manipulation.
To activate Artifactory as a Service, use the or2-manage-service (or2ms) command with the -a/--activate flag and the -s/--service-name parameter with the artifactory value:
or2ms -p project -r region -a -s artifactory
After the command is sent, the system requests an admin password. The password created by the user starting the service is then used to access the Artifactory server. This is an additional security measure protecting the repositories in the storage.
The service, when activated, by default starts an Artifactory server VM with the following configuration:
All artifacts are stored on the additional disk. No root disk space is used for artifact storage which guarantees reliable performance and availability.
You can find the details on the VMs created within the service activation, by calling the or2-describe-instances (or2din) with the -S artifactory parameter or or2-describe-services (or2dser) commands with -s artifactory parameter:
or2dser -p project -r region -s artifactory
/artifactory_info.png)
Once the Artifactory service has been activated, you can access its Web UI. Use the URL returned in the response to the or2ser command and log in under the username "admin" and the password specified at service activation. After you have logged in as administrator, you can create accounts for other service users.
/artifactory_ui.png)
The service usage price is defined by the price of the VM on which Artifactory is running.
The default parameters of an Artifactory instance are:
Therefore, the approximate monthly cost of an Artifactory server with 100% and 24/7 load is about $60.64 in EPAM-BY2 region (as to July 2020). The price can vary depending on the region and the usage pattern. To get more detailed estimations, please, use our Cost Estimator tool.
More information on the Artifactory Service can be found in the EPAM Cloud Services Guide. For detailed description of the Maestro CLI commands used to manage the Artifactory Service, refer to the Maestro CLI User Guide.