Oracle Cloud Infrastructure Object Storage support in Cloud Connector
Cloud Connector now supports routing requests to public Oracle Cloud Infrastructure Object Storage buckets using the S3 Compatibility API, with support for both path-style and virtual-hosted endpoint formats. This eliminates the need for separate origin-routing configuration when integrating with OCI.
Cloud Connector now supports public Oracle Cloud Infrastructure (OCI) Object Storage buckets. You can route matching requests to OCI without managing a separate origin-routing configuration.
OCI support uses the Amazon S3 Compatibility API. Both path-style and virtual-hosted endpoint formats are supported, including traditional oraclecloud.com and dedicated customer-oci.com path-style endpoints.
Public buckets only
Cloud Connector does not sign requests or provide OCI credentials. Your bucket must allow anonymous object reads. Private buckets and pre-authenticated request URLs are not supported.
API example
Set provider to oci_storage and provide a supported OCI hostname. The following rule uses a virtual-hosted endpoint:
{
"expression": "http.request.uri.path wildcard \"/assets/*\"",
"provider": "oci_storage",
"description": "Route assets to OCI Object Storage",
"enabled": true,
"parameters": {
"host": "<BUCKET_NAME>.vhcompat.objectstorage.<REGION>.oci.customer-oci.com"
}
}
For endpoint formats and bucket requirements, refer to Supported cloud providers in Cloud Connector.
Source: original entry ↗
More from Cloudflare
Follow Cloudflare to get its new changes in your feed and email digest.
Cloudflare API MCP server now serves Cloudflare skills
The Cloudflare API MCP server now integrates with the Skills over MCP extension, allowing MCP clients to discover and access Cloudflare skills. Users can add the MCP server endpoint to compatible MCP clients to access these skills.
WAF failed detections field now available in Rules
A new cf.appsec.request.failed_detections field lets you control how rules handle requests when security detections fail. This array of detection IDs covers content scanning, WAF attack scoring, attack signatures, leaked credentials, and AI-based PII/prompt injection/custom topic detection failures, and works across custom rules, rate limiting rules, and request header transform rules.
Markdown for Agents: More efficient in-process streaming conversion
Markdown for Agents now uses an in-process streaming engine at the edge to convert HTML, reducing overhead and memory use. The conversion limit increased from 2 MiB to 6 MiB, and token count headers are no longer generated.