DOCUMENTATION
/
Introdução
Guias
Desenvolvedor
Referência
Notas de lançamento
Tutoriais
Status
  1. Visão geral
    • Catálogo Snowflake Horizon
    • Aplicativos e ferramentas para conexão com o Snowflake
    • Warehouses virtuais
    • Bancos de dados, tabelas e exibições
    • Tipos de dados
      • Integração de dados
        1. Snowflake Openflow
        2. Apache Iceberg™
          1. Tabelas Apache Iceberg™
          2. Snowflake Open Catalog
      • Data engineering
        1. Carregamento de dados
        2. Tabelas dinâmicas
        3. Fluxos e tarefas
        4. Projetos dbt no Snowflake
        5. Descarregamento de dados
      • Storage Lifecycle Policies
      • Migrações
      • Consultas
      • Listagens
      • Colaboração
      • AI e ML do Snowflake
      • Alertas e notificações
      • Segurança
          1. Autenticação
          2. Overview of authentication
          3. Políticas de autenticação
            • Autenticação multifator (MFA)
            • Autenticação federada e SSO
            • Autenticação e rotação de pares de chaves
            • Tokens de acesso programático
              • OAuth
              • Federação de identidades de carga de trabalho
                • Autenticação e segredos de API
                  • Segurança de rede
                  • Proteção contra IP malicioso
                    • Políticas de redes
                      • Regras de rede
                        • Conectividade privada
                        • Conectividade privada de entrada
                            1. AWS PrivateLink
                              • Azure Private Link
                                • Google Cloud Private Service Connect
                                  • Impor acesso somente por privatelink
                                    • Fixação de pontos de extremidade de conectividade privada
                                      • Para estágios internos Snowflake
                                      • Pontos de extremidade da interface AWS VPC para estágios internos
                                        • Pontos de extremidade privados do Azure para estágios internos
                                          • Google Cloud PSC endpoints for internal stages
                                        • Conectividade privada de saída
                                        • Administração e autorização
                                        • Trust Center
                                        • Sessões e políticas de sessão
                                        • Suporte para SCIM
                                        • Controle de acesso
                                        • Criptografia
                                    • Governança de dados
                                    • Privacidade
                                    • Organizações e contas
                                    • Continuidade dos negócios e recuperação de dados
                                    • Otimização de desempenho
                                    • Custo e faturamento
                                    GuiasSegurançaConectividade privada de entradaAWS PrivateLink

                                    AWS PrivateLink e Snowflake¶

                                    Logotipo do Snowflake em preto (sem texto) Recurso Business Critical

                                    Este recurso requer Business Critical (ou superior).

                                    This topic describes how to configure AWS PrivateLink to directly connect your Snowflake account to one or more AWS Virtual Private Clouds (VPCs).

                                    Neste tópico:

                                    AWS PrivateLink: Overview¶

                                    AWS PrivateLink is an AWS service for creating private VPC endpoints that allow direct, secure connectivity between your AWS VPCs and the Snowflake VPC without traversing the public internet. AWS PrivateLink connectivity supports VPC endpoint services and AWS VPCs that are located in the same or in different AWS regions. Cross-region connectivity for AWS PrivateLink allows you to use a custom endpoint service to connect a Snowflake account in a region that is different from your AWS VPC region. Cross-region connectivity isn’t currently supported for any platform as a service (PaaS) services, such as Amazon Simple Storage Service (Amazon S3) or key management service (KMS).

                                    For more information, see the AWS blog page, Introducing Cross-Region Connectivity for AWS PrivateLink. For information about finding the region names for your account, see Find the cloud-provider’s name of the region for your account.

                                    When writing external functions, you can also use AWS PrivateLink with private endpoints.

                                    If you have an on-premises environment, such as a non-hosted data center, you can use AWS Direct Connect with AWS PrivateLink to connect all your virtual and physical environments in a single, private network.

                                    Nota

                                    AWS Direct Connect é um serviço AWS separado que deve ser implementado independentemente do AWS PrivateLink e está fora do escopo deste tópico. Para saber mais sobre a implementação do AWS Direct Connect, entre em contato com a Amazon.

                                    Enable AWS PrivateLink¶

                                    Nota

                                    The self-service enablement process in this section doesn’t currently support authorizing an AWS account identifier from a managed cloud service or a third-party vendor.

                                    To authorize an AWS account identifier for this use case, please retrieve the AWS account identifier from the vendor, and then contact Snowflake Support.

                                    Para habilitar o AWS PrivateLink para sua conta Snowflake, complete as seguintes etapas:

                                    1. Gere um token federado e salve a saída.

                                      1. To generate a token, run the AWS CLI STS command on the command line. get-federation-token requires either an identity and access management user in AWS or the AWS account root user. For details, refer to the AWS documentation.

                                        Importante

                                        The federated token expires after 12 hours. If you call any of the system functions to authorize, verify, or disable your Snowflake account to use AWS PrivateLink and the token has expired, regenerate the token by running the AWS CLI STS command again.

                                        aws sts get-federation-token --name sam
                                        
                                        Copy

                                        Em uma etapa posterior, você fornece a saída deste comando como o argumento federated_token para a função SYSTEM$AUTHORIZE_PRIVATELINK.

                                      2. From your generated token, extract the value of the "FederatedUserId" field. For example, if your token contains the following values:

                                        {
                                         ...
                                           "FederatedUser": {
                                             "FederatedUserId": "185...:sam",
                                             "Arn": "arn:aws:sts::185...:federated-user/sam"
                                           },
                                         "PackedPolicySize": 0
                                        }
                                        
                                        Copy

                                        Extract 185.... In the next step, you provide this 12-digit number as the aws_id argument for the SYSTEM$AUTHORIZE_PRIVATELINK function.

                                    2. Using the ACCOUNTADMIN Snowflake system role, call the SYSTEM$AUTHORIZE_PRIVATELINK function to authorize (enable) AWS PrivateLink for your Snowflake account:

                                      SELECT SYSTEM$AUTHORIZE_PRIVATELINK ( '<aws_id>' , '<federated_token>' );
                                      
                                      Copy

                                      Onde:

                                      • 'aws_id'

                                        O identificador de 12 dígitos que identifica de forma única sua conta no Amazon Web Services (AWS) como uma cadeia de caracteres.

                                      • 'federated_token'

                                        O valor do token federado que contém as credenciais de acesso para um usuário federado como uma cadeia de caracteres.

                                      Por exemplo:

                                      USE ROLE ACCOUNTADMIN;
                                      
                                      SELECT SYSTEM$AUTHORIZE_PRIVATELINK (
                                        '185...',
                                          '{
                                            "Credentials": {
                                              "AccessKeyId": "ASI...",
                                              "SecretAccessKey": "enw...",
                                              "SessionToken": "Fwo...",
                                              "Expiration": "2021-01-07T19:06:23+00:00"
                                            },
                                            "FederatedUser": {
                                              "FederatedUserId": "185...:sam",
                                              "Arn": "arn:aws:sts::185...:federated-user/sam"
                                            },
                                            "PackedPolicySize": 0
                                           }'
                                        );
                                      
                                      Copy

                                      To verify your configuration, call the SYSTEM$GET_PRIVATELINK function in your Snowflake account on AWS. This function uses the same argument values for 'aws_id' and 'federated_token' that were used to authorize your Snowflake account.

                                      SYSTEM$GET_PRIVATELINK returns Account is authorized for PrivateLink. for a successful authorization.

                                    3. Optional: If you need to disable AWS PrivateLink in your Snowflake account, call the SYSTEM$REVOKE_PRIVATELINK function by using the same argument values for 'aws_id' and 'federated_token'.

                                    To further harden your security posture, Snowflake recommends pinning private endpoints for your Snowflake account. For more information, see Fixação de pontos de extremidade de conectividade privada para tráfego de entrada.

                                    Configure your AWS VPC environment¶

                                    Atenção

                                    This section covers only the Snowflake-specific details for configuring your VPC environment.

                                    Snowflake isn’t responsible for the actual configuration of the required AWS VPC endpoints, security group rules, and Domain Name System (DNS) records. If you encounter issues with any of these configuration tasks, please contact AWS Support.

                                    Create and configure your AWS VPC endpoint¶

                                    To create and configure a VPC endpoint in your AWS VPC environment, complete the following steps:

                                    1. In your Snowflake account, use the ACCOUNTADMIN system role to call the SYSTEM$GET_PRIVATELINK_CONFIG function, and then record the privatelink-vpce-id value.

                                    2. In your AWS environment, create a VPC endpoint by using the privatelink-vpce-id value from the previous step.

                                      Nota

                                      If the Snowflake region of your VPC endpoint is different from the region of your AWS VPC, you must make two selections that enable cross-region connectivity. In the AWS VPC Console, select Enable Cross Region endpoint, and then select the primary region of the service in Service Settings » Service Region.

                                      Para instruções completas, consulte o procedimento passo a passo para configurar a conectividade entre regiões na documentação da AWS.

                                      For instructions that describe how to find the region name of your account, see Find the cloud-provider’s name of the region for your account.

                                    3. Em seu ambiente AWS, autorize um grupo de segurança de serviços que conecte a conexão de saída do Snowflake à porta 443 e 80 do VPCE CIDR (roteamento entre domínios sem classe).

                                    For more information, see the following topics in the AWS documentation:

                                    • Como trabalhar com VPCs e sub-redes

                                    • Pontos de extremidade VPC

                                    • Serviços de ponto de extremidade VPC (AWS PrivateLink)

                                    • Grupos de segurança para sua VPC

                                    Find the cloud-provider’s name of the region for your account¶

                                    Snowflake and the cloud provider that hosts your Snowflake account use similar, but different names for the region that hosts the Snowflake service. You can use system functions to find region names that you use to establish connectivity across regions. To determine the cloud-provider’s name of the region that hosts your Snowflake account, take the following steps:

                                    1. Run the CURRENT_REGION and SHOW REGIONS commands.

                                    2. In the output returned by SHOW REGIONS, find a row that shows a value in the snowflake_region column that matches the output returned by SELECT CURRENT REGION.

                                      The value in this row’s region column is the cloud-provider’s name of the region that hosts your Snowflake account.

                                    In the following example, us-west-2 is the cloud-provider’s name of the region that hosts the Snowflake account named AWS_US_WEST.

                                    SELECT CURRENT_REGION();
                                    
                                    Copy

                                    Output:

                                    +------------------+
                                    | CURRENT_REGION() |
                                    |------------------|
                                    | AWS_US_WEST_2    |
                                    +------------------+
                                    
                                    Copy
                                    SHOW REGIONS;
                                    
                                    Copy

                                    Output:

                                    +------------------+-------+-----------|-----------------+
                                    | snowflake_region | cloud | region    | display_name    |
                                    |------------------|-------|-----------|-----------------|
                                    | AWS_US_WEST_2    | aws   | us-west-2 | US West (Oregon)|
                                    +------------------+-------+-----------+-----------------+
                                    
                                    Copy

                                    Configuração de sua rede VPC¶

                                    To access Snowflake by using an AWS PrivateLink endpoint, you must create Canonical Name (CNAME) records in your DNS to resolve the appropriate endpoint values from the SYSTEM$GET_PRIVATELINK_CONFIG function to the DNS name of your VPC endpoint.

                                    Os valores a serem obtidos da saída de SYSTEM$GET_PRIVATELINK_CONFIG dependem de quais recursos do Snowflake você acessa usando conectividade privada. Para obter uma descrição dos valores possíveis, consulte Valores de retorno.

                                    Observe que os valores para regionless-snowsight-privatelink-url e snowsight-privatelink-url permitem o acesso a Snowsight e a Snowflake Marketplace usando conectividade privada. No entanto, há uma configuração adicional se você quiser habilitar redirecionamentos de URL. Para obter informações, consulte Snowsight e a conectividade privada.

                                    Para ajuda adicional com a configuração DNS, entre em contato com seu administrador interno AWS.

                                    Importante

                                    The structure of the Online Certificate Status Protocol (OCSP) cache server host name depends on the version of your installed clients, as described in Configure your Snowflake clients:

                                    • If you use the listed version or a later version, use the format shown in Configure your Snowflake clients, which enables better DNS resolution when you have multiple Snowflake accounts — for example, dev, test, and production — in the same region. When updating client drivers and using OCSP with PrivateLink, update the firewall rules to allow the OCSP host name.

                                    • If you use an earlier client version, then the OCSP cache server host name takes the form ocsp.region_id.privatelink.snowflakecomputing.com without an account identifier.

                                    • Your DNS record must resolve to private IP addresses within your VPC. If it resolves to public IP addresses, the record isn’t configured correctly.

                                    Criação de pontos de extremidade de interface VPC da AWS para o Amazon S3¶

                                    This step is required for Amazon S3 traffic from Snowflake clients to stay on the AWS backbone. The Snowflake clients (such as Snowflake CLI, SnowSQL, JDBC driver, and so on) require access to Amazon S3 to perform various runtime operations.

                                    If your AWS VPC network doesn’t allow access to the public internet, you can configure private connectivity to internal stages or more gateway endpoints to the Amazon S3 host names required by the Snowflake clients.

                                    There are three options to configure access to Amazon S3. The first two options avoid the public internet and the third option uses the public internet:

                                    • Configure um ponto de extremidade de interface VPC da AWS para estágios internos. Esta opção é recomendada.

                                    • Configure an Amazon S3 gateway endpoint. For more information, see the following Attention section.

                                    • Don’t configure an interface endpoint or a gateway endpoint. This results in access that uses the public internet.

                                    Atenção

                                    To prevent communications between an Amazon S3 bucket and an AWS VPC with Snowflake from using the public internet, you can set up an Amazon S3 gateway endpoint in the same AWS region as the Amazon S3 bucket. This prevents communications on the public internet because AWS PrivateLink only allows communications between VPCs, and the Amazon S3 bucket isn’t included in the VPC.

                                    You can configure the Amazon S3 gateway endpoint to limit access to specific users, Amazon S3 resources, routes, and subnets; however, Snowflake doesn’t require this configuration. For more information, see Gateway endpoints for Amazon S3.

                                    To limit Amazon S3 gateways to use only Amazon S3 resources for Snowflake, choose one of the following options:

                                    • Use the specific Amazon S3 host name addresses that is used by your Snowflake account in your AWS endpoint policies. For the complete list of host names that are used by your account, see SYSTEM$ALLOWLIST.

                                    • Use an Amazon S3 host name pattern that matches the Snowflake S3 host names in your AWS endpoint policies. With this option, there are two possible types of connections to Snowflake: VPC-to-VPC or On-Premises-to-VPC.

                                      Based on your connection type, complete the following instructions:

                                      VPC a VPC:

                                      Ensure that the Amazon S3 gateway endpoint exists. Optionally modify the Amazon S3 gateway endpoint policy to match the specific host name patterns that are shown in the following Amazon S3 Hostnames table.

                                      No local a VPC:

                                      Define a setup to include the Amazon S3 host name patterns in the firewall or proxy configuration if Amazon S3 traffic isn’t permitted on the public gateway.

                                    Se você não precisar que seus pontos de extremidade de gateway correspondam explicitamente aos buckets S3 gerenciados pelo Snowflake de sua conta, pode usar os padrões de nome de host do Amazon S3 mostrados na tabela a seguir para criar pontos de extremidade de gateway:

                                    Nomes de host do Amazon S3

                                    Notas

                                    Todas as regiões

                                    sfc-*-stage.s3.amazonaws.com:443

                                    None.

                                    Todas as regiões, exceto US East

                                    sfc-*-stage.s3-<id_região>.amazonaws.com:443

                                    The pattern uses a hyphen (-) before the region ID.

                                    sfc-*-stage.s3.<id_região>.amazonaws.com:443

                                    The pattern uses a period (.) before the region ID.

                                    For information about creating gateway endpoints, see Gateway VPC endpoints.

                                    Conexão com o Snowflake¶

                                    Before you connect to Snowflake, you can optionally use the Snowflake Connectivity Diagnostic tool (SnowCD) to evaluate the network connection with Snowflake and AWS PrivateLink.

                                    Para obter mais informações, consulte SnowCD e SYSTEM$ALLOWLIST_PRIVATELINK.

                                    Caso conectividade privada, conecte-se ao Snowflake com a URL da sua conta de conectividade privada.

                                    If you want to connect to Snowsight through AWS PrivateLink, follow the instructions in the Snowsight documentation.

                                    Block public access — Recommended¶

                                    After you test private connectivity to Snowflake by using AWS PrivateLink, you can optionally block public access to Snowflake. This means that users can access Snowflake only if their connection request originates from an IP address within a particular CIDR block range specified in a Snowflake network policy.

                                    To block public access by using a network policy:

                                    1. Create a new network policy or edit an existing network policy.

                                    2. Adicione o intervalo de blocos CIDR para sua organização.

                                    3. Ative a política de redes para sua conta.

                                    For more information, see Controle do tráfego de rede com políticas de rede.

                                    Configure your Snowflake clients¶

                                    As seções a seguir descrevem como configurar clientes Snowflake para casos de uso específicos.

                                    Como garantir o suporte dos clientes Snowflake ao servidor de cache OCSP¶

                                    The Snowflake OCSP cache server mitigates connectivity issues between Snowflake clients and the server. To enable your installed Snowflake clients to use the OCSP server cache, ensure that you use the following client versions:

                                    • Snowflake CLI 3.0.0 (or higher)

                                    • SnowSQL 1.1.57 (or higher)

                                    • Python Connector 1.8.2 (or higher)

                                    • JDBC Driver 3.8.3 (or higher)

                                    • ODBC Driver 2.19.3 (or higher)

                                    Nota

                                    The Snowflake OCSP cache server listens on port 80, which is why you were instructed in Create and configure your AWS VPC endpoint to configure your AWS PrivateLink VPCE security group to accept both port 80 and port 443, which is required for all other Snowflake traffic.

                                    Specify a host name for Snowflake clients¶

                                    Each Snowflake client requires a host name to connect to your Snowflake account.

                                    The host name is the same as the host name that you specified in the CNAME records in Configuração de sua rede VPC.

                                    This step isn’t applicable to access the Snowflake Marketplace.

                                    Por exemplo, para uma conta chamada xy12345:

                                    • If the account is in US West, the host name is xy12345.us-west-2.privatelink.snowflakecomputing.com.

                                    • If the account is in EU (Frankfurt), the host name is xy12345.eu-central-1.privatelink.snowflakecomputing.com.

                                    Importante

                                    The method for specifying the host name differs depending on the client:

                                    • For the Spark connector and the ODBC and JDBC drivers, specify the entire host name.

                                    • For all the other clients, don’t specify the entire host name. Instead, specify the account identifier with the privatelink segment, which is <account_identifier>.privatelink. Snowflake concatenates this name with snowflakecomputing.com to dynamically construct the host name.

                                    For more information about specifying the account name or host name for a Snowflake client, see the documentation for each client.

                                    Uso de SSO com o AWS PrivateLink¶

                                    O Snowflake oferece suporte ao uso de SSO com o AWS PrivateLink. Para obter mais informações, consulte:

                                    • SSO com conectividade privada

                                    • Aplicativos de parceiros

                                    Uso do redirecionamento do cliente com o AWS PrivateLink¶

                                    O Snowflake oferece suporte ao uso do redirecionamento do cliente com o AWS PrivateLink.

                                    Para obter mais informações, consulte Redirecionamento de conexões do cliente.

                                    Usando replicação e Tri-Secret Secure com conectividade privada¶

                                    O Snowflake oferece suporte à replicação de seus dados da conta de origem para a conta de destino, independentemente de você habilitar o Tri-Secret Secure ou este recurso na conta de destino.

                                    Solução de problemas¶

                                    Para solucionar problemas que você possa encontrar com o PrivateLink, consulte os seguintes artigos da Comunidade Snowflake:

                                    • Como recuperar um token de federação do AWS for PrivateLink Self-Service

                                    • FAQ: PrivateLink Self-Service com AWS

                                    • Solução de problemas: funções de auto-serviço Snowflake para AWS PrivateLink

                                    Esta página foi útil?

                                    Visite Snowflake
                                    Participe da conversa
                                    Como desenvolver com Snowflake
                                    Compartilhe seu feedback
                                    Leia as novidades em nosso blog
                                    Tenha sua própria certificação
                                    Aviso de privacidadeTermos do siteConfigurações de cookies© 2026 Snowflake, Inc. Todos os direitos reservados.
                                    1. AWS PrivateLink: Overview
                                    2. Enable AWS PrivateLink
                                    3. Configure your AWS VPC environment
                                    4. Conexão com o Snowflake
                                    5. Block public access — Recommended
                                    6. Configure your Snowflake clients
                                    7. Uso de SSO com o AWS PrivateLink
                                    8. Uso do redirecionamento do cliente com o AWS PrivateLink
                                    9. Usando replicação e Tri-Secret Secure com conectividade privada
                                    10. Solução de problemas
                                    1. SnowCD
                                    2. Impor acesso somente por privatelink
                                    Linguagem: Português
                                    • English
                                    • Français
                                    • Deutsch
                                    • 日本語
                                    • 한국어
                                    • Português