Module types

Module types 

Source
Expand description

Data structures used by operation inputs/outputs.

Modules§

builders
Builders
error
Error types that Amazon Route 53 can respond with.

Structs§

AccountLimit

A complex type that contains the type of limit that you specified in the request and the current value for that limit.

AlarmIdentifier

A complex type that identifies the CloudWatch alarm that you want Amazon Route 53 health checkers to use to determine whether the specified health check is healthy.

AliasTarget

Alias resource record sets only: Information about the Amazon Web Services resource, such as a CloudFront distribution or an Amazon S3 bucket, that you want to route traffic to.

When creating resource record sets for a private hosted zone, note the following:

Change

The information for each resource record set that you want to change.

ChangeBatch

The information for a change request.

ChangeInfo

A complex type that describes change information about changes made to your hosted zone.

CidrBlockSummary

A complex type that lists the CIDR blocks.

CidrCollection

A complex type that identifies a CIDR collection.

CidrCollectionChange

A complex type that contains information about the CIDR collection change.

CidrRoutingConfig

The object that is specified in resource record set object when you are linking a resource record set to a CIDR location.

A LocationName with an asterisk “*” can be used to create a default CIDR record. CollectionId is still required for default record.

CloudWatchAlarmConfiguration

A complex type that contains information about the CloudWatch alarm that Amazon Route 53 is monitoring for this health check.

CollectionSummary

A complex type that is an entry in an CidrCollection array.

Coordinates

A complex type that lists the coordinates for a geoproximity resource record.

DelegationSet

A complex type that lists the name servers in a delegation set, as well as the CallerReference and the ID for the delegation set.

Dimension

For the metric that the CloudWatch alarm is associated with, a complex type that contains information about one dimension.

DnssecStatus

A string representing the status of DNSSEC signing.

GeoLocation

A complex type that contains information about a geographic location.

GeoLocationDetails

A complex type that contains the codes and full continent, country, and subdivision names for the specified geolocation code.

GeoProximityLocation

(Resource record sets only): A complex type that lets you specify where your resources are located. Only one of LocalZoneGroup, Coordinates, or Amazon Web ServicesRegion is allowed per request at a time.

For more information about geoproximity routing, see Geoproximity routing in the Amazon Route 53 Developer Guide.

HealthCheck

A complex type that contains information about one health check that is associated with the current Amazon Web Services account.

HealthCheckConfig

A complex type that contains information about the health check.

HealthCheckObservation

A complex type that contains the last failure reason as reported by one Amazon Route 53 health checker.

HostedZone

A complex type that contains general information about the hosted zone.

HostedZoneConfig

A complex type that contains an optional comment about your hosted zone. If you don't want to specify a comment, omit both the HostedZoneConfig and Comment elements.

HostedZoneLimit

A complex type that contains the type of limit that you specified in the request and the current value for that limit.

HostedZoneOwner

A complex type that identifies a hosted zone that a specified Amazon VPC is associated with and the owner of the hosted zone. If there is a value for OwningAccount, there is no value for OwningService, and vice versa.

HostedZoneSummary

In the response to a ListHostedZonesByVPC request, the HostedZoneSummaries element contains one HostedZoneSummary element for each hosted zone that the specified Amazon VPC is associated with. Each HostedZoneSummary element contains the hosted zone name and ID, and information about who owns the hosted zone.

KeySigningKey

A key-signing key (KSK) is a complex type that represents a public/private key pair. The private key is used to generate a digital signature for the zone signing key (ZSK). The public key is stored in the DNS and is used to authenticate the ZSK. A KSK is always associated with a hosted zone; it cannot exist by itself.

LinkedService

If a health check or hosted zone was created by another service, LinkedService is a complex type that describes the service that created the resource. When a resource is created by another service, you can't edit or delete it using Amazon Route 53.

LocationSummary

A complex type that contains information about the CIDR location.

QueryLoggingConfig

A complex type that contains information about a configuration for DNS query logging.

ResourceRecord

Information specific to the resource record.

If you're creating an alias resource record set, omit ResourceRecord.

ResourceRecordSet

Information about the resource record set to create or delete.

ResourceTagSet

A complex type containing a resource and its associated tags.

ReusableDelegationSetLimit

A complex type that contains the type of limit that you specified in the request and the current value for that limit.

StatusReport

A complex type that contains the status that one Amazon Route 53 health checker reports and the time of the health check.

Tag

A complex type that contains information about a tag that you want to add or edit for the specified health check or hosted zone.

TrafficPolicy

A complex type that contains settings for a traffic policy.

TrafficPolicyInstance

A complex type that contains settings for the new traffic policy instance.

TrafficPolicySummary

A complex type that contains information about the latest version of one traffic policy that is associated with the current Amazon Web Services account.

Vpc

(Private hosted zones only) A complex type that contains information about an Amazon VPC.

If you associate a private hosted zone with an Amazon VPC when you make a CreateHostedZone request, the following parameters are also required.

Enums§

AccountLimitType
When writing a match expression against AccountLimitType, 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.
ChangeAction
When writing a match expression against ChangeAction, 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.
ChangeStatus
When writing a match expression against ChangeStatus, 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.
CidrCollectionChangeAction
When writing a match expression against CidrCollectionChangeAction, 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.
CloudWatchRegion
When writing a match expression against CloudWatchRegion, 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.
ComparisonOperator
When writing a match expression against ComparisonOperator, 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.
HealthCheckRegion
When writing a match expression against HealthCheckRegion, 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.
HostedZoneLimitType
When writing a match expression against HostedZoneLimitType, 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.
HostedZoneType
When writing a match expression against HostedZoneType, 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.
InsufficientDataHealthStatus
When writing a match expression against InsufficientDataHealthStatus, 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.
ResettableElementName
When writing a match expression against ResettableElementName, 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.
ResourceRecordSetFailover
When writing a match expression against ResourceRecordSetFailover, 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.
ResourceRecordSetRegion
When writing a match expression against ResourceRecordSetRegion, 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.
ReusableDelegationSetLimitType
When writing a match expression against ReusableDelegationSetLimitType, 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.
RrType
When writing a match expression against RrType, 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.
Statistic
When writing a match expression against Statistic, 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.
TagResourceType
When writing a match expression against TagResourceType, 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.
VpcRegion
When writing a match expression against VpcRegion, 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.