Oracle Cloud Infrastructure Integration

Helidon SE OCI Integration provides easy access to Oracle Cloud Infrastructure.

Deprecated

The custom Helidon SE OCI clients documented here are deprecated. It is recommended that you use the OCI Java SDK directly, in particular the Async clients. For more information see:

Experimental

Helidon integration with Oracle Cloud Infrastructure is still experimental and not intended for production use. APIs and features have not yet been fully tested and are subject to change.

General Configuration

If you follow these instructions on how to Generate an API Signing Key, be advised that Helidon does not currently support passphrase-protected private keys in PKCS#1 format. If generating a private key using those instructions, use the no passphrase option.

Using Helidon SE Properties Configuration

The first option to configure connection to OCI is to directly specify properties in application.yaml file:

oci:
    config:
        oci-profile:
            user: ocid1.user....
            fingerprint: 1c:6c:....
            tenancy: ocid1.tenancy.oc1..
            region: us-...
            key-pem: <pem content>
Copied

Using OCI Configuration

The second option is via OCI configuration file. For authentication in OCI a special configuration file should be set up. The file is usually located at ~/.oci/config

[DEFAULT]
user=ocid1.user....
fingerprint=1c:6c:....
tenancy=ocid1.tenancy.oc1..
region=us-...
key_file=<path to key file>
Copied

More information how to set up on your environment: Official website