When configuring storage locations in Zenko Orbit, you need to enter some combination of access key, secret key, and account name. All this information varies by cloud provider and it can be annoyingly complicated to find all that information. This cheatsheet will help you configure access to AWS, Azure and Google for Zenko Orbit.
This document assumes you know how to log into the AWS, Azure and Google cloud portals and that you know how to create a storage location in Zenko Orbit.
|Location name = any descriptive name; “aws-location” “aws-demo” etc.|
AWS Access Key and AWS Secret Key: https://console.aws.amazon.com/iam/home?#/security_credential
Target Bucket Name = name of existing Bucket in Amazon S3
|Location name = any descriptive name; “azure-location” “azure-demo” etc.|
Azure Storage Endpoint = the “Blob Storage Endpoint” located on the top right of the Overview tab for your storage account (screenshot below).
Azure Account Name = the name of your Azure storage account located on the top of the Azure Portal (screenshot below – “scalitydemo” is Azure Account Name).
Azure Access Key = the “key1 / Key” visible when you select Access Key in the Azure Portal.
Target Bucket Name = name of existing Container in Azure
|Location name = any descriptive name; “gcs-location” “gcs-demo” etc.|
GCP Access Key and Secret Key = navigate to GCP Console / Storage / Settings / Interoperability Tab (see screenshot below
Target Bucket Name = name of existing Bucket in Google Cloud Storage
Target Helper Bucket Name for Multi-part Uploads = name of existing Bucket in Google Cloud Storage
(Google Cloud Storage handles MPU in such a way that Zenko requires a second bucket for temporary staging purposes)