
PostgreSQL on SAP BTP instances created via BTP Cockpit or Cloud Foundry command line (CLI) are provisioned by default with private endpoints that are only accessible from BTP applications. In certain scenarios where PostgreSQL instances needs to be accessible from other landscapes and environments (e.g. from external sources), customers may now leverage access via public IPs feature. Check official product documentation regarding the supported regions.
Check below how to create an instance accessible via public IPs
To make your instance accessible publicly you must enable two additional parameters in your instances on SAP BTP Cockpit or via Cloud Foundry CLI operations at the time of instance creation.
Prerequisites/considerations:
How to create a new publicly accessible instance
Access BTP Cockpit > select your Global Account > Create a new instance
In the parameter tab within the allow access section add the IP addresses that should have access to your PostgreSQL, if you have multiple IP addresses use comma to separate these. Please consider that each time you provide a new IP/domain, it will overwrite the existing settings, so always provide the complete list of IPs if you update 'allow_access' parameter.
Additionally tick the ‘Public Access’ checkbox, which ensures your instance is now accessible publicly to the allow listed IP addresses you entered above.
Your PostgreSQL instance is now accessible externally via Public IP.
Please refer to our official product documentation at SAP Help Portal for more information on PostgreSQL.
Check out other interesting blogs on PostgreSQL:
Thank you for reading!
SAP BTP Backing Services – Product Management
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
16 | |
12 | |
10 | |
9 | |
8 | |
8 | |
7 | |
6 | |
6 | |
6 |