-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pvsadm with a private cos endpoint #117
Comments
/cc @mkumatag Below are the observations:PowerVS Environment:
VPC Environment:
Test Snnipet code used for performing the s3 operations:
Output:
|
@bpradipt we aren't able to talk to the private endpoint from either VPC or PowerVS machines, let us know if any additional n/w configuration required to talk to the private endpoint? |
@mkumatag @bpradipt with classic infra setup, using COS api's I am able to list the buckets from the COS instance, but the bucket creation operation doesn't succeed.
|
moving to 21.03 milestone |
There is requirement of using the private cos endpoint instead for the secure private n/w use case, currently I see an option
--bucket-region
to supply the region, this option is used internally to build the cos URI, this task is to supply theprivate.
prefix with this flag and make sure things are working fine(upload and import)e.g:
Public EP: s3.us-south.cloud-object-storage.appdomain.cloud
Private EP: s3.private.us-south.cloud-object-storage.appdomain.cloud
/cc @bpradipt
/assign @bkhadars
The text was updated successfully, but these errors were encountered: