---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Configure the AES 128-bit encryption key

# Configure the AES 128-bit encryption key {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
After you configure the HTTPS certificate through the Edge Encryption proxy installer, configure
the AES 128-bit encryption key to encrypt your data.

## Before you begin

Role required: admin

## About this task

The encryption key is either a plain text file inside the /keys directory or a secret key inside a keystore. If you use a keystore for your AES 128-bit and AES 256-bit encryption keys, they must both use the same keystore.

If you are updating an SSL certificate on an Edge proxy server, see
[Update SSL
certificate](https://www.servicenow.com/docs/Dm4JxRtSXiWlyO1amXFGaQ "When updating an SSL certificate on an Edge proxy server, you must delete the old one.").

## Procedure

1. Select the encryption key location.

   | Option | Description |
   | File Store | Use a file to store a single encryption key. You can use an existing file in the /keys directory, or you can generate a new file. To generate a new file, enter an alias and click Generate. A file containing an encryption key is created. Note: This choice designates both the storage location and the encryption key. If you select File Store, click Next and go to [step 5](https://www.servicenow.com/docs/KggWLJlLnz6oxDqnvxYO~Q#configure-128-key__configure-key-on-instance). |
   | Create New Java KeyStore | Create a keystore to store the encryption key. |
   | Java KeyStore File | Store the encryption key in an existing Java KeyStore file. |
   |-|-|

   {#configure-128-key__choicetable_hj2_b1p_gfb}
2. Click Next.
3. Select or create the encryption key.

   | Option | Description |
   | New Key | Create an encryption key and alias. Note: You must use lowercase letters and numbers for the alias name (key name, key alias), per Java KeyStore requirements. To find out more about the keytool utility, see the [Java SE Documentation](http://docs.oracle.com/javase/6/docs/technotes/tools/windows/keytool.html). |
   | Use Existing Key | Use an existing encryption key in the selected keystore. |
   | Import Existing Key | Import an encryption key from a different keystore. |
   |-|-|

   {#configure-128-key__choicetable_trt_g1p_gfb}
4. Click Next.
5. Configure the key on the instance according to the requirements defined in your installer.  
   To configure the key on the instance, navigate to the instance and define a default key. See [Configure encryption keys on the instance](https://www.servicenow.com/docs/iQKgZCBBJotswQSmDqsCJQ "Edge Encryption provides the tools to manage encryption keys without taking the proxy offline."). Ensure that the key alias, size, and type match the requirements defined in the installer.Figure 1. Default key requirements {#configure-128-key__configure-key-on-instance}
{#configure-128-key__configure-key-on-instance}
6. Once the key is configured on the instance, return to the installer and click Next.
**Previous topic:** [Configure the HTTPS certificate](https://www.servicenow.com/docs/RKLz_DmOlj1Y0_xx7zCF8g "To enable clients to connect to the Edge Encryption proxy server using a secure SSL connection, import the HTTPS certificate to the proxy server.")  
**Next topic:** [Configure the AES 256-bit encryption key](https://www.servicenow.com/docs/xWxOnaZG7H_tk8j24dkc3A "After you configure the AES 128-bit key through the Edge proxy installer, you can optionally configure an AES 256-bit encryption key to encrypt your data.")