A Cloud Object Storage URI Formats

The URI format to use when specifying source files in cloud object storage services depends on the object storage service you are using.

Oracle Cloud Infrastructure Object Storage URI Format

If your source files reside on the Oracle Cloud Infrastructure Object Storage you can use Oracle Cloud Infrastructure native URIs or the Swift URIs. The format for files can be either:

https://objectstorage.region.oraclecloud.com/n/object_storage_namespace/b/bucket/o/filename
or
https://swiftobjectstorage.region.oraclecloud.com/v1/object_storage_namespace/bucket/filename

For example, the Native URI for the file channels.txt in the atpc_user bucket in the atpc object storage name in the Phoenix data center:

https://objectstorage.us-phoenix-1.oraclecloud.com/n/atpc/b/atpc_user/o/channels.txt

For example, the Swift URI for the file channels.txt in the atpc_user bucket in the atpc object storage name in the Phoenix data center:

https://swiftobjectstorage.us-phoenix-1.oraclecloud.com/v1/atpc/atpc_user/channels.txt

You can find the URI from the Oracle Cloud Infrastructure Object Storage "Object Details" in the right hand side ellipsis menu in the Object Store:

  1. From the Oracle Cloud Infrastructure left navigation list click Object StorageObject Storage.
  2. From the Name column, select a bucket.
  3. In the Objects area, click View Object Details.
  4. On the Object Details page, the URL Path (URI) field shows the URI to access the object.

Note:

The source files need to be stored in an Object Storage tier bucket. Autonomous Transaction Processing does not support buckets in the Archive Storage tier. See Overview of Object Storage for more information.

Oracle Cloud Infrastructure Object Storage URI Format Using Pre-Authenticated Request URL

If your source files reside on the Oracle Cloud Infrastructure Object Storage you can use Oracle Cloud Infrastructure pre-authenticated URIs. When you create a pre-authenticated request, a unique URL is generated. You can then provide the unique URL to users in your organization, partners, or third parties to access the Object Storage resource target identified in the pre-authenticated request.

Note:

Carefully assess the business requirement for and the security ramifications of pre‑authenticated access. When you create the pre-authenticated request URL, note the Expiration and the Access Type to make sure they are appropriate for your use.

A pre-authenticated request URL gives anyone who has the URL access to the targets identified in the request for as long as the request is active. In addition to considering the operational needs of pre-authenticated access, it is equally important to manage its distribution.

The format for pre-authenticated request URLs is:

https://objectstorage.region.oraclecloud.com/p/encrypted_string/n/object_storage_namespace/b/bucket/o/filename

For example, a sample pre-authenticated URI for the file channels.txt in the atpc_user bucket in the atpc object storage name in the Phoenix data center:

https://objectstorage.us-phoenix-1.oraclecloud.com/p/2xN-uDtWJNsiD910UCYGue5/n/atpc/b/atpc_user/o/channels.txt

See Using Pre-Authenticated Requests for more information.

Oracle Cloud Infrastructure Object Storage Classic URI Format

If your source files reside in Oracle Cloud Infrastructure Object Storage Classic, see the REST page for a description of the URI format for accessing your files: About REST URLs for Oracle Cloud Infrastructure Object Storage Classic Resources.

View the Oracle Cloud Infrastructure Object Storage Native URI

If you are using Oracle Cloud Infrastructure Object Storage you can find the URI for your files from the Oracle Cloud Infrastructure console.

  1. Sign in to your Oracle Cloud Account at cloud.oracle.com.
  2. From the Oracle Cloud Infrastructure left navigation list click Object Storage → Object Storage.
  3. On the Object Storage Buckets page, select your bucket. For example select the credit bucket.
  4. On the Bucket Details page, under Objects, click …-> Details to show the object details.
  5. Copy the path in the field URL Path (URI).