Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

COS_ENDPOINT is NOT the COS_ENDPOINT in COS Credentials but the endpoint in UI/COS/Endpoint #9

Open
remkohdev opened this issue Apr 12, 2020 · 0 comments

Comments

@remkohdev
Copy link

remkohdev commented Apr 12, 2020

E.g. the .env config for COS_ENDPOINT suggest an example

COS_ENDPOINT=<cloud object storage endpoint. e.g. s3.eu-gb.cloud-object-storage.appdomain.cloud>

but the COS credentials lists the following endpoint

"endpoints": "https://control.cloud-object-storage.cloud.ibm.com/v2/endpoints",

It should be pointed out that the COS_ENDPOINT meant here is obtained by going to the COS / Endpoint menu item in the UI...

image

not the Endpoints in credentials

image

Actually it's even more confusing, cause I think this is the correct location, on the config page of the bucket itself, and there's a choice between public, private, direct???

image

It's also here I think that the IAM_ROLE_CRN is taken from???? instead as the one from the credentials file?

and a 3rd point of confusion is that the COS instance has an api key for the whole instance AND just one for the Bucket... it should be pointed out which API KEY should be used here!!!

image

@remkohdev remkohdev changed the title COS_ENDPOINT format example should be similar to COS Credentials COS_ENDPOINT is NOT the COS_ENDPOINT in COS Credentials but the endpoint in UI/COS/Endpoint Apr 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant