ClaudeCloudflare Developer Platform2026/06/05 0:00

Gateway, Cloudflare Mesh, Workers VPC - Filter Workers' public Internet traffic using Gateway policies

要点だけを先に読めるように短く再構成したセクションです。

元記事

Quick Digest

要約

要点だけを先に読めるように短く再構成したセクションです。

claudeja

Gateway, Cloudflare Mesh, Workers VPC - Filter Workers' public Internet traffic using Gateway policies の要約

Key Points

  • ポイント1: Changelog New updates and improvements at Cloudflare.
  • ポイント2: Subscribe to RSS View RSS feeds ← Back to all posts Filter Workers' public Internet traffic using Gateway policies Jun 05, 2026 Gateway Cloudflare Mesh Workers VPC Workers usin
  • ポイント3: This means your existing Zero Trust traffic policies — DNS, HTTP, Network, and egress — extend to traffic that originates from your Workers, the same way they do for WARP users tod

Summary

この記事は 2026-06-05 に公開された「Gateway, Cloudflare Mesh, Workers VPC - Filter Workers' public Internet traffic using Gateway policies」の内容を日本語で簡潔にまとめたものです。

Key Points

  • ポイント1: Changelog New updates and improvements at Cloudflare.
  • ポイント2: Subscribe to RSS View RSS feeds ← Back to all posts Filter Workers' public Internet traffic using Gateway policies Jun 05, 2026 Gateway Cloudflare Mesh Workers VPC Workers usin
  • ポイント3: This means your existing Zero Trust traffic policies — DNS, HTTP, Network, and egress — extend to traffic that originates from your Workers, the same way they do for WARP users tod

Full Translation

翻訳

原文の流れを保ったまま読める翻訳セクションです。

claudeja

Gateway, Cloudflare Mesh, Workers VPC - Filter Workers' public Internet traffic using Gateway policies(原文タイトル)

概要

公開日: 2026-06-05 翻訳生成に失敗したため、原文をそのまま保存しています。

原文

Changelog New updates and improvements at Cloudflare. Subscribe to RSS View RSS feeds ← Back to all posts Filter Workers' public Internet traffic using Gateway policies Jun 05, 2026 Gateway Cloudflare Mesh Workers VPC Workers using a VPC Network binding with network_id: "cf1:network" now egress to public Internet destinations through Cloudflare Gateway . This means your existing Zero Trust traffic policies — DNS, HTTP, Network, and egress — extend to traffic that originates from your Workers, the same way they do for WARP users today. Worker Calls env.EGRESS.fetch() VPC binding ↓ Cloudflare Mesh Bind via cf1:network ↓ Cloudflare Gateway Policies applied: DNS HTTP Network ↓ ↗ Public Internet Any public hostname or IP Gateway logs DNS HTTP Network What you get by default: Visibility. Worker egress shows up in Gateway DNS , HTTP , and Network logs alongside your other traffic, so you can audit what your Workers are calling and when. Enforcement. Any existing Gateway policy whose selectors match a Worker request will apply — including allow / block lists, DNS category filtering, and HTTP destination rules. If you have already blocked a category for your workforce, your Workers inherit that block. wrangler.jsonc wrangler.toml JSONC { " vpc_networks " : [ { " binding " : "EGRESS" , " network_id " : "cf1:network" , " remote " : true , }, ], } TOML [[ vpc_networks ]] binding = "EGRESS" network_id = "cf1:network" remote = true JavaScript TypeScript JavaScript // Egress to a public destination — subject to your Gateway policies and logged const response = await env . EGRESS . fetch ( "https://api.example.com/data" ) ; TypeScript // Egress to a public destination — subject to your Gateway policies and logged const response = await env . EGRESS . fetch ( "https://api.example.com/data" ) ; For configuration options, refer to VPC Networks . For policy authoring, refer to Cloudflare Gateway traffic policies . Resources API New to Cloudflare? Directory Sponsorships Open Source Cloudflare Research Support Help Center System Status Compliance GDPR Company cloudflare.com Our team Careers Tools Cloudflare Radar Cloudflare Labs Speed Test Is BGP Safe Yet? Certificate Transparency Community Community forum X Discord YouTube GitHub © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Trademark Cookie Settings Was this helpful? Yes No