feat(objectstore): Add AWS SSE-KMS encryption support for S3 storage

[cuppett]

Summary

Add support for Server-Side Encryption with AWS Key Management Service (SSE-KMS) for S3 object storage. This allows Nextcloud to encrypt data at rest in S3 using AWS-managed keys.

Key Features

• New configuration options: sse_kms_enabled and sse_kms_key_id
• Full SSE-KMS support: Both single-part and multipart uploads
• Backward compatible: Existing SSE-C (customer-provided keys) continues to work
• Priority handling: SSE-C takes precedence when both SSE-C and SSE-KMS are configured

Implementation Details

• Added getServerSideEncryptionParameters() method to centralize encryption parameter logic for both SSE-C and SSE-KMS
• Updated multipart uploads to use unified encryption parameters (fixes potential SSE-KMS multipart upload issues)
• Added comprehensive PHPUnit test suite (S3SSEKMSTest.php) for SSE-KMS scenarios
• Validated with real AWS KMS keys and S3 buckets

Configuration Example

'objectstore' => [
  'class' => 'OC\\Files\\ObjectStore\\S3',
  'arguments' => [
    'bucket' => 'my-bucket',
    'region' => 'us-east-1',
    'key' => 'ACCESS_KEY',
    'secret' => 'SECRET_KEY',
    // SSE-KMS Configuration
    'sse_kms_enabled' => true,
    'sse_kms_key_id' => 'arn:aws:kms:us-east-1:ACCOUNT:key/KEY-ID',
  ]
]

Testing

Manual Testing

Validated both SSE-KMS and SSE-C encryption with comprehensive file upload/download tests:

SSE-KMS Testing:

• ✅ Small files (1KB, 1MB, 10MB) - single-part uploads
• ✅ Large files (100MB, 500MB, 1GB) - multipart uploads
• ✅ Verified `x-amz-server-side-encryption: aws:kms` headers on S3 objects
• ✅ Verified `x-amz-server-side-encryption-aws-kms-key-id` contains correct KMS key ARN
• ✅ All file integrity checks passed (md5sum matches)

SSE-C Backward Compatibility Testing:

• ✅ Confirmed SSE-C still works after changes
• ✅ Verified `SSECustomerAlgorithm: AES256` headers on SSE-C objects
• ✅ Both single-part and multipart uploads work correctly
• ✅ All file operations validated with checksum verification

PHPUnit Tests

• ✅ All 16 existing S3 tests pass with SSE-C configuration
• ✅ New `S3SSEKMSTest` class added with comprehensive SSE-KMS test coverage
• ✅ Tests validate encryption parameter handling for both SSE-C and SSE-KMS

Files Changed

• `lib/private/Files/ObjectStore/S3.php` - Added SSE-KMS configuration options
• `lib/private/Files/ObjectStore/S3ConnectionTrait.php` - Implemented `getServerSideEncryptionParameters()`
• `lib/private/Files/ObjectStore/S3ObjectTrait.php` - Updated multipart uploads to use unified encryption parameters
• `apps/files_external/lib/Lib/Storage/AmazonS3.php` - Extended SSE-KMS support to external storage
• `tests/lib/Files/ObjectStore/S3SSEKMSTest.php` - New comprehensive test suite

🤖 Generated with Claude Code

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

[cuppett]

@icewind1991 Can this be reviewed or merged? This allows Nextcloud to drive which KMS key is used for server-side encryption (within S3). An AWS S3 bucket can be configured with a default key and mandatory encryption; however, this allows multiple nextcloud instances/tenants (potentially under different IAM user/roles) to share the same bucket with different prefixes and logical isolation with permission to different keys.

[cuppett]

Also note, while preserved functionality here, AWS will remove SSE-C on April 6, 2026. We can do a separate PR to remove this (in some version) and then the existing logic can be refactored out:

https://aws.amazon.com/blogs/storage/advanced-notice-amazon-s3-to-disable-the-use-of-sse-c-encryption-by-default-for-all-new-buckets-and-select-existing-buckets-in-april-2026/