Skip to content

Remove merging issues in Update S3 storage documentation for TLS usage #316

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.

Sign up for GitHub

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

Merged
nastena1606 merged 1 commit into from
Nov 12, 2025
Merged

Remove merging issues in Update S3 storage documentation for TLS usage #316

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions docs/details/s3-storage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,8 +150,6 @@ retryer:

This upload retry increases the chances of data upload completion in cases of unstable connection.

<<<<<<< HEAD
=======
## Data upload to storage with self-signed TLS certificates

Percona Backup for MongoDB supports data upload to S3-compatible storage service over HTTPS with a self-signed or a private CA certificate. This feature is especially important when you use services like MinIO, Ceph, or internal S3 gateways that don't use certificates signed by public Certificate Authorities (CAs).
Expand Down Expand Up @@ -203,6 +201,4 @@ pbm config --set storage.s3.insecureSkipTLSVerify=True
!!! warning

Use this option with caution as it might leave a hole for man-in-the-middle attacks.
>>>>>>> Removed prompt sign from code blocks