Generate self-signed TLS credentials Stay organized with collections Save and categorize content based on your preferences.
This topic explains how to create self-signed TLS certificates for use in an environment configuration. This information is intended for trial or testing purposes only.
Warning: Self-signed certificates are not recommended for production. Only consider using them for development, trial, or testing purposes.The runtime ingress gateway (the gateway that handles API proxy traffic) requires a TLS certificate/key pair. For this quickstart installation, you can use self-signed credentials. In the following steps,openssl is used to generate the credentials.
- Execute the following command to create the certificate and key files. The certificate files will most likely have
.crtor.pemextensions and the key file will most likely have.key.Note:If you are usingapigeectlto install and manage Apigee hybrid, we recommend storing the certificate and key files in yourhybrid-files/certsdirectory.openssl req -nodes -new -x509 -keyout ./certs/keystore.key -out \ ./certs/keystore.pem -subj '/CN=mydomain.net' -days 3650
This command creates a self-signed certificate/key pair that you can use for the quickstart installation. The CN
mydomain.netcan be any value you wish for the self-signed credentials. - Check to make sure the files are in the
./certsdirectory:ls ./certskeystore.pem keystore.keyWhere
keystore.pemis the self-signed TLS certificate file andkeystore.keyis the key file.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-18 UTC.