Interacting with OCI Object Storage using Go SDK (first steps) image 101

Interacting with OCI Object Storage using Go SDK (first steps)

I am still fairly new at working with Go. I have the ambition of working with and perhaps even on several open source projects that all use Go as their implementation language. It seems like the number of open source projects that use Go is increasing [rapidly]. It seems that I need to get acquainted more with Go and I need to find out how to interact from Go with Oracle Cloud Infrastructure (OCI). (I intend to add features to open source products that leverage OCI services).


In this article a quick introduction into interaction with the OCI Object Storage Service for creating and removing a bucket and an object in that object from a simple Go program that uses the OCI Go SDK. My environment is Ubuntu 20.4 on WSL2 on Windows 10,  although that should not matter much.

The steps I go through in this article:

  • install a Go environment
  • create a Go application to connect to OCI using the OCI SDK
  • interact with OCI Object Storage

Install Go

Using this article:  Install Go on Ubuntu –  – I quickly got the current version of Go removed and the latest version of Go installed.


Go get the URL for the latest release:


Download using wget and untar


Then move the extracted directory go to the /usr/local directory:


I tried to run go at this point, but I was too early. First, a small edit of .profile is in order: add the definition of environment variable GOPATH and add $GOPATH to the PATH environment variable.


Once the change is made to .profile and the change has been applied with source ~/,profile the environment is once again ready to run go, the latest version.

    Create a Go application to connect to OCI using the OCI SDK

    On the Linux command line, I create a new directory – oci-client – and with “code .” I launch VS Code on this directory.


    I can edit code in VS Code and run the code in the context of the Ubuntu environment with the Go runtime set up. Let’s create the simplest of Go applications.


    And run it.

    No interaction with OCI yet, but a running Go application is a nice start.

    Now create go.mod and add this contents:

    module oci-client

    go 1.16

    require v54.0.0

    Then run:  “go mod tidy” (see docs for help): “go mod tidy ensures that the go.mod file matches the source code in the module. It adds any missing module requirements necessary to build the current module’s packages and dependencies, and it removes requirements on modules that don’t provide any relevant packages. It also adds any missing entries to go.sum and removes unnecessary entries. “

    Define constants in the application for the tenancy OCID, the user OCID, the region and the fingerprint (the usual entries in the oci config file):


    Import these packages:


    Extend the application to the following listing – with functions initializeConfigurationProvider (to contact OCI) and listDomains (to interact with the identity service APIs


    Finally create a file – for example called ppk (putty private key) – that contains the private key for an OCI account in PEM format.


    WIth this in place, I can run the application.

    The first action is to export an environment variable with the contents of the file ppk as its value:

    export pem=$(cat ./ppk)

    This makes the private key accessible to the Go application, using os.Getenv(“pem”).


    And there is contact between my locally running Go application and the OCI.

    Interact from Go Application with OCI Object Storage

      Time now to introduce the Object Storage APIs in the SDK (see docs here). These will allow us to create  buckets and objects in those buckets from the Go application. And that is a capability I will need when I implement a custom Dapr state component leveraging OCI Object Storage – as is my ambition.

      Let’s run the Go application I have crafted:

      The result of running this code is the creation of a Bucket:


      and a new file with the specified contents in this bucket:


      Inspect the contents by downloading and view the object to my local file system:


      So my Go application works with OCI Object Storage.

      The main function in the application orchestrates the moves:


      The configurationProvider contains the OCI connection details (such as OCIDs for tenancy and user, the fingerprint and private key). This provider is used to create the objectStorageClient – which is used for all subsequent interactions with the OCI ObjectStorage service.

      The steps subsequently taken:

      • determine the namespace for the tenancy
      • ensure that a bucket with the specified name exists – check if it is there already and if it is not, then create it
      • put an object with the specified name and contents in the bucket (overwrite the object that may already be there under that name)
      • defer the statement that will remove the object again
      • retrieve the object that was just created and write it contents to the output
      • sleep for one minute and afterwards execute all deferred statements (which means that the object is removed)

      This code is not robust, it does hardly any error checking and handling. It most certainly cannot be used in anything like a production environment. However, it does illustrate how the ObjectStorage service is interacted with through the Go SDK and under the right circumstances, it certainly does the job of creating the bucket and the object, reading the object and removing it.

      Let’s look at the code in a little more detail: this code for initializing the OCI Configuration Provider is generic across all Go applications that interact with whatever OCI services. It uses common OCI configuration details – commonly found in the config file in directory .oci when using the OCI CLI – to create signed HTTP requests to the OCI REST APIs


      The code that checks if a bucket already exists – by getting it and checking on status code 404 (not found) and creating the bucket if it was not found – is show below. Note that the getBucketRequest struct expects pointers to strings for namespacename and bucketname (see docs), hence the &namespace and &name to produces the addresses for these string values (one of the intricacies of Go I am still getting used to)


      With the Bucket established, creating the object is done as follows:


      This is quite straightforward code – except for the way in which the string that contains the object;s content is turned into a reader object (or at least to me that looks a bit special).

      To retrieve an object from the OCI Object Storage service is more or less the reverse operation from putObject:


      This function returns the contents of the object as a string – assuming that it is at all meaningful to turn this object into a string. Note that the response object returns pointers to ContentLength, ContentType and Content. The asterisk (*response.Content:Length) is used to retrieve the actual value (at the pointer’s location).

      Finally to delete the object – the simplest of the operations:


      The full code for my OCI ObjectStorage sample client is shown below


      Package Index:

      Configuring Go SDK: 


      OCI Object Storage REST API – 

      OCI Go SDK – generated client for GetObject – 

      OCI Go SDK – ObjectStorage Package Index –

      Leave a Reply

      This site uses Akismet to reduce spam. Learn how your comment data is processed.