-
Notifications
You must be signed in to change notification settings - Fork 366
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
feat(getting started s3): fusion between aws cli and manager getting started guide #7605
base: develop
Are you sure you want to change the base?
Conversation
pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-gb.md
Outdated
Show resolved
Hide resolved
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.
@OvhValentin je te laisse check en plus de mes commentaires via webex ;) thx!
@@ -16,42 +39,56 @@ This guide is designed to familiarise you with the management of your containers | |||
|
|||
## Instructions | |||
|
|||
### Using AWS CLI | |||
### Preparation |
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.
j'ajouterai également un avertissement stp :
Avertissement sur la compatibilité de la CLI et du SDK AWS
Récemment, Amazon Web Services (AWS) a effecuté une modification qui renforce les checksum lors d'opérations via l'API S3. Ces nouveaux contrôles d’intégrité sont en cours d'intégration sur notre plateforme. Aussi les headers suivants ne sont pas supportés :
- x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
- x-amz-sdk-checksum-algorithm with value CRC32
En attendant la mise à jour sur notre Object Storage, nous vous invitons à utiliser les versions max. supportées suivantes de la CLI, SDK et autres outils AWS:
- boto3 1.35.99
- legacy aws cli 1.36.40
- aws cli 2.22.35
- aws-sdk-go 1.72.3
- aws-sdk-java 2.29.52
- aws-sdk-js-v3 3.726.1
- aws-sdk-net 3.7.962.0
- aws-sdk-php 3.336.15
- aws-sdk-ruby 1.177.0
Pour en savoir plus : https://docs.aws.amazon.com/fr_fr/sdkref/latest/guide/feature-dataintegrity.html
Suivi de la mise à jour chez OVHcloud : https://public-cloud.status-ovhcloud.com/incidents/491vx956zx6b
pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-gb.md
Show resolved
Hide resolved
pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-gb.md
Outdated
Show resolved
Hide resolved
> - If you are interested in the **Standard object storage - SWIFT API** storage class, follow this [guide](/pages/storage_and_backup/object_storage/pcs_create_container) | ||
> - If you are interested in the **Cloud Archive - SWIFT API** storage class, follow this [guide](/pages/storage_and_backup/object_storage/pca_create_container). | ||
> | ||
|
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.
J'aimerais qu'on limite les références à SWIFT, aussi si possible je préciserai qu'il s'agit d'offres legacy par ex:
If you are using legacy SWIFT Object Storage, then:
- for Standard object storage - SWIFT API storage class, follow this guide
- for Cloud Archive - SWIFT API storage class, follow this guide.
For new projects we highly recommend using our S3-compatible Object Storage which benefits from our latest innovation and new features.
un truc comme ça ;)
Refer to SK-1822.