|sf-intelligence|의 개요¶

Create a Snowflake Intelligence object¶

You can either use the Snowflake Intelligence UI or SQL to create a Snowflake Intelligence object.

Snowflake Intelligence UISQL

Snowflake automatically creates the Snowflake Intelligence object when you modify the Snowflake Intelligence settings for the first time. When created using the UI, the Snowflake Intelligence object is named SNOWFLAKE_INTELLIGENCE_OBJECT_DEFAULT. You can’t specify a different name.

1. Snowsight 에 로그인합니다.

2. 탐색 메뉴에서 AI & ML » Agents 를 선택합니다.

3. Select the Snowflake Intelligence tab.

4. Select Open settings. The Snowflake Intelligence object is created automatically if it doesn’t already exist. You can then add agents to the object.

Add agents¶

The Snowflake Intelligence object is an account-level object that contains a list of agents. You can add or remove agents from this object to create a curated list of agents for your users. For more information about adding or removing agents, see Configure the visibility of agents in Snowflake Intelligence.

Grant Snowflake Intelligence privileges¶

The following privileges control access to Snowflake Intelligence objects:

• CREATE SNOWFLAKE INTELLIGENCE ON ACCOUNT: Account-level privilege that allows creating a Snowflake Intelligence object. This privilege is granted to ACCOUNTADMIN by default.

  To grant this privilege to another role, run the following command:

  GRANT CREATE SNOWFLAKE INTELLIGENCE ON ACCOUNT TO ROLE <role_name>;
  

  Copy

• USAGE: Object-level privilege that allows users to view the list of agents added to the Snowflake Intelligence object and see configuration values.

  To grant this privilege, run the following command:

  GRANT USAGE ON SNOWFLAKE INTELLIGENCE SNOWFLAKE_INTELLIGENCE_OBJECT_DEFAULT TO ROLE <role_name>;
  

  Copy

• ALTER: Object-level privilege that allows users to add or remove agents from the Snowflake Intelligence object and change configuration values. Account administrators have this privilege by default.

  To grant this privilege, run the following command:

  GRANT MODIFY ON SNOWFLAKE INTELLIGENCE SNOWFLAKE_INTELLIGENCE_OBJECT_DEFAULT TO ROLE <role_name>;
  

  Copy

To make the Snowflake Intelligence object visible to all of your users, grant USAGE privileges on the object to the PUBLIC role:

GRANT USAGE ON SNOWFLAKE INTELLIGENCE SNOWFLAKE_INTELLIGENCE_OBJECT_DEFAULT TO ROLE PUBLIC;

As an ADMIN, you also have ALTER privileges on the Snowflake Intelligence object. This allows you to add or remove agents from the object to create a curated list of agents for your users.

To set up Snowflake Intelligence for your users, you must configure agent privileges. For information about the privileges required for agents, see 액세스 제어 요구 사항.

Managing agents with the Snowflake Intelligence object¶

To add agents to the Snowflake Intelligence object, use the following command:

ALTER SNOWFLAKE INTELLIGENCE SNOWFLAKE_INTELLIGENCE_OBJECT_DEFAULT ADD AGENT <db.schema.agent_name>;

To remove agents from the Snowflake Intelligence object, use the following command:

ALTER SNOWFLAKE INTELLIGENCE SNOWFLAKE_INTELLIGENCE_OBJECT_DEFAULT DROP AGENT <db.schema.agent_name>;

Agent visibility logic¶

Snowflake Intelligence uses the following logic to determine which agents are visible to users:

1. If the Snowflake Intelligence object exists and contains one or more agents, users see the individual agents from this curated list that they have access.

2. If the Snowflake Intelligence object exists but contains zero agents AND the SNOWFLAKE_INTELLIGENCE.AGENTS schema exists with one or more agents, users see agents from the SNOWFLAKE_INTELLIGENCE.AGENTS schema. This ensures that Snowflake Intelligence doesn’t break if you haven’t migrated your agents yet.

3. If the Snowflake Intelligence object doesn’t exist or contains zero agents AND the SNOWFLAKE_INTELLIGENCE.AGENTS schema doesn’t exist or contains zero agents, users see all agents that they have access to in the account.

Migrating from the deprecated SNOWFLAKE_INTELLIGENCE.AGENTS schema¶

If you’re using the SNOWFLAKE_INTELLIGENCE.AGENTS schema, your agents will continue to work. However, migrating to the Snowflake Intelligence object provides the following benefits:

• Flexibility: Create and manage agents anywhere in your account without needing to centralize them in a single schema.

• Improved permission management: Separate the ability to create agents from the ability to publish them in Snowflake Intelligence.

• Avoid naming conflicts: Eliminate potential conflicts with the SNOWFLAKE_INTELLIGENCE.AGENTS schema name.

• Easier agent visibility management: Use a single object to control which agents appear to all users.

Make sure you’ve created a Snowflake Intelligence object before you migrate your agents. For information about creating a Snowflake Intelligence object, see Snowflake Intelligence 설정하기.

After you’ve created an object, use the following code to add an agent to the Snowflake Intelligence object:

ALTER SNOWFLAKE INTELLIGENCE SNOWFLAKE_INTELLIGENCE_OBJECT_DEFAULT ADD AGENT SNOWFLAKE_INTELLIGENCE.AGENTS.<agent_name>;

Copy

You can rename or drop the SNOWFLAKE_INTELLIGENCE database or AGENTS schema after the migration. For more information, see ALTER SCHEMA.

전제 조건¶

비공개 연결을 사용하여 |sf-intelligence|에 연결하기 전에 다음 전제 조건을 완료합니다.

• /user-guide/admin-security-privatelink`의 지침을 따라 AWS PrivateLink를 설정하거나 :doc:/user-guide/privatelink-azure`의 지침을 따라 Azure Private Link를 설정하세요.

• ACCOUNTADMIN 시스템 역할을 통해 SYSTEM$GET_PRIVATELINK_CONFIG 함수를 호출하여 :code: `regionless-snowsight-privatelink-url`이 제공되도록 보장합니다.

|sf-intelligence|에 연결¶

Snowflake Intelligence가 하위 도메인을 사용하도록 DNS를 구성하여 |sf-intelligence|에 연결합니다.

• VPC 또는 VNET 엔드포인트의 DNS 이름에 다음 URL을 매핑하는 비공개 DNS 존 :code:`privatelink.snowflakecomputing.com`에 CNAME 레코드를 생성합니다.

  si-<org-acct>.privatelink.snowflakecomputing.com
  

  Copy

구성이 완료되면 네트워크 내 사용자는 다음 URL로 이동하여 |sf-intelligence|에 액세스할 수 있습니다.

https://si-<org-acct>.privatelink.snowflakecomputing.com

Copy

이 연결은 비공개 연결을 통해 안전하게 라우팅됩니다.

비공개 연결을 사용한 사용자 인증¶

비공개 연결을 사용하여 |sf-intelligence|에 액세스하는 사용자는 표준 Snowflake 인증 프로세스를 사용하며, 이를 위해서는 로그인 페이지에서 계정 식별자, 사용자 이름, 비밀번호를 제공해야 합니다.