-
Notifications
You must be signed in to change notification settings - Fork 378
Ag pub2priv #8468
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
base: develop
Are you sure you want to change the base?
Ag pub2priv #8468
Conversation
Changelog: - creation of the file
will be removed then
…Rack/images/test Delete test file
new meta.yaml file
update index file w/ s3_interconnect_with_vRack
FR guide version
add conclusion
typos
change arbo
change arbo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reuse ID and slug from previous PR
test file for new folder - will be removed
…vate_network directory
meta.yaml file in the corresponding folder
Move file to the right folder /connect_other_ressources_in_vrack_private_network/
Move file in the correct folder /connect_other_ressources_in_vrack_private_network/
…kets_vrack_private.png Move image in the correct folder /connect_other_ressources_in_vrack_private_network/
…Rack/meta.yaml Remove older meta.yaml file
Update index with correct path: storage_and_backup/object_storage/connect_other_ressources_in_vrack_private_network/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see my comment
} | ||
``` | ||
|
||
To set this new policy to your S3 user, please follow the different steps shared in the [Object Storage - Identity and access management](/pages/storage_and_backup/object_storage/s3_identity_and_access_management) guide, and finalise the interconnection between your Object Storage resources and those within your vRack private network. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe add some additional infos :
- there are exceptions regarding 'the bucket owner' --> it could be a best practice to not use the bucket owner and create other users instead
- a policy has to be applied to each user accessing the buckets/objects
Description
This guide used to be part of our docs, but was deleted then. We updated the content and made it available again.
Mandatory information
This Pull Request can be merged as soon as possible.
Tech review being needed
This Pull Request content should be replicated for the US OVHcloud documentation : YES