Build Connector Hub service-to-service configurations for routing data between OCI services.
Last verified: May 2026
Build Connector Hub service-to-service configurations for routing data between Logging, Streaming, Functions, and Object Storage.
Required Fields
compartmentIddisplayNamesource.kindtarget.kindisEnabledOutput will appear here...Build Connector Hub service-to-service configurations for routing data between OCI services. This tool helps OCI engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
No. This tool runs entirely in your browser and generates configuration JSON that you can copy and paste into your infrastructure-as-code templates, CLI commands, or cloud console. It never connects to any cloud account or sends data externally.
The tool produces syntactically valid configurations based on current OCI service specifications. Always review generated configs against your organization security policies and test in a non-production environment before deploying.
Your team needs to forward all OCI Audit logs to Object Storage for long-term compliance archive. Without Service Connector Hub, you'd write a Function that polls audit logs and uploads to Object Storage — code to maintain, schedule, monitor. The builder generates an SCH connector: source = Logging (Audit log group), target = Object Storage (compliance bucket), no transformation needed. Total operational overhead: 0. Logs flow continuously to Object Storage with built-in reliability and retry. Annual engineering hours saved: ~20.
The builder constructs OCI Service Connector Hub configurations: connector resource (compartment, name, source service: Logging / Streaming / Monitoring / Notifications / Queue, source-specific config: log group OCIDs / stream OCIDs / metric definitions, target service: Logging / Streaming / Notifications / Functions / Object Storage / Monitoring, target-specific config, optional task: filter expression for selective forwarding, optional Function for transformation). Output is generated as oci sch service-connector commands and Terraform oci_sch_service_connector resources.
Service Connector Hub is the FREE 'glue' between OCI services — eliminates the need for custom Lambda/Function code that just forwards data. Want to send all CloudWatch-equivalent logs to Object Storage? Use SCH instead of writing a forwarder. Want to fan out streaming events to multiple targets? SCH.
SCH supports filtering and basic transformation. Don't write a Function just to drop fields or rename them — define the transformation in the SCH connector. The transformation language is limited but covers most basic ETL needs.
For complex transformations beyond SCH's capabilities, fall back to Functions. The pattern: SCH delivers events to Function → Function transforms → output to next destination. This is more code than pure SCH but dramatically less than building everything custom.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.