See below for creating a CloudKey for an EDB PostgreSQL Database Server.
Only keys created in the Cryptographic Security Platform Vault for Databases are supported.
To create a CloudKey
Log in to the Vault web GUI using an account with Cloud Admin privileges.
In the top menu bar, click CloudKeys.
Click the CloudKeys tab and select the key set with which the CloudKey will be associated.
Select Actions > Create CloudKey.
On the Details tab of the Create CloudKey dialog box, enter the following:
- Name—Enter the name for the CloudKey
- Description—Enter the optional description for the CloudKey
- Cipher—Select AES-256
- Click Continue.
On the Schedule tab, determine the rotation schedule for the CloudKey. This can be one of the following:
- Inherit from Key Set—The CloudKey will use the Key Set's default schedule. If the Key Set schedule changes after you create the CloudKey, the CloudKey schedule will not update.
- Never—The CloudKey will never be rotated.
- Once a year—The CloudKey will be rotated once a year.
- Every 6 months—The CloudKey will rotate every 6 months.
- Every 30 days—The CloudKey will rotate every 30 days.
- Other—The CloudKey will be rotated at the interval you select.
Choose when this CloudKey version should expire. The per-version expiration can be one of the following:
- Never—The CloudKey version will never expire.
- Fixed Date—All CloudKey versions will expire on the date that you set.
- Relative Expiry—Each CloudKey version will expire after the number of days that you set.
Choose when the CloudKey should expire. This can be Never, or you can choose a specific date.
If you selected an expiration date, choose the Expire Action to define what happens to the CloudKey when it expires. This can be one of the following:
Disable—The key will remain in the cloud, but is disabled and cannot be used by any applications.
Delete—The key is disabled in the cloud and cannot be used by any applications. You can set the date for permanent deletion.
- Click Apply.