docs/documentation/platform/pki/applications/certificate-syncs/f5-big-ip.mdx
Deploy certificates to F5 BIG-IP appliances. Certificates can be automatically attached to Client SSL or Server SSL profiles, so the BIG-IP starts serving them right after each sync.
<Info> Certificate Syncs are configured per Application. First select which certificates to sync, then configure the F5 BIG-IP destination. </Info> 2. Select the **F5 BIG-IP** option.
3. Configure the **Destination**:
- **F5 BIG-IP Connection**: The F5 BIG-IP Connection to authenticate with.
- **Partition** (Optional): The F5 partition where certificates will be stored. Defaults to `Common`.
- **Profile Binding** (Optional): Attach each certificate to a Client SSL or Server SSL profile so the BIG-IP starts using it right away. Choose **None** to just upload certificates without attaching them.
- **Profile Name** (Conditional): Required when **Profile Binding** is set. The name of the SSL profile inside the partition.
- **Create profile if missing** (Optional): Create the SSL profile on the BIG-IP if it doesn't exist yet.
- **Parent Profile** (Optional): The existing F5 profile to copy settings from when creating the new one. Defaults to `/Common/clientssl` (Client SSL) or `/Common/serverssl` (Server SSL).
4. Configure the **Sync Options**:
- **Enable Removal of Expired/Revoked Certificates**: Remove certificates from the BIG-IP when they're no longer active in Infisical.
- **Include Root CA in Certificate Chain**: Include the root CA in the chain uploaded to the BIG-IP. Most setups don't need the root, since clients already trust it.
- **Preserve Certificate on Renewal**: When on, renewed certificates keep the same name on the BIG-IP, so any profile or virtual server using them keeps working without changes. When off, the renewed certificate is uploaded with a new name and the original stays on the BIG-IP.
- **Certificate Name Schema** (Optional): Customize the name used on the BIG-IP. Must include `{{certificateId}}`. Defaults to `Infisical-{{certificateId}}`. The certificate chain follows the same name with `-chain` added.
- **Auto-Sync Enabled**: Automatically sync certificates when changes occur (including auto-renewals).
5. Configure the **Details**:
- **Name**: The name of your sync.
- **Description**: Optional description.
6. Select which certificates should be synced.
7. Review and click **Create Sync**.
</Tab>
<Tab title="API">
To create an **F5 BIG-IP Certificate Sync**, make an API request to the [Create F5 BIG-IP PKI Sync](/api-reference/endpoints/pki/syncs/f5-big-ip/create) endpoint.
### Sample request
<Note>
You can optionally specify `certificateIds` during sync creation to immediately add certificates to the sync.
If not provided, you can add certificates later using the certificate management endpoints.
</Note>
```bash Request
curl --request POST \
--url https://app.infisical.com/api/v1/cert-manager/syncs/f5-big-ip \
--header 'Authorization: Bearer <access-token>' \
--header 'Content-Type: application/json' \
--data '{
"name": "my-f5-big-ip-cert-sync",
"applicationId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"description": "an example certificate sync",
"connectionId": "550e8400-e29b-41d4-a716-446655440000",
"destination": "f5-big-ip",
"isAutoSyncEnabled": true,
"certificateIds": [
"550e8400-e29b-41d4-a716-446655440000"
],
"syncOptions": {
"canRemoveCertificates": true,
"includeRootCa": false,
"preserveItemOnRenewal": true,
"certificateNameSchema": "myapp-{{certificateId}}"
},
"destinationConfig": {
"partition": "Common",
"profileType": "client-ssl",
"profileName": "clientssl-prod",
"createProfileIfMissing": true,
"parentProfile": "/Common/clientssl"
}
}'
```
### Sample response
```json Response
{
"pkiSync": {
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"name": "my-f5-big-ip-cert-sync",
"description": "an example certificate sync",
"destination": "f5-big-ip",
"isAutoSyncEnabled": true,
"destinationConfig": {
"partition": "Common",
"profileType": "client-ssl",
"profileName": "clientssl-prod",
"createProfileIfMissing": true,
"parentProfile": "/Common/clientssl"
},
"syncOptions": {
"canRemoveCertificates": true,
"includeRootCa": false,
"preserveItemOnRenewal": true,
"certificateNameSchema": "myapp-{{certificateId}}"
},
"applicationId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"connectionId": "550e8400-e29b-41d4-a716-446655440000",
"createdAt": "2026-05-01T00:00:00.000Z",
"updatedAt": "2026-05-01T00:00:00.000Z"
}
}
```
</Tab>
The F5 BIG-IP Certificate Sync provides:
When a certificate is renewed in Infisical, the behavior depends on the Preserve Certificate on Renewal option:
You can manually trigger a sync to F5 BIG-IP. This is useful for:
To manually sync, use the Sync Certificates API endpoint or the manual sync option in the Infisical UI.
Server SSL profiles: only one certificate at a time. Adding a second certificate replaces the first one on the profile. </Accordion>
<Accordion title="Will Infisical overwrite other certificates already attached to the profile?"> On Client SSL profiles, no, as long as the new and existing certificates are different algorithm types (RSA / ECDSA / DSA). Each type gets its own slot, and certificates added by other tools or by hand stay untouched. On Server SSL profiles, the profile holds a single certificate, so syncing a new one replaces what was there. </Accordion>