New Object Storage guide for Swift to S3-compatible object storage migration #8514
+299
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Create the empty EN-GB guide
First draft of the guide
Changelog: - new meta.yaml file
add new entry in Tutorials section of Object Storage guides
Changelog: - typo in arbo
agoude
added
Guide creation
Y0Coss
reviewed
Oct 13, 2025
pages/storage_and_backup/object_storage/s3_migration_swift_to_s3/guide.en-gb.md
Outdated
Show resolved
Hide resolved
…s3/guide.en-gb.md Co-authored-by: Yoann Cosse <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of Pull Request is this?
Description
This guide aims to provide migration guidelines using rclone to move from Swift Object Storage to S3-compatible Object Storage.
Mandatory information
This Pull Request can be merged as soon as possible as soon as reviewed.
This Pull Request content should be replicated for the US OVHcloud documentation : YES