Struct aws_sdk_macie2::operation::get_sensitive_data_occurrences_availability::builders::GetSensitiveDataOccurrencesAvailabilityOutputBuilder
source · #[non_exhaustive]pub struct GetSensitiveDataOccurrencesAvailabilityOutputBuilder { /* private fields */ }
Expand description
A builder for GetSensitiveDataOccurrencesAvailabilityOutput
.
Implementations§
source§impl GetSensitiveDataOccurrencesAvailabilityOutputBuilder
impl GetSensitiveDataOccurrencesAvailabilityOutputBuilder
sourcepub fn code(self, input: AvailabilityCode) -> Self
pub fn code(self, input: AvailabilityCode) -> Self
Specifies whether occurrences of sensitive data can be retrieved for the finding. Possible values are: AVAILABLE, the sensitive data can be retrieved; and, UNAVAILABLE, the sensitive data can't be retrieved. If this value is UNAVAILABLE, the reasons array indicates why the data can't be retrieved.
sourcepub fn set_code(self, input: Option<AvailabilityCode>) -> Self
pub fn set_code(self, input: Option<AvailabilityCode>) -> Self
Specifies whether occurrences of sensitive data can be retrieved for the finding. Possible values are: AVAILABLE, the sensitive data can be retrieved; and, UNAVAILABLE, the sensitive data can't be retrieved. If this value is UNAVAILABLE, the reasons array indicates why the data can't be retrieved.
sourcepub fn get_code(&self) -> &Option<AvailabilityCode>
pub fn get_code(&self) -> &Option<AvailabilityCode>
Specifies whether occurrences of sensitive data can be retrieved for the finding. Possible values are: AVAILABLE, the sensitive data can be retrieved; and, UNAVAILABLE, the sensitive data can't be retrieved. If this value is UNAVAILABLE, the reasons array indicates why the data can't be retrieved.
sourcepub fn reasons(self, input: UnavailabilityReasonCode) -> Self
pub fn reasons(self, input: UnavailabilityReasonCode) -> Self
Appends an item to reasons
.
To override the contents of this collection use set_reasons
.
Specifies why occurrences of sensitive data can't be retrieved for the finding. Possible values are:
-
ACCOUNT_NOT_IN_ORGANIZATION - The affected account isn't currently part of your organization. Or the account is part of your organization but Macie isn't currently enabled for the account. You're not allowed to access the affected S3 object by using Macie.
-
INVALID_CLASSIFICATION_RESULT - There isn't a corresponding sensitive data discovery result for the finding. Or the corresponding sensitive data discovery result isn't available in the current Amazon Web Services Region, is malformed or corrupted, or uses an unsupported storage format. Macie can't verify the location of the sensitive data to retrieve.
-
INVALID_RESULT_SIGNATURE - The corresponding sensitive data discovery result is stored in an S3 object that wasn't signed by Macie. Macie can't verify the integrity and authenticity of the sensitive data discovery result. Therefore, Macie can't verify the location of the sensitive data to retrieve.
-
MEMBER_ROLE_TOO_PERMISSIVE - The trust or permissions policy for the IAM role in the affected member account doesn't meet Macie requirements for restricting access to the role. Or the role's trust policy doesn't specify the correct external ID for your organization. Macie can't assume the role to retrieve the sensitive data.
-
MISSING_GET_MEMBER_PERMISSION - You're not allowed to retrieve information about the association between your account and the affected account. Macie can't determine whether you’re allowed to access the affected S3 object as the delegated Macie administrator for the affected account.
-
OBJECT_EXCEEDS_SIZE_QUOTA - The storage size of the affected S3 object exceeds the size quota for retrieving occurrences of sensitive data from this type of file.
-
OBJECT_UNAVAILABLE - The affected S3 object isn't available. The object was renamed, moved, deleted, or changed after Macie created the finding. Or the object is encrypted with an KMS key that's currently disabled.
-
RESULT_NOT_SIGNED - The corresponding sensitive data discovery result is stored in an S3 object that hasn't been signed. Macie can't verify the integrity and authenticity of the sensitive data discovery result. Therefore, Macie can't verify the location of the sensitive data to retrieve.
-
ROLE_TOO_PERMISSIVE - Your account is configured to retrieve occurrences of sensitive data by using an IAM role whose trust or permissions policy doesn't meet Macie requirements for restricting access to the role. Macie can’t assume the role to retrieve the sensitive data.
-
UNSUPPORTED_FINDING_TYPE - The specified finding isn't a sensitive data finding.
-
UNSUPPORTED_OBJECT_TYPE - The affected S3 object uses a file or storage format that Macie doesn't support for retrieving occurrences of sensitive data.
This value is null if sensitive data can be retrieved for the finding.
sourcepub fn set_reasons(self, input: Option<Vec<UnavailabilityReasonCode>>) -> Self
pub fn set_reasons(self, input: Option<Vec<UnavailabilityReasonCode>>) -> Self
Specifies why occurrences of sensitive data can't be retrieved for the finding. Possible values are:
-
ACCOUNT_NOT_IN_ORGANIZATION - The affected account isn't currently part of your organization. Or the account is part of your organization but Macie isn't currently enabled for the account. You're not allowed to access the affected S3 object by using Macie.
-
INVALID_CLASSIFICATION_RESULT - There isn't a corresponding sensitive data discovery result for the finding. Or the corresponding sensitive data discovery result isn't available in the current Amazon Web Services Region, is malformed or corrupted, or uses an unsupported storage format. Macie can't verify the location of the sensitive data to retrieve.
-
INVALID_RESULT_SIGNATURE - The corresponding sensitive data discovery result is stored in an S3 object that wasn't signed by Macie. Macie can't verify the integrity and authenticity of the sensitive data discovery result. Therefore, Macie can't verify the location of the sensitive data to retrieve.
-
MEMBER_ROLE_TOO_PERMISSIVE - The trust or permissions policy for the IAM role in the affected member account doesn't meet Macie requirements for restricting access to the role. Or the role's trust policy doesn't specify the correct external ID for your organization. Macie can't assume the role to retrieve the sensitive data.
-
MISSING_GET_MEMBER_PERMISSION - You're not allowed to retrieve information about the association between your account and the affected account. Macie can't determine whether you’re allowed to access the affected S3 object as the delegated Macie administrator for the affected account.
-
OBJECT_EXCEEDS_SIZE_QUOTA - The storage size of the affected S3 object exceeds the size quota for retrieving occurrences of sensitive data from this type of file.
-
OBJECT_UNAVAILABLE - The affected S3 object isn't available. The object was renamed, moved, deleted, or changed after Macie created the finding. Or the object is encrypted with an KMS key that's currently disabled.
-
RESULT_NOT_SIGNED - The corresponding sensitive data discovery result is stored in an S3 object that hasn't been signed. Macie can't verify the integrity and authenticity of the sensitive data discovery result. Therefore, Macie can't verify the location of the sensitive data to retrieve.
-
ROLE_TOO_PERMISSIVE - Your account is configured to retrieve occurrences of sensitive data by using an IAM role whose trust or permissions policy doesn't meet Macie requirements for restricting access to the role. Macie can’t assume the role to retrieve the sensitive data.
-
UNSUPPORTED_FINDING_TYPE - The specified finding isn't a sensitive data finding.
-
UNSUPPORTED_OBJECT_TYPE - The affected S3 object uses a file or storage format that Macie doesn't support for retrieving occurrences of sensitive data.
This value is null if sensitive data can be retrieved for the finding.
sourcepub fn get_reasons(&self) -> &Option<Vec<UnavailabilityReasonCode>>
pub fn get_reasons(&self) -> &Option<Vec<UnavailabilityReasonCode>>
Specifies why occurrences of sensitive data can't be retrieved for the finding. Possible values are:
-
ACCOUNT_NOT_IN_ORGANIZATION - The affected account isn't currently part of your organization. Or the account is part of your organization but Macie isn't currently enabled for the account. You're not allowed to access the affected S3 object by using Macie.
-
INVALID_CLASSIFICATION_RESULT - There isn't a corresponding sensitive data discovery result for the finding. Or the corresponding sensitive data discovery result isn't available in the current Amazon Web Services Region, is malformed or corrupted, or uses an unsupported storage format. Macie can't verify the location of the sensitive data to retrieve.
-
INVALID_RESULT_SIGNATURE - The corresponding sensitive data discovery result is stored in an S3 object that wasn't signed by Macie. Macie can't verify the integrity and authenticity of the sensitive data discovery result. Therefore, Macie can't verify the location of the sensitive data to retrieve.
-
MEMBER_ROLE_TOO_PERMISSIVE - The trust or permissions policy for the IAM role in the affected member account doesn't meet Macie requirements for restricting access to the role. Or the role's trust policy doesn't specify the correct external ID for your organization. Macie can't assume the role to retrieve the sensitive data.
-
MISSING_GET_MEMBER_PERMISSION - You're not allowed to retrieve information about the association between your account and the affected account. Macie can't determine whether you’re allowed to access the affected S3 object as the delegated Macie administrator for the affected account.
-
OBJECT_EXCEEDS_SIZE_QUOTA - The storage size of the affected S3 object exceeds the size quota for retrieving occurrences of sensitive data from this type of file.
-
OBJECT_UNAVAILABLE - The affected S3 object isn't available. The object was renamed, moved, deleted, or changed after Macie created the finding. Or the object is encrypted with an KMS key that's currently disabled.
-
RESULT_NOT_SIGNED - The corresponding sensitive data discovery result is stored in an S3 object that hasn't been signed. Macie can't verify the integrity and authenticity of the sensitive data discovery result. Therefore, Macie can't verify the location of the sensitive data to retrieve.
-
ROLE_TOO_PERMISSIVE - Your account is configured to retrieve occurrences of sensitive data by using an IAM role whose trust or permissions policy doesn't meet Macie requirements for restricting access to the role. Macie can’t assume the role to retrieve the sensitive data.
-
UNSUPPORTED_FINDING_TYPE - The specified finding isn't a sensitive data finding.
-
UNSUPPORTED_OBJECT_TYPE - The affected S3 object uses a file or storage format that Macie doesn't support for retrieving occurrences of sensitive data.
This value is null if sensitive data can be retrieved for the finding.
sourcepub fn build(self) -> GetSensitiveDataOccurrencesAvailabilityOutput
pub fn build(self) -> GetSensitiveDataOccurrencesAvailabilityOutput
Consumes the builder and constructs a GetSensitiveDataOccurrencesAvailabilityOutput
.
Trait Implementations§
source§impl Clone for GetSensitiveDataOccurrencesAvailabilityOutputBuilder
impl Clone for GetSensitiveDataOccurrencesAvailabilityOutputBuilder
source§fn clone(&self) -> GetSensitiveDataOccurrencesAvailabilityOutputBuilder
fn clone(&self) -> GetSensitiveDataOccurrencesAvailabilityOutputBuilder
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moresource§impl Default for GetSensitiveDataOccurrencesAvailabilityOutputBuilder
impl Default for GetSensitiveDataOccurrencesAvailabilityOutputBuilder
source§fn default() -> GetSensitiveDataOccurrencesAvailabilityOutputBuilder
fn default() -> GetSensitiveDataOccurrencesAvailabilityOutputBuilder
source§impl PartialEq for GetSensitiveDataOccurrencesAvailabilityOutputBuilder
impl PartialEq for GetSensitiveDataOccurrencesAvailabilityOutputBuilder
source§fn eq(
&self,
other: &GetSensitiveDataOccurrencesAvailabilityOutputBuilder
) -> bool
fn eq( &self, other: &GetSensitiveDataOccurrencesAvailabilityOutputBuilder ) -> bool
self
and other
values to be equal, and is used
by ==
.