Struct ServerSideEncryptionRule 

pub struct ServerSideEncryptionRule {
    pub apply_server_side_encryption_by_default: Option<ServerSideEncryptionByDefault>,
    pub bucket_key_enabled: Option<BucketKeyEnabled>,
}

Specifies the default server-side encryption configuration.

• General purpose buckets - If you're specifying a customer managed KMS key, we recommend using a fully qualified KMS key ARN. If you use a KMS key alias instead, then KMS resolves the key within the requester’s account. This behavior can result in data that's encrypted with a KMS key that belongs to the requester, and not the bucket owner.

• Directory buckets - When you specify an KMS customer managed key for encryption in your directory bucket, only use the key ID or key ARN. The key alias format of the KMS key isn't supported.

Fields

apply_server_side_encryption_by_default: Option<ServerSideEncryptionByDefault>

Specifies the default server-side encryption to apply to new objects in the bucket. If a PUT Object request doesn't specify any server-side encryption, this default encryption will be applied.

bucket_key_enabled: Option<BucketKeyEnabled>

Specifies whether Amazon S3 should use an S3 Bucket Key with server-side encryption using KMS (SSE-KMS) for new objects in the bucket. Existing objects are not affected. Setting the BucketKeyEnabled element to true causes Amazon S3 to use an S3 Bucket Key.

• General purpose buckets - By default, S3 Bucket Key is not enabled. For more information, see Amazon S3 Bucket Keys in the Amazon S3 User Guide.

• Directory buckets - S3 Bucket Keys are always enabled for GET and PUT operations in a directory bucket and can’t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets to directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through CopyObject, UploadPartCopy, the Copy operation in Batch Operations, or the import jobs. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.

Trait Implementations

impl Clone for ServerSideEncryptionRule

fn clone(&self) -> ServerSideEncryptionRule

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ServerSideEncryptionRule

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for ServerSideEncryptionRule

fn default() -> ServerSideEncryptionRule

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for ServerSideEncryptionRule

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl<'xml> DeserializeContent<'xml> for ServerSideEncryptionRule

Available on crate feature minio only.

fn deserialize_content(d: &mut Deserializer<'xml>) -> DeResult<Self>

Deserializes the content of the data type

impl DtoExt for ServerSideEncryptionRule

fn ignore_empty_strings(&mut self)

Modifies all empty string fields from Some("") to None

impl PartialEq for ServerSideEncryptionRule

fn eq(&self, other: &ServerSideEncryptionRule) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for ServerSideEncryptionRule

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl SerializeContent for ServerSideEncryptionRule

Available on crate feature minio only.

fn serialize_content<W: Write>(&self, s: &mut Serializer<W>) -> SerResult

Serializes the content of the data type

impl StructuralPartialEq for ServerSideEncryptionRule