選取您的 Cookie 偏好設定

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

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

Considerations when using AWS PrivateLink for Neptune Analytics

焦點模式
Considerations when using AWS PrivateLink for Neptune Analytics - Neptune Analytics
此頁面尚未翻譯為您的語言。 請求翻譯

Amazon VPC considerations apply to AWS PrivateLink for Neptune Analytics. For more information, see Interface endpoint considerations and AWS PrivateLink quotas in the AWS PrivateLink guide. Additionally, the following restrictions apply:

  1. The AWS PrivateLink for Neptune Analytics control plane i.e. neptune-graph service does not support VPC endpoint policies. However, AWS PrivateLink for Neptune Analytics data plane i.e. neptune-graph-data service supports VPC endpoint policies.

  2. The AWS PrivateLink for Neptune Analytics supports Federal Information Processing Standard (FIPS) endpoints in US East (N. Virginia), US East (Ohio), and US West (Oregon) for control plane API operations under the service name neptune-graph-fips. FIPS endpoints are not supported in any AWS region for AWS PrivateLink for data plane API operations.

  3. Transport Layer Security (TLS) 1.1 is not supported.

  4. Private and Hybrid Domain Name System (DNS) services are not supported.

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