@aws-sdk/client-route53resolver

中文文档
3.1164.0发布于 2026/11/07Apache-2.0TypeScriptESM + CJS近 30 天下载 25.1万

AWS SDK for JavaScript Route53resolver Client for Node.js, Browser and React Native

原始使用文档
文档目录10 节
  1. Description
  2. Installing
  3. Getting Started
  4. Import
  5. Usage
  6. Troubleshooting
  7. Getting Help
  8. Contributing
  9. License
  10. Client Commands (Operations List)

@aws-sdk/client-route53resolver

Description

AWS SDK for JavaScript Route53Resolver Client for Node.js, Browser and React Native.

When you create a VPC using Amazon VPC, you automatically get DNS resolution within the VPC from Route 53 Resolver. By default, Resolver answers DNS queries for VPC domain names such as domain names for EC2 instances or Elastic Load Balancing load balancers. Resolver performs recursive lookups against public name servers for all other domain names.

You can also configure DNS resolution between your VPC and your network over a Direct Connect or VPN connection:

Forward DNS queries from resolvers on your network to Route 53 Resolver

DNS resolvers on your network can forward DNS queries to Resolver in a specified VPC. This allows your DNS resolvers to easily resolve domain names for Amazon Web Services resources such as EC2 instances or records in a Route 53 private hosted zone. For more information, see How DNS Resolvers on Your Network Forward DNS Queries to Route 53 Resolver in the Amazon Route 53 Developer Guide.

Conditionally forward queries from a VPC to resolvers on your network

You can configure Resolver to forward queries that it receives from EC2 instances in your VPCs to DNS resolvers on your network. To forward selected queries, you create Resolver rules that specify the domain names for the DNS queries that you want to forward (such as example.com), and the IP addresses of the DNS resolvers on your network that you want to forward the queries to. If a query matches multiple rules (example.com, acme.example.com), Resolver chooses the rule with the most specific match (acme.example.com) and forwards the query to the IP addresses that you specified in that rule. For more information, see How Route 53 Resolver Forwards DNS Queries from Your VPCs to Your Network in the Amazon Route 53 Developer Guide.

Like Amazon VPC, Resolver is Regional. In each Region where you have VPCs, you can choose whether to forward queries from your VPCs to your network (outbound queries), from your network to your VPCs (inbound queries), or both.

Installing

To install this package, use the CLI of your favorite package manager:

  • npm install @aws-sdk/client-route53resolver
  • yarn add @aws-sdk/client-route53resolver
  • pnpm add @aws-sdk/client-route53resolver

Getting Started

Import

The AWS SDK is modulized by clients and commands. To send a request, you only need to import the Route53ResolverClient and the commands you need, for example ListResolverRulesCommand:

// ES5 example
const { Route53ResolverClient, ListResolverRulesCommand } = require("@aws-sdk/client-route53resolver");
// ES6+ example
import { Route53ResolverClient, ListResolverRulesCommand } from "@aws-sdk/client-route53resolver";

Usage

To send a request:

  • Instantiate a client with configuration (e.g. credentials, region).
  • Instantiate a command with input parameters.
  • Call the send operation on the client, providing the command object as input.
const client = new Route53ResolverClient({ region: "REGION" });

const params = { /** input parameters */ };
const command = new ListResolverRulesCommand(params);

Async/await

We recommend using the await operator to wait for the promise returned by send operation as follows:

// async/await.
try {
  const data = await client.send(command);
  // process data.
} catch (error) {
  // error handling.
} finally {
  // finally.
}

Promises

You can also use Promise chaining.

client
  .send(command)
  .then((data) => {
    // process data.
  })
  .catch((error) => {
    // error handling.
  })
  .finally(() => {
    // finally.
  });

Aggregated client

The aggregated client class is exported from the same package, but without the "Client" suffix.

Route53Resolver extends Route53ResolverClient and additionally supports all operations, waiters, and paginators as methods. This style may be familiar to you from the AWS SDK for JavaScript v2.

If you are bundling the AWS SDK, we recommend using only the bare-bones client (Route53ResolverClient). More details are in the blog post on modular packages in AWS SDK for JavaScript.

import { Route53Resolver } from "@aws-sdk/client-route53resolver";

const client = new Route53Resolver({ region: "REGION" });

// async/await.
try {
  const data = await client.listResolverRules(params);
  // process data.
} catch (error) {
  // error handling.
}

// Promises.
client
  .listResolverRules(params)
  .then((data) => {
    // process data.
  })
  .catch((error) => {
    // error handling.
  });

// callbacks (not recommended).
client.listResolverRules(params, (err, data) => {
  // process err and data.
});

Troubleshooting

When the service returns an exception, the error will include the exception information, as well as response metadata (e.g. request id).

try {
  const data = await client.send(command);
  // process data.
} catch (error) {
  const { requestId, cfId, extendedRequestId } = error.$metadata;
  console.log({ requestId, cfId, extendedRequestId });
  /**
   * The keys within exceptions are also parsed.
   * You can access them by specifying exception names:
   * if (error.name === 'SomeServiceException') {
   *     const value = error.specialKeyInException;
   * }
   */
}

See also docs/ERROR_HANDLING.

Getting Help

Please use these community resources for getting help. We use GitHub issues for tracking bugs and feature requests, but have limited bandwidth to address them.

To test your universal JavaScript code in Node.js, browser and react-native environments, visit our code samples repo.

Contributing

This client code is generated automatically. Any modifications will be overwritten the next time the @aws-sdk/client-route53resolver package is updated. To contribute to client you can check our generate clients scripts.

License

This SDK is distributed under the Apache License, Version 2.0, see LICENSE for more information.

Client Commands (Operations List)

AssociateFirewallRuleGroup

Command API Reference / Input / Output

AssociateResolverEndpointIpAddress

Command API Reference / Input / Output

AssociateResolverQueryLogConfig

Command API Reference / Input / Output

AssociateResolverRule

Command API Reference / Input / Output

BatchCreateFirewallRule

Command API Reference / Input / Output

BatchDeleteFirewallRule

Command API Reference / Input / Output

BatchUpdateFirewallRule

Command API Reference / Input / Output

CreateFirewallDomainList

Command API Reference / Input / Output

CreateFirewallRule

Command API Reference / Input / Output

CreateFirewallRuleGroup

Command API Reference / Input / Output

CreateOutpostResolver

Command API Reference / Input / Output

CreateResolverEndpoint

Command API Reference / Input / Output

CreateResolverQueryLogConfig

Command API Reference / Input / Output

CreateResolverRule

Command API Reference / Input / Output

DeleteFirewallDomainList

Command API Reference / Input / Output

DeleteFirewallRule

Command API Reference / Input / Output

DeleteFirewallRuleGroup

Command API Reference / Input / Output

DeleteOutpostResolver

Command API Reference / Input / Output

DeleteResolverEndpoint

Command API Reference / Input / Output

DeleteResolverQueryLogConfig

Command API Reference / Input / Output

DeleteResolverRule

Command API Reference / Input / Output

DisassociateFirewallRuleGroup

Command API Reference / Input / Output

DisassociateResolverEndpointIpAddress

Command API Reference / Input / Output

DisassociateResolverQueryLogConfig

Command API Reference / Input / Output

DisassociateResolverRule

Command API Reference / Input / Output

GetFirewallConfig

Command API Reference / Input / Output

GetFirewallDomainList

Command API Reference / Input / Output

GetFirewallRuleGroup

Command API Reference / Input / Output

GetFirewallRuleGroupAssociation

Command API Reference / Input / Output

GetFirewallRuleGroupPolicy

Command API Reference / Input / Output

GetOutpostResolver

Command API Reference / Input / Output

GetResolverConfig

Command API Reference / Input / Output

GetResolverDnssecConfig

Command API Reference / Input / Output

GetResolverEndpoint

Command API Reference / Input / Output

GetResolverQueryLogConfig

Command API Reference / Input / Output

GetResolverQueryLogConfigAssociation

Command API Reference / Input / Output

GetResolverQueryLogConfigPolicy

Command API Reference / Input / Output

GetResolverRule

Command API Reference / Input / Output

GetResolverRuleAssociation

Command API Reference / Input / Output

GetResolverRulePolicy

Command API Reference / Input / Output

ImportFirewallDomains

Command API Reference / Input / Output

ListFirewallConfigs

Command API Reference / Input / Output

ListFirewallDomainLists

Command API Reference / Input / Output

ListFirewallDomains

Command API Reference / Input / Output

ListFirewallRuleGroupAssociations

Command API Reference / Input / Output

ListFirewallRuleGroups

Command API Reference / Input / Output

ListFirewallRules

Command API Reference / Input / Output

ListFirewallRuleTypes

Command API Reference / Input / Output

ListOutpostResolvers

Command API Reference / Input / Output

ListResolverConfigs

Command API Reference / Input / Output

ListResolverDnssecConfigs

Command API Reference / Input / Output

ListResolverEndpointIpAddresses

Command API Reference / Input / Output

ListResolverEndpoints

Command API Reference / Input / Output

ListResolverQueryLogConfigAssociations

Command API Reference / Input / Output

ListResolverQueryLogConfigs

Command API Reference / Input / Output

ListResolverRuleAssociations

Command API Reference / Input / Output

ListResolverRules

Command API Reference / Input / Output

ListTagsForResource

Command API Reference / Input / Output

PutFirewallRuleGroupPolicy

Command API Reference / Input / Output

PutResolverQueryLogConfigPolicy

Command API Reference / Input / Output

PutResolverRulePolicy

Command API Reference / Input / Output

TagResource

Command API Reference / Input / Output

UntagResource

Command API Reference / Input / Output

UpdateFirewallConfig

Command API Reference / Input / Output

UpdateFirewallDomains

Command API Reference / Input / Output

UpdateFirewallRule

Command API Reference / Input / Output

UpdateFirewallRuleGroupAssociation

Command API Reference / Input / Output

UpdateOutpostResolver

Command API Reference / Input / Output

UpdateResolverConfig

Command API Reference / Input / Output

UpdateResolverDnssecConfig

Command API Reference / Input / Output

UpdateResolverEndpoint

Command API Reference / Input / Output

UpdateResolverRule

Command API Reference / Input / Output

版本与发布记录

@aws-sdk/client-route53resolver 共发布 736 个版本,首次发布于 2020/01/08;过去 12 个月发布了 220 个版本。

版本发布日期距今
3.1164.0latest2026/11/071 天前
3.1163.02026/11/062 天前
3.1162.02026/11/052 天前
3.1161.02026/10/318 天前
3.1160.02026/10/309 天前
3.1159.02026/10/2910 天前

其他发布通道:alpha → 1.0.0-alpha.25,beta → 1.0.0-beta.5,gamma → 1.0.0-gamma.11,rc → 3.5.1-rc.0。

关于 @aws-sdk/client-route53resolver 的常见问题

@aws-sdk/client-route53resolver 是什么?

AWS SDK for JavaScript Route53resolver Client for Node.js, Browser and React Native

如何安装 @aws-sdk/client-route53resolver?

在项目目录运行 npm install @aws-sdk/client-route53resolver,或使用 pnpm add / yarn add / bun add。

@aws-sdk/client-route53resolver 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@aws-sdk/client-route53resolver 支持 ESM 还是 CommonJS?

同时提供 ES Module 与 CommonJS 入口,import 和 require() 都可以使用,打包工具会自动选择合适的版本。

@aws-sdk/client-route53resolver 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=20.0.0。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@aws-sdk/client-route53resolver 可以商用吗?

@aws-sdk/client-route53resolver 使用 Apache-2.0 许可。宽松许可:允许商业使用、修改和再分发,并附带明确的专利授权;分发时需保留许可与 NOTICE 文件,修改过的文件要注明改动。以上为概括,不构成法律意见,请以许可原文为准。

@aws-sdk/client-route53resolver 的下载量有多少?

根据 npm 官方下载统计,@aws-sdk/client-route53resolver 在 2026/10/08 – 2026/11/06 这 30 天内被下载 251,040 次,日均约 8,368 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@aws-sdk/client-route53resolver 还在维护吗?

最新版本 3.1164.0 发布于 2026/11/07(1 天前);至今共发布 736 个版本,其中过去 12 个月发布了 220 个;首次发布于 2020/01/08。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。