# Securely connecting Celigo to a private resource (in a private subnet)

**URL:** https://connective.celigo.com/t/securely-connecting-celigo-to-a-private-resource-in-a-private-subnet/4057
**Category:** Integrator.io
**Tags:** builders-hub
**Created:** [March 31, 2025, 6:50pm UTC](https://connective.celigo.com/t/securely-connecting-celigo-to-a-private-resource-in-a-private-subnet/4057 "2025-03-31T18:50:57Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![youssefzouhairi](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/youssefzouhairi/32/7087_2.png) [@youssefzouhairi](https://connective.celigo.com/u/youssefzouhairi)
#### Post date: [March 31, 2025, 6:50pm UTC](https://connective.celigo.com/t/securely-connecting-celigo-to-a-private-resource-in-a-private-subnet/4057/1 "2025-03-31T18:50:57Z")

</div>

Integrating cloud-based services with private resources can be challenging, especially when security is a top priority. [This Builder’s Hub article explains how to securely connect the Celigo integration platform as a service (iPaaS) to a private resource in a private subnet](https://www.celigo.com/blog/securely-connecting-celigo-to-a-private-resource-in-a-private-subnet/?-builders-hub). In this example we’ll use a PostgreSQL database hosted on AWS, a bastion host and SSH tunneling to enable the Celigo on-premises agent to communicate with isolated private resources without compromising security.