Struct aws_sdk_forecast::input::CreateExplainabilityInput

source · [−]

#[non_exhaustive]
pub struct CreateExplainabilityInput { /* private fields */ }

Implementations

source

impl CreateExplainabilityInput

source

pub async fn make_operation(
&self,
_config: &Config
) -> Result<Operation<CreateExplainability, AwsResponseRetryClassifier>, BuildError>

Consumes the builder and constructs an Operation<CreateExplainability>

source

pub fn builder() -> Builder

Creates a new builder-style object to manufacture CreateExplainabilityInput.

source

impl CreateExplainabilityInput

source

pub fn explainability_name(&self) -> Option<&str>

A unique name for the Explainability.

source

pub fn resource_arn(&self) -> Option<&str>

The Amazon Resource Name (ARN) of the Predictor or Forecast used to create the Explainability.

source

pub fn explainability_config(&self) -> Option<&ExplainabilityConfig>

The configuration settings that define the granularity of time series and time points for the Explainability.

source

pub fn data_source(&self) -> Option<&DataSource>

The source of your data, an AWS Identity and Access Management (IAM) role that allows Amazon Forecast to access the data and, optionally, an AWS Key Management Service (KMS) key.

source

pub fn schema(&self) -> Option<&Schema>

Defines the fields of a dataset.

source

pub fn enable_visualization(&self) -> Option<bool>

Create an Explainability visualization that is viewable within the AWS console.

source

pub fn start_date_time(&self) -> Option<&str>

If TimePointGranularity is set to SPECIFIC, define the first point for the Explainability.

Use the following timestamp format: yyyy-MM-ddTHH:mm:ss (example: 2015-01-01T20:00:00)

source

pub fn end_date_time(&self) -> Option<&str>

If TimePointGranularity is set to SPECIFIC, define the last time point for the Explainability.

Use the following timestamp format: yyyy-MM-ddTHH:mm:ss (example: 2015-01-01T20:00:00)

source

pub fn tags(&self) -> Option<&[Tag]>

Optional metadata to help you categorize and organize your resources. Each tag consists of a key and an optional value, both of which you define. Tag keys and values are case sensitive.

The following restrictions apply to tags:

For each resource, each tag key must be unique and each tag key must have one value.
Maximum number of tags per resource: 50.
Maximum key length: 128 Unicode characters in UTF-8.
Maximum value length: 256 Unicode characters in UTF-8.
Accepted characters: all letters and numbers, spaces representable in UTF-8, and + - = . _ : / @. If your tagging schema is used across other services and resources, the character restrictions of those services also apply.
Key prefixes cannot include any upper or lowercase combination of aws: or AWS:. Values can have this prefix. If a tag value has aws as its prefix but the key does not, Forecast considers it to be a user tag and will count against the limit of 50 tags. Tags with only the key prefix of aws do not count against your tags per resource limit. You cannot edit or delete tag keys with this prefix.