• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question How to follow advice "enable backup encryption on the cloud storage side"?

That's why any user should read up on the documentation of the cloud storage provider ;)
Perhaps you're misunderstanding me? I cannot see inside the Plesk source code for the settings/params it uses to talk to the external services, so no amount of reading up on the cloud storage provider's documentation is going to answer those questions. And when you share information here in the forum as you did above that is not in the documentation, you learned it from some source that is not readily accessible to new users, hence my request that such information is added to the documentation where we expect to find it. I really do think I'm being clear here, so please forgive me if I refrain from rephrasing my point one more time? All the best!
 
[...] I cannot see inside the Plesk source code for the settings/params it uses to talk to the external services, so no amount of reading up on the cloud storage provider's documentation is going to answer those questions.
This would be based on the (false) assumption that during a backup Plesk manages the cloud storage security settings/parameters (ie. whether or not backups are stored privately or publicly and/or are encrypted at rest). Which isn't the case. Plesk only uploads (transports) the backups the cloud storage provider. Any security settings/parameters are managed with the cloud storage provider. Plesk has no influence on these settings (which would a security risk in itself).

And when you share information here in the forum as you did above that is not in the documentation, you learned it from some source that is not readily accessible to new users, hence my request that such information is added to the documentation where we expect to find it. [..]
That's false as well. I actually found the information in the DigitaloOcean Spaces documentation. Which is publicly available to anyone.
 
Thank you for confirming that you've completely misunderstood all that I've said, and that I am not in fact losing my mind. All the best!
 
Reviving this old thread since I am looking for the same thing. S3 storage offers this:


But it requires the S3 client (like Plesk backup) to maintain the encryption key and use it for any access. Is this implemented and if not, any ETA?
 
Currently, there are no plans for implementing the encryption method in question on Plesk's side. There's an existing feature request and you may vote for it here. However, taking into account the popularity of the request thus far, I doubt that it will be considered soon. The backup software is not designed to directly interact with S3 for storing backups, but only for sending them to S3.
 
Currently, there are no plans for implementing the encryption method in question on Plesk's side. There's an existing feature request and you may vote for it here. However, taking into account the popularity of the request thus far, I doubt that it will be considered soon. The backup software is not designed to directly interact with S3 for storing backups, but only for sending them to S3.
Thank you. That's disappointing because the work required on Plesk's side would be minimal, all the heavy lifting re. encryption/decryption would be done on the side of the S3 server. And the benefit would be great.
 
Back
Top