Deploy the PostgreSQL service

complete the following steps to deploy the postgresql service in {{ch}} log in to the {{ch}} under dual control using your administrator identities select the service you intend to deploy and select \[ deploy ] configure the following service setup settings service name the name of the application leave as default service category the category the service falls under leave as default select \[ next ] configure the following access control settings authorized resources the role you are logged in with has access to the service by default add additional resources optional select \[ next ] configure the authentication settings to determine how users will authenticate to access encrypted files the two options are kerberos or local authentication local authentication uses local windows accounts to manage access to encrypted files users will be authenticated using their local windows credentials kerberos authentication uses windows active directory to manage access to encrypted files users will be authenticated using their domain credentials active directory configuration is required for kerberos authentication go to identity & access management , then select the active directory tab to set this up select local or kerberos authentication and select \[ next ] configure the path rules select \[ add path rule ] enter role or group names from active directory for broad access enter active directory or individual usernames to grant access choose basic setup to encrypt a specific directory and file type, or select advanced setup to use wildcards like for subdirectories and for pattern matching select \[ add ] for the postgresql integration, you must specify a file matching pattern the path to the data directory of your postgresql installation the example below will recursively encrypt all files in the c \postgresql\data\ directory example c \postgresql\data based on the postgresql directory structure, the following folders within the data directory relate to database instances base this is the primary directory containing all database instances within base each database has its own subdirectory named with its object id (oid) for example, if a database had oid 16387, its files would be in data\base\16387\ global contains cluster wide tables like pg database and authentication information pg wal (or pg xlog in older versions) contains write ahead log files essential for database recovery pg tblspc contains symbolic links to any tablespaces defined outside the main data directory the individual database data is primarily in the numbered subdirectories within base , such as c \postgresql\data\base\16387\ if you're considering encryption strategies, understanding this structure helps you decide whether to encrypt the entire data directory or target specific database subdirectories within base select \[ deploy ]