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
- AWS released the external_web_access parameter on August 19, 2026 at 23:00 UTC, allowing Bedrock Web Search to retrieve public webpage content directly.
- The parameter defaults to true, but the calling identity also needs bedrock-websearch:ExternalWebAccess. Both the parameter and IAM permission are required.
- When set to false, search uses only Amazon's web index and knowledge graph inside AWS, and request data stays within the AWS boundary.
- External access can improve freshness but expands data-disclosure, prompt-injection, source-change and audit risks. Do not retain it simply because the default is true.
- At release, support is limited to N. Virginia, Ohio and Oregon. Check prices separately against current Bedrock Web Search billing.
Who should check this change immediately
This update affects RAG, agent, platform-security and compliance teams using Bedrock Web Search to supply models with real-time information, especially systems whose queries may contain customer, internal-incident, unreleased-product, financial or medical context. The real decision is whether freshness justifies a wider data boundary.
The previous path used AWS-internal web indexes and knowledge graphs. external_web_access lets the same tool fetch public webpages directly. It changes retrieval paths and risk exposure, not the underlying model version.
Default true does not automatically grant permission
The announcement states that external_web_access defaults to true, but the requesting identity must still have bedrock-websearch:ExternalWebAccess. The parameter declares intent; IAM determines whether the identity may use the external path. Audit them separately.
Do not hide configuration problems behind broad administrator permissions. Grant the dedicated permission only to roles that genuinely need live external access. Sensitive workloads should explicitly set false and use policies, template checks and call logs to prevent default changes from reopening external access.
Choosing true or false
true suits public prices, sports results, news and new documentation, provided requests contain no sensitive information and the application can handle unavailable sources. false suits customer tickets, internal incidents, regulated data, unreleased code or workloads that must stay within AWS.
false still performs searches, but uses only Amazon's in-AWS web index and knowledge graph. It does not disable search completely or guarantee that the internal index has the latest content.
Four risks added by external access
Risks include request data leaving the AWS boundary, prompt injection in public webpages, content changes making answers difficult to reproduce, and domains, redirects and third-party resources expanding audit scope. Disabling the external path does not automatically eliminate errors or stale information in indexed content.
Applications still need source classification, separation of retrieved content from system instructions, retained citations, minimized sensitive fields and output review. Treat search results as untrusted input: they must not determine tool permissions or subsequent write operations.
Pre-release permission and data checklist
Check data sensitivity, the reason for true or false, least-privilege IAM, infrastructure-template parameters, nonsensitive path tests, identity and Region logs, fallback for abnormal sources and permission denials, and reviews of role and template drift, in that order.
If one application handles both public and sensitive requests, separate calling identities or service paths so the search types use different permissions and alerts. Select the path by data classification.
Regions, prices and failure classification
At launch, External Web Access is available only in N. Virginia, Ohio and Oregon. Do not infer availability in another Region just because the SDK exposes the parameter. Check pricing, cross-Region architecture, logs and organization policies as well.
AccessDenied points to IAM; parameter validation or unsupported Regions point to product configuration. DNS, TLS and connection timeouts may indicate the network path. Blaming every error on the proxy obscures permission boundaries.
Common mistakes and the limits of network troubleshooting
Common mistakes include interpreting default true as automatic public-web access for all accounts, believing false disables search entirely, equating the internal index with the latest public web, and changing only the console without fixing infrastructure configuration.
Only with explicit DNS, timeout, TLS or proxy-authentication evidence should you use the proxy connection troubleshooting checklist for the network layer. For request identity and parameters, see the AI API configuration guide. If you need stable access to AWS documentation, visit the PuppyIP website to learn about fixed egress. A proxy cannot grant IAM permissions or change data-processing boundaries.
Sources
Frequently Asked Questions
Does external_web_access default to true?
Yes, but the requesting identity must also have bedrock-websearch:ExternalWebAccess permission.
Can search still work with false?
Yes. It uses only Amazon's AWS-internal web index and knowledge graph, and request data does not leave the AWS boundary.
How should sensitive-data workloads be configured?
Explicitly set false, remove unnecessary dedicated IAM permissions, and continuously check parameters, identity, Region and logs.
Does disabling external access prevent all prompt injection?
No. All retrieved content remains untrusted input and needs source controls, instruction separation and output review.
Which Regions support External Web Access?
At release, N. Virginia, Ohio and Oregon.
Can changing proxies resolve AccessDenied?
Usually not. Check the requesting identity and bedrock-websearch:ExternalWebAccess permission first.