Skip to main content
NetApp Knowledge Base

Unable to Use AWS KMS (SSE-KMS) Encryption for On-Prem ONTAP Backups to S3

  1. Last updated
  2. Save as PDF
Views:
34
Visibility:
Public
Votes:
0
Category:
netapp_console
Specialty:
ds_cbs
Last Updated:

Applies to

  • NetApp Backup & Recovery
  • On-premises ONTAP backup to AWS S3
  • Amazon Web Services (AWS)
  • KMS

Issue

  • When configuringBackup & Recovery for on-premises ONTAP to back up data to AWS S3, attempts to use customer-managed AWS KMS keys (SSE-KMS) for server-side encryption fail.
  • Even when the S3 bucket is created with KMS encryption, the backup objects are stored using the default SSE-S3 encryption instead of SSE-KMS. The Backup Dashboard UI does not allow changing the encryption type for existing buckets, and the destination bucket option is grayed out during backup configuration.
  • Objects in the S3 bucket are encrypted with SSE-S3, not SSE-KMS, even though bucket policy and creation used KMS keys.
  • Attempting to block SSE-S3 uploads with an explicet IAM policy causes backup jobs to fail.
  • User cannot select KMS encryption in the NetApp Console UI for existing buckets.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.