Module aws_sdk_servicediscovery::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS Cloud Map can respond with.

Structs

• DnsConfig

  A complex type that contains information about the Amazon Route 53 DNS records that you want Cloud Map to create when you register an instance.

• DnsConfigChange

  A complex type that contains information about changes to the Route 53 DNS records that Cloud Map creates when you register an instance.

• DnsProperties

  A complex type that contains the ID for the Route 53 hosted zone that Cloud Map creates when you create a namespace.

• DnsRecord

  A complex type that contains information about the Route 53 DNS records that you want Cloud Map to create when you register an instance.

• HealthCheckConfig

  Public DNS and HTTP namespaces only. A complex type that contains settings for an optional health check. If you specify settings for a health check, Cloud Map associates the health check with the records that you specify in DnsConfig.

• HealthCheckCustomConfig

  A complex type that contains information about an optional custom health check. A custom health check, which requires that you use a third-party health checker to evaluate the health of your resources, is useful in the following circumstances:

• HttpInstanceSummary

  In a response to a DiscoverInstances request, HttpInstanceSummary contains information about one instance that matches the values that you specified in the request.

• HttpNamespaceChange

  Updated properties for the HTTP namespace.

• HttpProperties

  A complex type that contains the name of an HTTP namespace.

• Instance

  A complex type that contains information about an instance that Cloud Map creates when you submit a RegisterInstance request.

• InstanceSummary

  A complex type that contains information about the instances that you registered by using a specified service.

• Namespace

  A complex type that contains information about a specified namespace.

• NamespaceFilter

  A complex type that identifies the namespaces that you want to list. You can choose to list public or private namespaces.

• NamespaceProperties

  A complex type that contains information that's specific to the namespace type.

• NamespaceSummary

  A complex type that contains information about a namespace.

• Operation

  A complex type that contains information about a specified operation.

• OperationFilter

  A complex type that lets you select the operations that you want to list.

• OperationSummary

  A complex type that contains information about an operation that matches the criteria that you specified in a ListOperations request.

• PrivateDnsNamespaceChange

  Updated properties for the private DNS namespace.

• PrivateDnsNamespaceProperties

  DNS properties for the private DNS namespace.

• PrivateDnsNamespacePropertiesChange

  Updated properties for the private DNS namespace.

• PrivateDnsPropertiesMutable

  DNS properties for the private DNS namespace.

• PrivateDnsPropertiesMutableChange

  Updated DNS properties for the private DNS namespace.

• PublicDnsNamespaceChange

  Updated properties for the public DNS namespace.

• PublicDnsNamespaceProperties

  DNS properties for the public DNS namespace.

• PublicDnsNamespacePropertiesChange

  Updated properties for the public DNS namespace.

• PublicDnsPropertiesMutable

  DNS properties for the public DNS namespace.

• PublicDnsPropertiesMutableChange

  Updated DNS properties for the public DNS namespace.

• Service

  A complex type that contains information about the specified service.

• ServiceChange

  A complex type that contains changes to an existing service.

• ServiceFilter

  A complex type that lets you specify the namespaces that you want to list services for.

• ServiceSummary

  A complex type that contains information about a specified service.

• Soa

  Start of Authority (SOA) properties for a public or private DNS namespace.

• SoaChange

  Updated Start of Authority (SOA) properties for a public or private DNS namespace.

• Tag

  A custom key-value pair that's associated with a resource.

Enums

• CustomHealthStatus
  When writing a match expression against CustomHealthStatus, 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.
• FilterCondition
  When writing a match expression against FilterCondition, 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.
• HealthCheckType
  When writing a match expression against HealthCheckType, 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.
• HealthStatus
  When writing a match expression against HealthStatus, 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.
• HealthStatusFilter
  When writing a match expression against HealthStatusFilter, 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.
• NamespaceFilterName
  When writing a match expression against NamespaceFilterName, 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.
• NamespaceType
  When writing a match expression against NamespaceType, 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.
• OperationFilterName
  When writing a match expression against OperationFilterName, 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.
• OperationStatus
  When writing a match expression against OperationStatus, 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.
• OperationTargetType
  When writing a match expression against OperationTargetType, 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.
• OperationType
  When writing a match expression against OperationType, 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.
• RecordType
  When writing a match expression against RecordType, 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.
• RoutingPolicy
  When writing a match expression against RoutingPolicy, 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.
• ServiceFilterName
  When writing a match expression against ServiceFilterName, 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.
• ServiceType
  When writing a match expression against ServiceType, 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.
• ServiceTypeOption
  When writing a match expression against ServiceTypeOption, 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.