import { Command as $Command } from "@smithy/smithy-client"; import type { MetadataBearer as __MetadataBearer } from "@smithy/types"; import type { EC2ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../EC2Client"; import type { GetRouteServerPropagationsRequest, GetRouteServerPropagationsResult } from "../models/models_6"; /** * @public */ export type { __MetadataBearer }; export { $Command }; /** * @public * * The input for {@link GetRouteServerPropagationsCommand}. */ export interface GetRouteServerPropagationsCommandInput extends GetRouteServerPropagationsRequest { } /** * @public * * The output of {@link GetRouteServerPropagationsCommand}. */ export interface GetRouteServerPropagationsCommandOutput extends GetRouteServerPropagationsResult, __MetadataBearer { } declare const GetRouteServerPropagationsCommand_base: { new (input: GetRouteServerPropagationsCommandInput): import("@smithy/smithy-client").CommandImpl; new (input: GetRouteServerPropagationsCommandInput): import("@smithy/smithy-client").CommandImpl; getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions; }; /** *

Gets information about the route propagations for the specified route server.

*

When enabled, route server propagation installs the routes in the FIB on the route table you've specified. Route server supports IPv4 and IPv6 route propagation.

*

Amazon VPC Route Server simplifies routing for traffic between workloads that are deployed within a VPC and its internet gateways. With this feature, * VPC Route Server dynamically updates VPC and internet gateway route tables with your preferred IPv4 or IPv6 routes to achieve routing fault tolerance for those workloads. This enables you to automatically reroute traffic within a VPC, which increases the manageability of VPC routing and interoperability with third-party workloads.

*

Route server supports the follow route table types:

* *

Route server does not support route tables associated with virtual private gateways. To propagate routes into a transit gateway route table, use Transit Gateway Connect.

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript * import { EC2Client, GetRouteServerPropagationsCommand } from "@aws-sdk/client-ec2"; // ES Modules import * // const { EC2Client, GetRouteServerPropagationsCommand } = require("@aws-sdk/client-ec2"); // CommonJS import * // import type { EC2ClientConfig } from "@aws-sdk/client-ec2"; * const config = {}; // type is EC2ClientConfig * const client = new EC2Client(config); * const input = { // GetRouteServerPropagationsRequest * RouteServerId: "STRING_VALUE", // required * RouteTableId: "STRING_VALUE", * DryRun: true || false, * }; * const command = new GetRouteServerPropagationsCommand(input); * const response = await client.send(command); * // { // GetRouteServerPropagationsResult * // RouteServerPropagations: [ // RouteServerPropagationsList * // { // RouteServerPropagation * // RouteServerId: "STRING_VALUE", * // RouteTableId: "STRING_VALUE", * // State: "pending" || "available" || "deleting", * // }, * // ], * // }; * * ``` * * @param GetRouteServerPropagationsCommandInput - {@link GetRouteServerPropagationsCommandInput} * @returns {@link GetRouteServerPropagationsCommandOutput} * @see {@link GetRouteServerPropagationsCommandInput} for command's `input` shape. * @see {@link GetRouteServerPropagationsCommandOutput} for command's `response` shape. * @see {@link EC2ClientResolvedConfig | config} for EC2Client's `config` shape. * * @throws {@link EC2ServiceException} *

Base exception class for all service exceptions from EC2 service.

* * * @public */ export declare class GetRouteServerPropagationsCommand extends GetRouteServerPropagationsCommand_base { /** @internal type navigation helper, not in runtime. */ protected static __types: { api: { input: GetRouteServerPropagationsRequest; output: GetRouteServerPropagationsResult; }; sdk: { input: GetRouteServerPropagationsCommandInput; output: GetRouteServerPropagationsCommandOutput; }; }; }