Custom Storage Locations

CXone Cloud Storage is another storage option you can use with CXone. It is a good option if you want to save files to your own storage location instead of using CXone default storage for compliance reasons. Contact your CXone Account Representative to find out more about whether using custom storage is the right storage method for your organization.

Cloud Storage Services supports using your own Amazon Web Services (AWS) location for cloud storage. There are differences in feature availability when you use a custom storage location with Cloud Storage Services. These differences are shown in the following table.

Feature	CXone Cloud Storage	Custom Storage with AWS
File names include contact ID	Yes	No
TTL and other Life Cycle Management rules managed in Cloud Storage Services	Yes	No
Playback of files in CXone	Yes	Yes, exclusively
Use of Cloud Storage Services Secure External Access (SEA)	Yes	No
Stored files are encrypted	Yes	Yes

Before Setting Up Custom Storage

Before enabling custom storage, you need to set up and configure the location where you intend to save interactions. This can be an AWS S3 bucket.

If you're storing call recordings in custom storage, your custom S3 bucket must be configured with some required policies. The policies must allow CXone files to be stored and accessed in your custom bucket using Cloud Storage APIs. Contact your CXone Account Representative for more information about the required policies.

Do not modify the IAM bucket-level policy. Changes to the IAM policy may result in CXone failing to save files to your custom storage location.

Encryption of Stored Files

Files stored in custom storage locations are encrypted. This provides higher security. However, it means that you cannot access or play the files directly in the AWS environment. You must use CXone to access or play back the files.

File Names When Using Custom Storage

Custom storage and the default Cloud Storage locations results in different file names. Files stored in the default Cloud Storage location are named following a convention that uses identifying information such as the creation date, agent, contact ID, and so on.

Custom storage doesn't support this convention. This is because file names are encrypted as part of the process of moving to custom storage. Encrypted file names cannot be matched to specific contact IDs. They may not provide useful information related to the contents of the files. If you need file names that include the contact ID, consider using Secure External Access (SEA) instead of custom storage.

Key Facts about Custom Storage

• Custom storage will not allow you to: 

  • Save or remove playable files in your storage. Calls are encrypted, have a GUID for a file name, and can only be played using CXone. You will need to retrieve stored files back into CXone to play them.
  • Use your own long-term or glacier storage. That disables your ability to retrieve your files in CXone for playback.
  • Use SEA or APIs to pull unencrypted files off the CXone platform.

• You can set up custom storage in an AWS region that differs from your CXone hosted region. However, if you use FedRAMP, you should create your custom storage location in the same region as your CXone hosted region to comply with the regulatory requirements.

• You cannot use custom storage and a custom AWS KMS key together.

• When you use a custom storage location, you're responsible for the setup, maintenance, and operation of your AWS S3 bucket.
• All files created after you enable custom storage are stored in your custom location. If at any point you disable custom storage, all files created from that point on are stored in the default cloud location.
• Files cannot move between custom storage and Cloud Storage. This includes files in active and long-term Cloud Storage. When you change your storage location to custom storage or back to Cloud Storage, files stay in the location where they were saved. Because of this, you may have files stored in different locations.

• After you enable custom storage, you cannot modify the Life Cycle Management rules for CXoneCloud Storage unless you first disable custom storage. If you have files currently in active or long-term Cloud Storage, ensure that the rules you have in place to manage those files in the way you need them to before enabling custom storage.

• Historical files from the CXone file server or Cloud Storage cannot be moved to your custom storage location.