Keycloak 20.0.3 Infinispan not starting with correct transport stack for EC2

We migrate from Keycloak 17.0.1 to 20.0.3. We set keycloak variables in Dockerfile

ENV KC_CACHE=ispn
KC_CACHE_STACK=ec2
KC_CACHE_CONFIG_FILE=cache-ispn.xml

We have some extended caches defined in cache-ispn.xml.

Version 17.0.1 NATIVE_S3_PING is properly activated

[2023-03-20 04:22:31.589 +0000] [/] INFO [o.i.CLUSTER:460] (keycloak-cache-init) ISPN000078: Starting JGroups channel ISPN
[2023-03-20 04:22:32.098 +0000] [/] DEBUG [o.j.s.Configurator:136] (keycloak-cache-init) set property TCP.diagnostics_addr to default value /224.0.75.75
[2023-03-20 04:22:32.186 +0000] [/] DEBUG [o.j.p.TCP:142] (keycloak-cache-init) thread pool min/max/keep-alive: 0/200/60000 use_fork_join=false, internal pool: 0/4/30000 (1 cores available)
[2023-03-20 04:22:34.875 +0000] [/] INFO [o.j.a.s.NATIVE_S3_PING:131] (keycloak-cache-init) using Amazon S3 ping in region eu-west-1 with bucket ‘up-idp-test-ping’ and prefix ‘’
[2023-03-20 04:22:35.494 +0000] [/] INFO [o.j.a.s.NATIVE_S3_PING:131] (keycloak-cache-init) found bucket up-idp-test-ping

Version 20.0.3 UDP default transport is not supported on AWS

2023-03-23 06:28:31,485 INFO [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000128: Infinispan version: Infinispan ‘Triskaidekaphobia’ 13.0.10.Final
2023-03-23 06:28:32,168 INFO [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000078: Starting JGroups channel ISPN
2023-03-23 06:28:32,169 INFO [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000088: Unable to use any JGroups configuration mechanisms provided in properties {}. Using default JGroups configuration!
2023-03-23 06:28:32,655 DEBUG [org.jgroups.stack.Configurator] (keycloak-cache-init) set property UDP.diagnostics_addr to default value /224.0.75.75

I dont expect any changes in cache configuration : Configuring distributed caches - Keycloak

Consequence: we are not able to login to admin console anymore