#[non_exhaustive]pub struct ResolverEndpoint {Show 16 fields
pub id: Option<String>,
pub creator_request_id: Option<String>,
pub arn: Option<String>,
pub name: Option<String>,
pub security_group_ids: Option<Vec<String>>,
pub direction: Option<ResolverEndpointDirection>,
pub ip_address_count: Option<i32>,
pub host_vpc_id: Option<String>,
pub status: Option<ResolverEndpointStatus>,
pub status_message: Option<String>,
pub creation_time: Option<String>,
pub modification_time: Option<String>,
pub outpost_arn: Option<String>,
pub preferred_instance_type: Option<String>,
pub resolver_endpoint_type: Option<ResolverEndpointType>,
pub protocols: Option<Vec<Protocol>>,
}
Expand description
In the response to a CreateResolverEndpoint, DeleteResolverEndpoint, GetResolverEndpoint, Updates the name, or ResolverEndpointType for an endpoint, or UpdateResolverEndpoint request, a complex type that contains settings for an existing inbound or outbound Resolver endpoint.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.id: Option<String>
The ID of the Resolver endpoint.
creator_request_id: Option<String>
A unique string that identifies the request that created the Resolver endpoint. The CreatorRequestId
allows failed requests to be retried without the risk of running the operation twice.
arn: Option<String>
The ARN (Amazon Resource Name) for the Resolver endpoint.
name: Option<String>
The name that you assigned to the Resolver endpoint when you submitted a CreateResolverEndpoint request.
security_group_ids: Option<Vec<String>>
The ID of one or more security groups that control access to this VPC. The security group must include one or more inbound rules (for inbound endpoints) or outbound rules (for outbound endpoints). Inbound and outbound rules must allow TCP and UDP access. For inbound access, open port 53. For outbound access, open the port that you're using for DNS queries on your network.
direction: Option<ResolverEndpointDirection>
Indicates whether the Resolver endpoint allows inbound or outbound DNS queries:
-
INBOUND
: allows DNS queries to your VPC from your network -
OUTBOUND
: allows DNS queries from your VPC to your network -
INBOUND_DELEGATION
: Resolver delegates queries to Route 53 private hosted zones from your network.
ip_address_count: Option<i32>
The number of IP addresses that the Resolver endpoint can use for DNS queries.
host_vpc_id: Option<String>
The ID of the VPC that you want to create the Resolver endpoint in.
status: Option<ResolverEndpointStatus>
A code that specifies the current status of the Resolver endpoint. Valid values include the following:
-
CREATING
: Resolver is creating and configuring one or more Amazon VPC network interfaces for this endpoint. -
OPERATIONAL
: The Amazon VPC network interfaces for this endpoint are correctly configured and able to pass inbound or outbound DNS queries between your network and Resolver. -
UPDATING
: Resolver is associating or disassociating one or more network interfaces with this endpoint. -
AUTO_RECOVERING
: Resolver is trying to recover one or more of the network interfaces that are associated with this endpoint. During the recovery process, the endpoint functions with limited capacity because of the limit on the number of DNS queries per IP address (per network interface). For the current limit, see Limits on Route 53 Resolver. -
ACTION_NEEDED
: This endpoint is unhealthy, and Resolver can't automatically recover it. To resolve the problem, we recommend that you check each IP address that you associated with the endpoint. For each IP address that isn't available, add another IP address and then delete the IP address that isn't available. (An endpoint must always include at least two IP addresses.) A status ofACTION_NEEDED
can have a variety of causes. Here are two common causes:-
One or more of the network interfaces that are associated with the endpoint were deleted using Amazon VPC.
-
The network interface couldn't be created for some reason that's outside the control of Resolver.
-
-
DELETING
: Resolver is deleting this endpoint and the associated network interfaces.
status_message: Option<String>
A detailed description of the status of the Resolver endpoint.
creation_time: Option<String>
The date and time that the endpoint was created, in Unix time format and Coordinated Universal Time (UTC).
modification_time: Option<String>
The date and time that the endpoint was last modified, in Unix time format and Coordinated Universal Time (UTC).
outpost_arn: Option<String>
The ARN (Amazon Resource Name) for the Outpost.
preferred_instance_type: Option<String>
The Amazon EC2 instance type.
resolver_endpoint_type: Option<ResolverEndpointType>
The Resolver endpoint IP address type.
protocols: Option<Vec<Protocol>>
Protocols used for the endpoint. DoH-FIPS is applicable for a default inbound endpoints only.
For an inbound endpoint you can apply the protocols as follows:
-
Do53 and DoH in combination.
-
Do53 and DoH-FIPS in combination.
-
Do53 alone.
-
DoH alone.
-
DoH-FIPS alone.
-
None, which is treated as Do53.
For a delegation inbound endpoint you can use Do53 only.
For an outbound endpoint you can apply the protocols as follows:
-
Do53 and DoH in combination.
-
Do53 alone.
-
DoH alone.
-
None, which is treated as Do53.
Implementations§
Source§impl ResolverEndpoint
impl ResolverEndpoint
Sourcepub fn creator_request_id(&self) -> Option<&str>
pub fn creator_request_id(&self) -> Option<&str>
A unique string that identifies the request that created the Resolver endpoint. The CreatorRequestId
allows failed requests to be retried without the risk of running the operation twice.
Sourcepub fn name(&self) -> Option<&str>
pub fn name(&self) -> Option<&str>
The name that you assigned to the Resolver endpoint when you submitted a CreateResolverEndpoint request.
Sourcepub fn security_group_ids(&self) -> &[String]
pub fn security_group_ids(&self) -> &[String]
The ID of one or more security groups that control access to this VPC. The security group must include one or more inbound rules (for inbound endpoints) or outbound rules (for outbound endpoints). Inbound and outbound rules must allow TCP and UDP access. For inbound access, open port 53. For outbound access, open the port that you're using for DNS queries on your network.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .security_group_ids.is_none()
.
Sourcepub fn direction(&self) -> Option<&ResolverEndpointDirection>
pub fn direction(&self) -> Option<&ResolverEndpointDirection>
Indicates whether the Resolver endpoint allows inbound or outbound DNS queries:
-
INBOUND
: allows DNS queries to your VPC from your network -
OUTBOUND
: allows DNS queries from your VPC to your network -
INBOUND_DELEGATION
: Resolver delegates queries to Route 53 private hosted zones from your network.
Sourcepub fn ip_address_count(&self) -> Option<i32>
pub fn ip_address_count(&self) -> Option<i32>
The number of IP addresses that the Resolver endpoint can use for DNS queries.
Sourcepub fn host_vpc_id(&self) -> Option<&str>
pub fn host_vpc_id(&self) -> Option<&str>
The ID of the VPC that you want to create the Resolver endpoint in.
Sourcepub fn status(&self) -> Option<&ResolverEndpointStatus>
pub fn status(&self) -> Option<&ResolverEndpointStatus>
A code that specifies the current status of the Resolver endpoint. Valid values include the following:
-
CREATING
: Resolver is creating and configuring one or more Amazon VPC network interfaces for this endpoint. -
OPERATIONAL
: The Amazon VPC network interfaces for this endpoint are correctly configured and able to pass inbound or outbound DNS queries between your network and Resolver. -
UPDATING
: Resolver is associating or disassociating one or more network interfaces with this endpoint. -
AUTO_RECOVERING
: Resolver is trying to recover one or more of the network interfaces that are associated with this endpoint. During the recovery process, the endpoint functions with limited capacity because of the limit on the number of DNS queries per IP address (per network interface). For the current limit, see Limits on Route 53 Resolver. -
ACTION_NEEDED
: This endpoint is unhealthy, and Resolver can't automatically recover it. To resolve the problem, we recommend that you check each IP address that you associated with the endpoint. For each IP address that isn't available, add another IP address and then delete the IP address that isn't available. (An endpoint must always include at least two IP addresses.) A status ofACTION_NEEDED
can have a variety of causes. Here are two common causes:-
One or more of the network interfaces that are associated with the endpoint were deleted using Amazon VPC.
-
The network interface couldn't be created for some reason that's outside the control of Resolver.
-
-
DELETING
: Resolver is deleting this endpoint and the associated network interfaces.
Sourcepub fn status_message(&self) -> Option<&str>
pub fn status_message(&self) -> Option<&str>
A detailed description of the status of the Resolver endpoint.
Sourcepub fn creation_time(&self) -> Option<&str>
pub fn creation_time(&self) -> Option<&str>
The date and time that the endpoint was created, in Unix time format and Coordinated Universal Time (UTC).
Sourcepub fn modification_time(&self) -> Option<&str>
pub fn modification_time(&self) -> Option<&str>
The date and time that the endpoint was last modified, in Unix time format and Coordinated Universal Time (UTC).
Sourcepub fn outpost_arn(&self) -> Option<&str>
pub fn outpost_arn(&self) -> Option<&str>
The ARN (Amazon Resource Name) for the Outpost.
Sourcepub fn preferred_instance_type(&self) -> Option<&str>
pub fn preferred_instance_type(&self) -> Option<&str>
The Amazon EC2 instance type.
Sourcepub fn resolver_endpoint_type(&self) -> Option<&ResolverEndpointType>
pub fn resolver_endpoint_type(&self) -> Option<&ResolverEndpointType>
The Resolver endpoint IP address type.
Sourcepub fn protocols(&self) -> &[Protocol]
pub fn protocols(&self) -> &[Protocol]
Protocols used for the endpoint. DoH-FIPS is applicable for a default inbound endpoints only.
For an inbound endpoint you can apply the protocols as follows:
-
Do53 and DoH in combination.
-
Do53 and DoH-FIPS in combination.
-
Do53 alone.
-
DoH alone.
-
DoH-FIPS alone.
-
None, which is treated as Do53.
For a delegation inbound endpoint you can use Do53 only.
For an outbound endpoint you can apply the protocols as follows:
-
Do53 and DoH in combination.
-
Do53 alone.
-
DoH alone.
-
None, which is treated as Do53.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .protocols.is_none()
.
Source§impl ResolverEndpoint
impl ResolverEndpoint
Sourcepub fn builder() -> ResolverEndpointBuilder
pub fn builder() -> ResolverEndpointBuilder
Creates a new builder-style object to manufacture ResolverEndpoint
.
Trait Implementations§
Source§impl Clone for ResolverEndpoint
impl Clone for ResolverEndpoint
Source§fn clone(&self) -> ResolverEndpoint
fn clone(&self) -> ResolverEndpoint
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for ResolverEndpoint
impl Debug for ResolverEndpoint
Source§impl PartialEq for ResolverEndpoint
impl PartialEq for ResolverEndpoint
impl StructuralPartialEq for ResolverEndpoint
Auto Trait Implementations§
impl Freeze for ResolverEndpoint
impl RefUnwindSafe for ResolverEndpoint
impl Send for ResolverEndpoint
impl Sync for ResolverEndpoint
impl Unpin for ResolverEndpoint
impl UnwindSafe for ResolverEndpoint
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);