Oracle Cloud Infrastructure Documentation
Try Free Tier

Overview of Artifact Registry

Oracle Cloud Infrastructure (OCI) Artifact Registry is a repository service for storing, sharing, and managing software development packages.

With Artifact Registry, you can manage artifacts as follows:

  • Make artifacts immutable.
  • Identify artifacts with secure hash.
  • Add versions.
  • Upload and download.
  • Fetch the latest.
  • Control visibility and permissions.
Important

Pay attention to the type of file that you're saving. Store non-container generic artifacts or blobs in Artifact Registry. Store container images such as Docker images in Container Registry. Create and store custom compute images with Compute.

Accessing the Artifact Registry Service

Use any of the following options to access Artifact Registry.

The Console
From a supported browser, sign in to the Console. Open the navigation menu and click Developer Services. Under Containers & Artifacts, click Artifact Registry.
API Endpoints
See Artifacts and Container Images API and Generic Artifacts Content API for endpoint details. For OCI APIs, see API Reference and Endpoints. For information about using the API and signing requests, see REST APIs and Security Credentials.
OCI CLI
OCI CLI provides quick access and full functionality without the need for programming. See Command Line Reference for Artifact Registry.
SDKs
To use Artifact Registry with applications, you can use Oracle-provided Software Development Kits and Command Line Interface. The SDKs can interact with Artifact Registry resources without the need to create a framework.
Tip

To use the OCI CLI or REST APIs, either use OCI Cloud Shell or set up OCI CLI in a local environment. For Cloud Shell, see Using Cloud Shell and the OCI CLI Reference. To install the OCI CLI in a local environment, follow the steps in the CLI Quickstart.

This guide includes instructions for the Console, REST APIs, and OCI CLI.

Regions and Availability Domains

Oracle Cloud Infrastructure (OCI) services are hosted in regions and availability domains.

A region is a localized geographic area, and an availability domain is one or more data centers in that region.

Regions with Artifact Registry are listed and updated here:

Cloud Regions for Infrastructure and Platform Services

For region names and their identifiers, see the table on the Regions and Availability Domains page.

Service Limits for Artifact Registry

In each region that's enabled in a tenancy, you can create up to 500 repositories in Artifact Registry consuming a maximum of 500 GB in total.

You're charged for stored artifacts, as shown in the Cloud Price List for Artifact Storage.

Integration with the DevOps Service

In the DevOps service, you can include artifacts from Artifact Registry or Container Registry:

  1. Create a deployment pipeline in the DevOps service.
  2. Define stages for delivering artifacts to a target environment.
  3. Point to the artifacts stored in Artifact Registry or Container Registry.
  4. Run the DevOps deployment and deliver the artifacts to the target environment.

For more information about how to use Artifact Registry artifacts in the DevOps service, see the following topics:

Important

Artifact Registry doesn't display the history of artifacts uploaded to other services. To view which artifacts are delivered through DevOps pipelines, in the Console, navigate to the DevOps service and check the DevOps deployment history.

Resource Identifiers

Artifact Registry resources, like most OCI resources have a unique, Oracle-assigned identifier called an Oracle Cloud ID (OCID).

The Artifact Registry repositories have an OCID with the format, ocid1.artifactrepository.<unique-id>. The artifacts have a format of ocid1.genericartifact.<unique-id>

For information about the OCID format and other ways to identify resources, see Resource Identifiers.

Was this article helpful?