選取您的 Cookie 偏好設定

我們使用提供自身網站和服務所需的基本 Cookie 和類似工具。我們使用效能 Cookie 收集匿名統計資料,以便了解客戶如何使用我們的網站並進行改進。基本 Cookie 無法停用,但可以按一下「自訂」或「拒絕」以拒絕效能 Cookie。

如果您同意,AWS 與經核准的第三方也會使用 Cookie 提供實用的網站功能、記住您的偏好設定,並顯示相關內容,包括相關廣告。若要接受或拒絕所有非必要 Cookie,請按一下「接受」或「拒絕」。若要進行更詳細的選擇,請按一下「自訂」。

Mounting caches from on-premises or a peered Amazon VPC - Amazon File Cache
此頁面尚未翻譯為您的語言。 請求翻譯

Mounting caches from on-premises or a peered Amazon VPC

You can access your cache in two ways. One is from Amazon EC2 instances located in an Amazon VPC that's peered to the cache's VPC. The other is from on-premises clients that are connected to your cache's VPC using AWS Direct Connect or VPN.

Connect the client's VPC and your Amazon File Cache's VPC using either a VPC peering connection or a VPC transit gateway. When you use either option, Amazon EC2 instances that are in one VPC can access caches in another VPC, even if the VPCs belong to different accounts.

Before using the following the procedure, you must set up either a VPC peering connection or a VPC transit gateway.

A transit gateway is a network transit hub that you can use to interconnect your VPCs and on-premises networks. For more information about using VPC transit gateways, see Getting Started with Transit Gateways in the Amazon VPC Transit Gateways Guide.

A VPC peering connection is a networking connection between two VPCs. This type of connection enables you to route traffic between them using private Internet Protocol version 4 (IPv4) or Internet Protocol version 6 (IPv6) addresses. You can use VPC peering to connect VPCs within the same AWS Region or between AWS RegionsAWS Regions. For more information about VPC peering, see What is VPC Peering? in the Amazon VPC Peering Guide.

You can mount your cache from outside its VPC using the IP address of its primary network interface. The primary network interface is the first network interface returned when you run the aws fsx describe-file-caches AWS Command Line Interface (AWS CLI) command. You can also get this IP address from the AWS Management Console.

To retrieve the IP address of the primary network interface for a cache
  1. Open the AWS console at https://console.aws.amazon.com/fsx/.

  2. In the navigation pane, choose Caches.

  3. Choose your cache from the dashboard.

  4. From the Summary details page, choose Network & security.

  5. For Network interface, choose the ID for your primary elastic network interface. This takes you to the Amazon EC2 console.

  6. On the Details tab, find the Primary private IPv4 IP. This is the IP address for your primary network interface.

Note

You can't use Domain Name System (DNS) name resolution when mounting an Amazon File Cache resource from outside the VPC it's associated with.

隱私權網站條款Cookie 偏好設定
© 2025, Amazon Web Services, Inc.或其附屬公司。保留所有權利。