【ORACLE】dbms_cloud包使用的各大云厂商对象存储的username及password位置

前言

之前没有万事达和visa卡，想测试oracle各种功能，比如dbms_cloud，遇到了点麻烦，当天就申请了万事达卡，结果卡还没到，第二天就用京东云和腾讯云跑通了。
https://www.darkathena.top/archives/dbmscloudjdcloudoss
https://www.darkathena.top/archives/dbmscloudrelated

然后今天我的万事达卡到了，赶紧去银行把卡开了，然后马不停蹄地赶回家，直接就把国外三大云服务厂商的免费套餐都申请了

然后这三家全部都用dbms_cloud包上传成功，中间找api要用的username及password费了不少时间，所以本文就收集整理各个云厂商对象存储针对dbms_cloud包的username及password位置。

begin
  dbms_cloud.create_credential (
    credential_name => credential_name ,
    username        => username        ,
    password        => password        );
end;
/

先上官方文档

https://docs.oracle.com/en/cloud/paas/autonomous-database/adbdh/#ADBDH-GUID-0C42BA43-3960-416D-B351-FDFBA8733847

Oracle Cloud Infrastructure Credentials (Auth Tokens)

For Oracle Cloud Infrastructure the username is your Oracle Cloud Infrastructure user name. The password is your Oracle Cloud Infrastructure auth token. See Working with Auth Tokens.

Oracle Cloud Infrastructure Object Storage Classic Credentials

If your source files reside in Oracle Cloud Infrastructure Object Storage Classic, the username is your Oracle Cloud Infrastructure Classic user name and the password is your Oracle Cloud Infrastructure Classic password.

Amazon Web Services (AWS) Credentials

If your source files reside in Amazon S3 or you are calling an AWS API, the username is your AWS access key ID and the password is your AWS secret access key. See AWS Identity and Access Management.

Microsoft Azure Credentials

If your source files reside in Azure Blob Storage or you are calling an Azure API, the username is your Azure storage account name and the password is an Azure storage account access key. See About Azure storage accounts.

Amazon S3-Compatible Credentials

Service Credentials Information

Oracle Cloud Infrastructure (Customer Secret Keys)

If your source files reside in Oracle Cloud Infrastructure, then you need to use Customer Secret Keys with S3-compatible URLs. See Working with Customer Secret Keys for more information.

Google Cloud Storage

If your source files reside in Google Cloud Storage or you are calling Google Cloud Storage APIs, then you need to set a default Google project and obtain an HMAC key to create credentials to supply with Google Cloud Storage S3-compatible URLs. Use the HMAC key id as the username, and the HMAC secret as the password.

See Projects and HMAC Keys for more information.

Wasabi Hot Cloud Storage

If your source files reside in Wasabi Hot Cloud Storage or you are calling Wasabi Hot Cloud Storage APIs, then you need Access Keys to create credentials to supply with S3-compatible URLs. Use the Wasabi Hot Cloud Storage Access Key as the username, and the Wasabi Hot Cloud Storage Secret Key as the password.

See Creating a Wasabi API Access Key Set for more information.