Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Newly discovered resources include GCP VMs, Artifact Registry container images, Cloud Run functions and identities.
- GCP monitoring has an independent 30-day free trial starting when the GCP integration is created, not when you read the announcement.
- UAE, Bahrain, Taipei and New Zealand are excluded AWS Regions for creating the integration; this is not a GCP workload-location list.
- After the trial, equivalent GCP and AWS resources have the same monitoring price. The current general pricing page does not establish each GCP resource-unit mapping.
What is available, and who should evaluate it?
AWS confirmed on November 17, 2026 that Security Hub now extends to Google Cloud Platform (GCP), alongside AWS and existing Microsoft Azure support. Teams operating in both AWS and GCP can evaluate a shared view for prioritizing risks and coordinating responses across clouds.
The announced discovery scope includes GCP virtual machines, Google Artifact Registry (GAR) container images, Cloud Run functions and identities. It does not enumerate every resource subtype or all GCP locations. Check your intended resources against current official support information before defining the integration scope.
Finding a risk and verifying its repair are separate steps
Security Hub evaluates misconfigurations, internet exposure and software vulnerabilities. It offers posture checks against standards including CIS Google Cloud Platform Foundations, plus unified resource inventory, risk and exposure analysis. A posture check evaluates cloud-resource configuration against requirements; it does not certify the security of an entire business.
AWS and GCP findings can share a prioritized view, finding formats and automation workflows, with response through existing EventBridge integrations. The announcement does not establish automatic remediation for every finding or provide a complete GCP probe-port list or scanning cadence. An older AWS Network Scanning coverage table therefore does not establish this integration’s coverage.
For evaluation, keep separate evidence that a resource was discovered, that the relevant checks returned results, and that a repair was subsequently verified. A unified dashboard or an absence of findings alone does not prove that every resource was checked or every risk eliminated.
Check the AWS Region where the integration will be created
The announcement allows GCP integrations to be created from AWS Regions where Security Hub is available, except Middle East (UAE), Middle East (Bahrain), Asia Pacific (Taipei) and Asia Pacific (New Zealand). Check service availability in the intended AWS creation Region first, then these four exceptions.
This restriction concerns the AWS side of integration creation. It neither lists all supported GCP workload locations nor requires every user to be in the United States. Customer eligibility, processing requirements and GCP resource locations need separate checks. Changing a network exit cannot replace service eligibility or organizational data requirements.
The independent 30-day trial starts at GCP integration creation
GCP monitoring has an independent 30-day free trial that begins when you create the integration with Google Cloud Platform. Its start is not the announcement date, the first article view or the first resource-inventory view. The announcement does not establish that an existing AWS trial restarts.
Before creation, confirm the authorized owner, intended resources, target AWS Region and budget approval so preparation does not consume the trial period. Record the actual start and displayed trial status when creating it, and schedule a billing review before it ends. This guide did not access a cloud account or verify trial entitlement for any individual account.
Confirm equivalent resources before estimating ongoing costs
AWS says monitoring GCP resources costs the same as monitoring equivalent AWS resources after the trial. That relationship concerns monitoring prices. It does not make GCP compute, storage or networking free, or set one fixed total for a multicloud environment.
The current general Security Hub pricing page describes resource-unit and monitored-time billing, but its core conversion examples still mainly name AWS and Azure. The reviewed text does not establish an explicit mapping for each resource in the new native GCP integration. GCP prices for partner offerings on the same page are not native integration quotes.
Start a budget with intended VM, image, function and identity counts. Confirm current prices in the target Region, the corresponding GCP resource units, and charges for additional features or standalone products. Leave an unresolved conversion pending confirmation; applying AWS or Azure examples directly would produce an unjustifiably precise monthly estimate.
Use these four checks before connecting
First, define resources and the evaluation goal: configuration compliance, vulnerability management or a unified risk view. Second, check the AWS service Region, current GCP support, organizational access requirements and data-handling requirements read-only.
Third, consult the current official integration guide to identify identities and permissions before authorized staff follow a reviewed procedure. The announcement and linked overview do not establish a complete permission list, console fields or installation steps. This guide therefore provides no assembled IAM commands and ran no setup scripts.
Fourth, record the trial start, billing review, resource discovery and check results as separate acceptance items. Before enabling response automation later, review authorization and recovery for each action. Integration existence, risk detection and effective remediation each need their own evidence.
Sources
Frequently Asked Questions
Can I connect only for posture checks or vulnerability management?
Yes. The AWS announcement also permits independent GCP integrations through Security Hub CSPM for posture checks and Amazon Inspector for vulnerability management. Check the chosen product’s current integration and pricing terms; do not transfer bundled Security Hub features, prices or trial conditions to a standalone product.
Does connecting migrate GCP workloads to AWS?
The announcement describes cross-cloud discovery, security evaluation and response management; it does not announce workload migration. Keep monitoring integration and business migration separate. Confirm processing locations, collection scope and access permissions against current integration documentation and organizational requirements.