Module aws_sdk_elasticsearch::types
source · Expand description
Data structures used by operation inputs/outputs.
Modules§
- Builders
- Error types that Amazon Elasticsearch Service can respond with.
Structs§
The configured access rules for the domain's document and search endpoints, and the current status of those rules.
List of limits that are specific to a given InstanceType and for each of it's
InstanceRole
Status of the advanced options for the specified Elasticsearch domain. Currently, the following advanced options are available:
Specifies the advanced security configuration: whether advanced security is enabled, whether the internal database option is enabled.
Specifies the advanced security configuration: whether advanced security is enabled, whether the internal database option is enabled, master username and password (if internal database is enabled), and master user ARN (if IAM is enabled).
Specifies the status of advanced security options for the specified Elasticsearch domain.
Information about an account or service that has access to an Amazon OpenSearch Service domain through the use of an interface VPC endpoint.
Specifies Auto-Tune type and Auto-Tune action details.
Specifies details of the Auto-Tune action. See the Developer Guide for more information.
Specifies Auto-Tune maitenance schedule. See the Developer Guide for more information.
Specifies the Auto-Tune options: the Auto-Tune desired state for the domain, rollback state when disabling Auto-Tune options and list of maintenance schedules.
Specifies the Auto-Tune options: the Auto-Tune desired state for the domain and list of maintenance schedules.
Specifies the Auto-Tune options: the Auto-Tune desired state for the domain and list of maintenance schedules.
Specifies the status of Auto-Tune options for the specified Elasticsearch domain.
Provides the current status of the Auto-Tune options.
A property change that was cancelled for an Amazon OpenSearch Service domain.
Specifies change details of the domain configuration change.
A progress stage details of a specific domain configuration change.
The progress details of a specific domain configuration change.
Options to specify the Cognito user and identity pools for Kibana authentication. For more information, see Amazon Cognito Authentication for Kibana.
Status of the Cognito options for the specified Elasticsearch domain.
Specifies the configuration for cold storage options such as enabled
A map from an
ElasticsearchVersion
ElasticsearchVersion
Filter to apply in
DescribePackage
response.Options to configure endpoint for the Elasticsearch domain.
The configured endpoint options for the domain and their current status.
Information on a package that is associated with a domain.
Specifies maintenance schedule duration: duration value and duration unit. See the Developer Guide for more information.
Options to enable, disable, and specify the properties of EBS storage volumes. For more information, see Configuring EBS-based Storage.
Status of the EBS options for the specified Elasticsearch domain.
Specifies the configuration for the domain cluster, such as the type and number of instances.
Specifies the configuration status for the specified Elasticsearch domain.
The configuration of an Elasticsearch domain.
The current status of an Elasticsearch domain.
Status of the Elasticsearch version options for the specified Elasticsearch domain.
Specifies the Encryption At Rest Options.
Status of the Encryption At Rest options for the specified Elasticsearch domain.
A filter used to limit results when describing inbound or outbound cross-cluster search connections. Multiple values can be specified per filter. A cross-cluster search connection must match at least one of the specified values for it to be returned from an operation.
Specifies details of an inbound connection.
Specifies the coonection status of an inbound cross-cluster search connection.
InstanceCountLimits represents the limits on number of instances that be created in Amazon Elasticsearch for given InstanceType.
InstanceLimits represents the list of instance related attributes that are available for given InstanceType.
Limits for given InstanceType and for each of it's role.
Log Publishing option that is set for given domain.
The configured log publishing options for the domain and their current status.
Credentials for the master user: username and password, ARN, or both.
Information about the domain properties that are currently being modified.
Specifies the node-to-node encryption options.
Status of the node-to-node encryption options for the specified Elasticsearch domain.
Provides the current status of the entity.
Specifies details of an outbound connection.
Specifies the connection status of an outbound cross-cluster search connection.
Basic information about a package.
The S3 location for importing the package specified as
S3BucketName
andS3Key
Details of a package version.
Contains the specific price and frequency of a recurring charges for a reserved Elasticsearch instance, or for a reserved Elasticsearch instance offering.
Details of a reserved Elasticsearch instance.
Details of a reserved Elasticsearch instance offering.
Specifies the SAML Identity Provider's information.
Specifies the SAML application configuration for the domain.
Describes the SAML application configured for the domain.
Specifies details of the scheduled Auto-Tune action. See the Developer Guide for more information.
The current options of an Elasticsearch domain service software options.
Specifies the time, in UTC format, when the service takes a daily automated snapshot of the specified Elasticsearch domain. Default value is
0
hours.Status of a daily automated snapshot.
StorageTypes represents the list of storage related types and their attributes that are available for given InstanceType.
Limits that are applicable for given storage type.
Specifies a key value pair for a resource tag.
History of the last 10 Upgrades and Upgrade Eligibility Checks.
Represents a single step of the Upgrade or Upgrade Eligibility Check workflow.
Options to specify the subnets and security groups for VPC endpoint. For more information, see VPC Endpoints for Amazon Elasticsearch Service Domains.
Status of the VPC options for the specified Elasticsearch domain.
The connection endpoint for connecting to an Amazon OpenSearch Service domain through a proxy.
Error information when attempting to describe an Amazon OpenSearch Service-managed VPC endpoint.
Summary information for an Amazon OpenSearch Service-managed VPC endpoint.
Options to specify the subnets and security groups for VPC endpoint. For more information, see VPC Endpoints for Amazon Elasticsearch Service Domains.
Specifies the zone awareness configuration for the domain cluster, such as the number of availability zones.
Enums§
- When writing a match expression against
AutoTuneDesiredState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
AutoTuneState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
AutoTuneType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ConfigChangeStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DeploymentStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DescribePackagesFilterName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DomainPackageStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DomainProcessingStatusType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
EngineType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
EsPartitionInstanceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
EsWarmPartitionInstanceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
InboundCrossClusterSearchConnectionStatusCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
InitiatedBy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
LogType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
OptionState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
OutboundCrossClusterSearchConnectionStatusCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
OverallChangeStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PackageStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PackageType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PrincipalType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PropertyValueType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ReservedElasticsearchInstancePaymentOption
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
RollbackOnDisable
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ScheduledAutoTuneActionType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ScheduledAutoTuneSeverityType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TimeUnit
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TlsSecurityPolicy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
UpgradeStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
UpgradeStep
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
VolumeType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
VpcEndpointErrorCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
VpcEndpointStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.