pub struct UpdateEventDataStoreFluentBuilder { /* private fields */ }
Expand description
Fluent builder constructing a request to UpdateEventDataStore
.
Updates an event data store. The required EventDataStore
value is an ARN or the ID portion of the ARN. Other parameters are optional, but at least one optional parameter must be specified, or CloudTrail throws an error. RetentionPeriod
is in days, and valid values are integers between 7 and 3653 if the BillingMode
is set to EXTENDABLE_RETENTION_PRICING
, or between 7 and 2557 if BillingMode
is set to FIXED_RETENTION_PRICING
. By default, TerminationProtection
is enabled.
For event data stores for CloudTrail events, AdvancedEventSelectors
includes or excludes management, data, or network activity events in your event data store. For more information about AdvancedEventSelectors
, see AdvancedEventSelectors.
For event data stores for CloudTrail Insights events, Config configuration items, Audit Manager evidence, or non-Amazon Web Services events, AdvancedEventSelectors
includes events of that type in your event data store.
Implementations§
Source§impl UpdateEventDataStoreFluentBuilder
impl UpdateEventDataStoreFluentBuilder
Sourcepub fn as_input(&self) -> &UpdateEventDataStoreInputBuilder
pub fn as_input(&self) -> &UpdateEventDataStoreInputBuilder
Access the UpdateEventDataStore as a reference.
Sourcepub async fn send(
self,
) -> Result<UpdateEventDataStoreOutput, SdkError<UpdateEventDataStoreError, HttpResponse>>
pub async fn send( self, ) -> Result<UpdateEventDataStoreOutput, SdkError<UpdateEventDataStoreError, HttpResponse>>
Sends the request and returns the response.
If an error occurs, an SdkError
will be returned with additional details that
can be matched against.
By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.
Sourcepub fn customize(
self,
) -> CustomizableOperation<UpdateEventDataStoreOutput, UpdateEventDataStoreError, Self>
pub fn customize( self, ) -> CustomizableOperation<UpdateEventDataStoreOutput, UpdateEventDataStoreError, Self>
Consumes this builder, creating a customizable operation that can be modified before being sent.
Sourcepub fn event_data_store(self, input: impl Into<String>) -> Self
pub fn event_data_store(self, input: impl Into<String>) -> Self
The ARN (or the ID suffix of the ARN) of the event data store that you want to update.
Sourcepub fn set_event_data_store(self, input: Option<String>) -> Self
pub fn set_event_data_store(self, input: Option<String>) -> Self
The ARN (or the ID suffix of the ARN) of the event data store that you want to update.
Sourcepub fn get_event_data_store(&self) -> &Option<String>
pub fn get_event_data_store(&self) -> &Option<String>
The ARN (or the ID suffix of the ARN) of the event data store that you want to update.
Sourcepub fn advanced_event_selectors(self, input: AdvancedEventSelector) -> Self
pub fn advanced_event_selectors(self, input: AdvancedEventSelector) -> Self
Appends an item to AdvancedEventSelectors
.
To override the contents of this collection use set_advanced_event_selectors
.
The advanced event selectors used to select events for the event data store. You can configure up to five advanced event selectors for each event data store.
Sourcepub fn set_advanced_event_selectors(
self,
input: Option<Vec<AdvancedEventSelector>>,
) -> Self
pub fn set_advanced_event_selectors( self, input: Option<Vec<AdvancedEventSelector>>, ) -> Self
The advanced event selectors used to select events for the event data store. You can configure up to five advanced event selectors for each event data store.
Sourcepub fn get_advanced_event_selectors(
&self,
) -> &Option<Vec<AdvancedEventSelector>>
pub fn get_advanced_event_selectors( &self, ) -> &Option<Vec<AdvancedEventSelector>>
The advanced event selectors used to select events for the event data store. You can configure up to five advanced event selectors for each event data store.
Sourcepub fn multi_region_enabled(self, input: bool) -> Self
pub fn multi_region_enabled(self, input: bool) -> Self
Specifies whether an event data store collects events from all Regions, or only from the Region in which it was created.
Sourcepub fn set_multi_region_enabled(self, input: Option<bool>) -> Self
pub fn set_multi_region_enabled(self, input: Option<bool>) -> Self
Specifies whether an event data store collects events from all Regions, or only from the Region in which it was created.
Sourcepub fn get_multi_region_enabled(&self) -> &Option<bool>
pub fn get_multi_region_enabled(&self) -> &Option<bool>
Specifies whether an event data store collects events from all Regions, or only from the Region in which it was created.
Sourcepub fn organization_enabled(self, input: bool) -> Self
pub fn organization_enabled(self, input: bool) -> Self
Specifies whether an event data store collects events logged for an organization in Organizations.
Only the management account for the organization can convert an organization event data store to a non-organization event data store, or convert a non-organization event data store to an organization event data store.
Sourcepub fn set_organization_enabled(self, input: Option<bool>) -> Self
pub fn set_organization_enabled(self, input: Option<bool>) -> Self
Specifies whether an event data store collects events logged for an organization in Organizations.
Only the management account for the organization can convert an organization event data store to a non-organization event data store, or convert a non-organization event data store to an organization event data store.
Sourcepub fn get_organization_enabled(&self) -> &Option<bool>
pub fn get_organization_enabled(&self) -> &Option<bool>
Specifies whether an event data store collects events logged for an organization in Organizations.
Only the management account for the organization can convert an organization event data store to a non-organization event data store, or convert a non-organization event data store to an organization event data store.
Sourcepub fn retention_period(self, input: i32) -> Self
pub fn retention_period(self, input: i32) -> Self
The retention period of the event data store, in days. If BillingMode
is set to EXTENDABLE_RETENTION_PRICING
, you can set a retention period of up to 3653 days, the equivalent of 10 years. If BillingMode
is set to FIXED_RETENTION_PRICING
, you can set a retention period of up to 2557 days, the equivalent of seven years.
CloudTrail Lake determines whether to retain an event by checking if the eventTime
of the event is within the specified retention period. For example, if you set a retention period of 90 days, CloudTrail will remove events when the eventTime
is older than 90 days.
If you decrease the retention period of an event data store, CloudTrail will remove any events with an eventTime
older than the new retention period. For example, if the previous retention period was 365 days and you decrease it to 100 days, CloudTrail will remove events with an eventTime
older than 100 days.
Sourcepub fn set_retention_period(self, input: Option<i32>) -> Self
pub fn set_retention_period(self, input: Option<i32>) -> Self
The retention period of the event data store, in days. If BillingMode
is set to EXTENDABLE_RETENTION_PRICING
, you can set a retention period of up to 3653 days, the equivalent of 10 years. If BillingMode
is set to FIXED_RETENTION_PRICING
, you can set a retention period of up to 2557 days, the equivalent of seven years.
CloudTrail Lake determines whether to retain an event by checking if the eventTime
of the event is within the specified retention period. For example, if you set a retention period of 90 days, CloudTrail will remove events when the eventTime
is older than 90 days.
If you decrease the retention period of an event data store, CloudTrail will remove any events with an eventTime
older than the new retention period. For example, if the previous retention period was 365 days and you decrease it to 100 days, CloudTrail will remove events with an eventTime
older than 100 days.
Sourcepub fn get_retention_period(&self) -> &Option<i32>
pub fn get_retention_period(&self) -> &Option<i32>
The retention period of the event data store, in days. If BillingMode
is set to EXTENDABLE_RETENTION_PRICING
, you can set a retention period of up to 3653 days, the equivalent of 10 years. If BillingMode
is set to FIXED_RETENTION_PRICING
, you can set a retention period of up to 2557 days, the equivalent of seven years.
CloudTrail Lake determines whether to retain an event by checking if the eventTime
of the event is within the specified retention period. For example, if you set a retention period of 90 days, CloudTrail will remove events when the eventTime
is older than 90 days.
If you decrease the retention period of an event data store, CloudTrail will remove any events with an eventTime
older than the new retention period. For example, if the previous retention period was 365 days and you decrease it to 100 days, CloudTrail will remove events with an eventTime
older than 100 days.
Sourcepub fn termination_protection_enabled(self, input: bool) -> Self
pub fn termination_protection_enabled(self, input: bool) -> Self
Indicates that termination protection is enabled and the event data store cannot be automatically deleted.
Sourcepub fn set_termination_protection_enabled(self, input: Option<bool>) -> Self
pub fn set_termination_protection_enabled(self, input: Option<bool>) -> Self
Indicates that termination protection is enabled and the event data store cannot be automatically deleted.
Sourcepub fn get_termination_protection_enabled(&self) -> &Option<bool>
pub fn get_termination_protection_enabled(&self) -> &Option<bool>
Indicates that termination protection is enabled and the event data store cannot be automatically deleted.
Sourcepub fn kms_key_id(self, input: impl Into<String>) -> Self
pub fn kms_key_id(self, input: impl Into<String>) -> Self
Specifies the KMS key ID to use to encrypt the events delivered by CloudTrail. The value can be an alias name prefixed by alias/
, a fully specified ARN to an alias, a fully specified ARN to a key, or a globally unique identifier.
Disabling or deleting the KMS key, or removing CloudTrail permissions on the key, prevents CloudTrail from logging events to the event data store, and prevents users from querying the data in the event data store that was encrypted with the key. After you associate an event data store with a KMS key, the KMS key cannot be removed or changed. Before you disable or delete a KMS key that you are using with an event data store, delete or back up your event data store.
CloudTrail also supports KMS multi-Region keys. For more information about multi-Region keys, see Using multi-Region keys in the Key Management Service Developer Guide.
Examples:
-
alias/MyAliasName
-
arn:aws:kms:us-east-2:123456789012:alias/MyAliasName
-
arn:aws:kms:us-east-2:123456789012:key/12345678-1234-1234-1234-123456789012
-
12345678-1234-1234-1234-123456789012
Sourcepub fn set_kms_key_id(self, input: Option<String>) -> Self
pub fn set_kms_key_id(self, input: Option<String>) -> Self
Specifies the KMS key ID to use to encrypt the events delivered by CloudTrail. The value can be an alias name prefixed by alias/
, a fully specified ARN to an alias, a fully specified ARN to a key, or a globally unique identifier.
Disabling or deleting the KMS key, or removing CloudTrail permissions on the key, prevents CloudTrail from logging events to the event data store, and prevents users from querying the data in the event data store that was encrypted with the key. After you associate an event data store with a KMS key, the KMS key cannot be removed or changed. Before you disable or delete a KMS key that you are using with an event data store, delete or back up your event data store.
CloudTrail also supports KMS multi-Region keys. For more information about multi-Region keys, see Using multi-Region keys in the Key Management Service Developer Guide.
Examples:
-
alias/MyAliasName
-
arn:aws:kms:us-east-2:123456789012:alias/MyAliasName
-
arn:aws:kms:us-east-2:123456789012:key/12345678-1234-1234-1234-123456789012
-
12345678-1234-1234-1234-123456789012
Sourcepub fn get_kms_key_id(&self) -> &Option<String>
pub fn get_kms_key_id(&self) -> &Option<String>
Specifies the KMS key ID to use to encrypt the events delivered by CloudTrail. The value can be an alias name prefixed by alias/
, a fully specified ARN to an alias, a fully specified ARN to a key, or a globally unique identifier.
Disabling or deleting the KMS key, or removing CloudTrail permissions on the key, prevents CloudTrail from logging events to the event data store, and prevents users from querying the data in the event data store that was encrypted with the key. After you associate an event data store with a KMS key, the KMS key cannot be removed or changed. Before you disable or delete a KMS key that you are using with an event data store, delete or back up your event data store.
CloudTrail also supports KMS multi-Region keys. For more information about multi-Region keys, see Using multi-Region keys in the Key Management Service Developer Guide.
Examples:
-
alias/MyAliasName
-
arn:aws:kms:us-east-2:123456789012:alias/MyAliasName
-
arn:aws:kms:us-east-2:123456789012:key/12345678-1234-1234-1234-123456789012
-
12345678-1234-1234-1234-123456789012
Sourcepub fn billing_mode(self, input: BillingMode) -> Self
pub fn billing_mode(self, input: BillingMode) -> Self
You can't change the billing mode from EXTENDABLE_RETENTION_PRICING
to FIXED_RETENTION_PRICING
. If BillingMode
is set to EXTENDABLE_RETENTION_PRICING
and you want to use FIXED_RETENTION_PRICING
instead, you'll need to stop ingestion on the event data store and create a new event data store that uses FIXED_RETENTION_PRICING
.
The billing mode for the event data store determines the cost for ingesting events and the default and maximum retention period for the event data store.
The following are the possible values:
-
EXTENDABLE_RETENTION_PRICING
- This billing mode is generally recommended if you want a flexible retention period of up to 3653 days (about 10 years). The default retention period for this billing mode is 366 days. -
FIXED_RETENTION_PRICING
- This billing mode is recommended if you expect to ingest more than 25 TB of event data per month and need a retention period of up to 2557 days (about 7 years). The default retention period for this billing mode is 2557 days.
For more information about CloudTrail pricing, see CloudTrail Pricing and Managing CloudTrail Lake costs.
Sourcepub fn set_billing_mode(self, input: Option<BillingMode>) -> Self
pub fn set_billing_mode(self, input: Option<BillingMode>) -> Self
You can't change the billing mode from EXTENDABLE_RETENTION_PRICING
to FIXED_RETENTION_PRICING
. If BillingMode
is set to EXTENDABLE_RETENTION_PRICING
and you want to use FIXED_RETENTION_PRICING
instead, you'll need to stop ingestion on the event data store and create a new event data store that uses FIXED_RETENTION_PRICING
.
The billing mode for the event data store determines the cost for ingesting events and the default and maximum retention period for the event data store.
The following are the possible values:
-
EXTENDABLE_RETENTION_PRICING
- This billing mode is generally recommended if you want a flexible retention period of up to 3653 days (about 10 years). The default retention period for this billing mode is 366 days. -
FIXED_RETENTION_PRICING
- This billing mode is recommended if you expect to ingest more than 25 TB of event data per month and need a retention period of up to 2557 days (about 7 years). The default retention period for this billing mode is 2557 days.
For more information about CloudTrail pricing, see CloudTrail Pricing and Managing CloudTrail Lake costs.
Sourcepub fn get_billing_mode(&self) -> &Option<BillingMode>
pub fn get_billing_mode(&self) -> &Option<BillingMode>
You can't change the billing mode from EXTENDABLE_RETENTION_PRICING
to FIXED_RETENTION_PRICING
. If BillingMode
is set to EXTENDABLE_RETENTION_PRICING
and you want to use FIXED_RETENTION_PRICING
instead, you'll need to stop ingestion on the event data store and create a new event data store that uses FIXED_RETENTION_PRICING
.
The billing mode for the event data store determines the cost for ingesting events and the default and maximum retention period for the event data store.
The following are the possible values:
-
EXTENDABLE_RETENTION_PRICING
- This billing mode is generally recommended if you want a flexible retention period of up to 3653 days (about 10 years). The default retention period for this billing mode is 366 days. -
FIXED_RETENTION_PRICING
- This billing mode is recommended if you expect to ingest more than 25 TB of event data per month and need a retention period of up to 2557 days (about 7 years). The default retention period for this billing mode is 2557 days.
For more information about CloudTrail pricing, see CloudTrail Pricing and Managing CloudTrail Lake costs.
Trait Implementations§
Source§impl Clone for UpdateEventDataStoreFluentBuilder
impl Clone for UpdateEventDataStoreFluentBuilder
Source§fn clone(&self) -> UpdateEventDataStoreFluentBuilder
fn clone(&self) -> UpdateEventDataStoreFluentBuilder
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read moreAuto Trait Implementations§
impl Freeze for UpdateEventDataStoreFluentBuilder
impl !RefUnwindSafe for UpdateEventDataStoreFluentBuilder
impl Send for UpdateEventDataStoreFluentBuilder
impl Sync for UpdateEventDataStoreFluentBuilder
impl Unpin for UpdateEventDataStoreFluentBuilder
impl !UnwindSafe for UpdateEventDataStoreFluentBuilder
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);