- Who is this for?
- Mobile application and backend teams.
- Before you start
- An owned staging environment, sample user journey and access model.
1. Clients connect only to the API
Do not embed permanent MySQL / PostgreSQL passwords in Flutter, React Native or web clients. App packages and web code can be inspected. The API verifies sessions and executes authorized queries server-side. Exposing the SQL port to the internet is not inherently required.
2. Authorize access to each record
A valid session is not permission to every record. Evaluate organization membership, role and ownership in the relevant query. Do not trust project_id or organization_id from a client without checking it. Individual reads, updates and deletes need the same boundary as lists.
3. Limit the SQL account
Grant only the permissions required by application queries. Plan schema migrations and management work under separate operator permissions. Routine application connections do not need a database superuser account. Prepare a credential rotation plan that considers running connections.
4. Verify the TLS certificate
Encryption and server identity verification are different controls. PostgreSQL libpq verify-full checks the certificate trust chain and host name. Configure trusted CA information according to provider instructions. Driver options vary; do not hide connection errors by disabling TLS verification.
postgresql://app_user:<secret>@db.internal:5432/app?sslmode=verify-full
# Illustrative only. Real host, secret and CA information comes from your provider.5. Size connection pools deliberately
Use pooling rather than opening a connection for each HTTP request. Consider web processes and worker counts when calculating limits. Monitor connection timeouts, idle connections and query durations. Closing unused connections also matters during releases.
6. Check backups and restoration separately
Creating a backup file does not prove restoration works. Define retention, access and recovery steps. Test restoration in a separate environment and check application consistency. Uygulama Cloud does not currently offer customer database backup or restore services.
7. Investigate connection failures safely
Inspect network access, DNS, ports, permissions and TLS separately. Keep passwords and full connection strings out of issue reports. A resource definition cannot supply working database credentials when no live provider is connected.
7. Check network, roles and tenants together
Private networking does not itself isolate user records. Scope queries to the authenticated tenant and give the application role only required privileges. Keep migration and administration roles out of request handling. Test RLS using the actual app role because stronger roles may bypass policies.
Check that connection secrets are absent from logs, errors and operator screens. Test what happens to pooled connections when credentials rotate.
8. Test with two users
Create distinct records for A and B. Use A’s session against B’s identifiers for lists, details, updates, deletion and files. Protecting only one endpoint is insufficient. Reject access without leaking data or applying a business effect.
- Scope lists and searches.
- Avoid administrator app roles.
- Separate backup permissions.
- Prevent restored tests from sending real notifications.
A session + B record → no data / permission denied
A session + A record → permitted action
No session → authentication rejectedAction summary
- Check network, roles and tenants together
- Test with two users
Common questions
Does this enable live Uygulama Cloud resources?
No. Customer provisioning is closed; adapt the architectural examples to your environment.
What counts as validation?
Verified data, permissions and failure cases for your workload, rather than one successful screen or a backup file.
Sources and scope
Technical references are listed below. Examples illustrate implementation in your own environment; they are not customer benchmarks or claims of live Uygulama Cloud services. Check the current provider documentation before applying settings.
Sources checked: