[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-05 UTC。"],[],[],null,["# Bucket IP filtering\n\nThis page provides an overview of bucket IP filtering including its benefits,\nhow it works, supported locations, and limitations to consider.\n\nOverview\n--------\n\nCloud Storage offers bucket IP filtering to manage access to your data stored\nin buckets.\n\nBucket IP filtering is a network security mechanism that restricts access to a\nbucket based on the source IP address of the request and secures your data from\nunauthorized access.\n\nThe bucket IP filtering feature for Cloud Storage enables fine-grained\naccess control based on IPv4 or IPv6 address ranges or the Google Cloud\nVirtual Private Cloud. You can configure a list of IP ranges at the bucket level and all\nincoming requests to the bucket are restricted to the configured IP ranges and\nVPCs. This feature provides a way to secure sensitive data in\nCloud Storage buckets and prevent unauthorized access from specific IP\naddresses or VPCs.\n\nBenefits\n--------\n\nBucket IP filtering for Cloud Storage offers the following benefits:\n\n- **Fine-grained access control**: Restrict access to your\n Cloud Storage buckets based on the specific IP address (IPv4 or\n IPv6) or Google Cloud Virtual Private Cloud of the requester. Bucket IP filtering\n acts as a strong network-level security layer, preventing unauthorized\n access from unknown or untrusted sources.\n\n- **Enhanced security**: By limiting access to authorized IP addresses or\n VPCs, you can reduce the risk of unauthorized access, data breaches, and\n malicious activity.\n\n- **Flexible configuration**: You can configure and manage lists of IP ranges\n at the bucket level, tailoring the access control to your specific\n requirements.\n\nHow does it work?\n-----------------\n\nBucket IP filtering helps you control access to your buckets by defining rules that permit requests from specific IPv4 and IPv6 addresses. Incoming requests are evaluated against these rules to determine access permissions.\n\nA bucket IP filtering rule includes the following configurations:\n\n- **Public internet access**: You can define rules to manage requests\n originating from the public internet (outside any configured Virtual Private\n Cloud). These rules specify allowed IPv4 or IPv6 addresses using CIDR\n ranges, authorizing inbound traffic from those sources.\n\n- **Virtual private cloud (VPC) access**: For granular control over access\n from specific VPC networks, you can define rules for each network.\n These rules include allowed IP ranges, enabling precise management of access\n from your virtual network infrastructure.\n\n- **Service agent access**: Google Cloud service agents retain access to\n buckets, even with an active IP filter configuration. You can set up a\n configuration that allows Google Cloud services such as BigLake,\n Storage Insights, Vertex AI, and BigQuery to bypass the\n IP filter validation when accessing your buckets.\n\nLimitations\n-----------\n\nBucket IP filtering has the following limitations:\n\n- **Maximum number of IP CIDR blocks**: You can specify a maximum of 200 IP\n CIDR blocks across public and VPC networks in the IP\n filter rule for a bucket.\n\n- **Maximum number of VPC networks**: You can specify a maximum of 25\n VPC networks in the IP filter rules for a bucket.\n\n- **Regional endpoints** : [Regional endpoints](/storage/docs/regional-endpoints) work with IP filtering only\n when you use [Private Service Connect](/vpc/docs/private-service-connect).\n\n- **IPv6 support** : IP filtering with gRPC direct path is\n not supported on an IPv4 VM. When you use IP filtering with\n gRPC direct path, you must enable [IPv6 support](/vpc/docs/ipv6-support) on\n the VPC network.\n\n- **Blocked Google Cloud services** : Enabling IP filtering on\n Cloud Storage buckets restricts access for some Google Cloud services, regardless of\n whether they use a [service agent](/iam/docs/service-agents) to interact with Cloud Storage. For example, services such as\n BigQuery use Cloud Storage for importing and exporting\n data. To prevent service disruptions, we recommend not using IP filtering on Cloud Storage buckets accessed by the following services:\n\n - BigQuery interactions with Cloud Storage:\n - [Load data](/bigquery/docs/loading-data-cloud-storage-csv) from Cloud Storage to BigQuery.\n - [Export table data](/bigquery/docs/exporting-data) from BigQuery to Cloud Storage.\n - [Export query results](/bigquery/docs/writing-results#downloading-saving-results-console) from BigQuery to Cloud Storage.\n - Query from an [external Cloud Storage table](/bigquery/docs/external-data-cloud-storage#query_external_tables) with BigQuery.\n - If your [App Engine applications access data in Cloud Storage](/appengine/docs/standard/using-cloud-storage), we recommend [using App Engine through a Virtual Private Cloud](/appengine/docs/legacy/standard/python/connecting-vpc).\n - IP filtering doesn't support Cloud Shell.\n\nWhat's next\n-----------\n\n- [Create IP filtering rules on a bucket](/storage/docs/create-ip-filter).\n- [Update the IP filtering rules on a bucket](/storage/docs/update-ip-filter).\n- [List the IP filtering rules on a bucket](/storage/docs/list-ip-filter).\n- [Disable the IP filtering rules on a bucket](/storage/docs/disable-ip-filtering).\n- [Bypass the IP filtering rules on a bucket](/storage/docs/bypass-ip-filter).\n\nTry it for yourself\n-------------------\n\n\nIf you're new to Google Cloud, create an account to evaluate how\nCloud Storage performs in real-world\nscenarios. New customers also get $300 in free credits to run, test, and\ndeploy workloads.\n[Try Cloud Storage free](https://console.cloud.google.com/freetrial)"]]
