# Snowflake Create External Access Integration > Consult Snowflake CREATE EXTERNAL ACCESS INTEGRATION parameter reference before generating any CREATE EXTERNAL ACCESS INTEGRATION DDL. Use when this capability is needed. - Skill: `tomevault-io/snowflake-create-external-access-integration` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/snowflake-create-external-access-integration` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/snowflake-create-external-access-integration/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Integrations & APIs - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/snowflake-create-external-access-integration --- Before writing a CREATE EXTERNAL ACCESS INTEGRATION statement: 1. Read `references/parameters.md` to review all available parameters and their defaults. 2. For each parameter, decide whether the user's request implies a non-default value. 3. Include only the parameters that differ from the default or that the user explicitly requested. 4. Never use `CREATE OR REPLACE` — use `CREATE EXTERNAL ACCESS INTEGRATION` (IF NOT EXISTS is not supported for this object). 5. ALLOWED_NETWORK_RULES must reference EGRESS-mode network rules only; INGRESS or INTERNAL_STAGE rules will cause an error. 6. ALLOWED_AUTHENTICATION_SECRETS should be `none` unless the external endpoint requires authentication; when secrets are needed, list them explicitly rather than using `all`. 7. ENABLED = TRUE is the default; only include it explicitly if setting to FALSE or the user wants the integration disabled at creation time. --- > Source: [Gyrus-Dev/frosty](https://github.com/Gyrus-Dev/frosty) — distributed by [TomeVault](https://tomevault.io).