How to find keys and account info for AWS, Azure and Google

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 […]

Written By Stefano Maffulli

On June 12, 2018
"

Read more

Solve the challenges of large-scale data, once and for all.

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.

AWS

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

  • You may or may not have IAM roles set up in your account. If not, press the Continue to Security Credentials button
  • Press the “+” sign next to “Access keys (access key ID and secret access key)”
  • Prease the Create New Access Key Button
  • Window will appear with your Access and Secret Key (screenshot below)
  • Copy/paste your Secret Key somewhere safe.

Target Bucket Name = name of existing Bucket in Amazon S3

Azure

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

Google

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)

Richard Payette

Simple, secure S3 object storage software for modern applications