diff --git a/spring-data-cassandra/src/test/resources/testcontainer-cassandra-v5.yaml b/spring-data-cassandra/src/test/resources/testcontainer-cassandra-v5.yaml
index adbfb6cbc..f41743d49 100644
--- a/spring-data-cassandra/src/test/resources/testcontainer-cassandra-v5.yaml
+++ b/spring-data-cassandra/src/test/resources/testcontainer-cassandra-v5.yaml
@@ -1553,7 +1553,7 @@ crypto_provider:
 # **NOTE** this default configuration is an insecure configuration. If you need to
 # enable server-to-server encryption generate server keystores (and truststores for mutual
 # authentication) per:
-# http://download.oracle.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide.html#CreateKeystore
+# https://download.oracle.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide.html#CreateKeystore
 # Then perform the following configuration changes:
 #
 # Step 1: Set internode_encryption=<dc|rack|all> and explicitly set optional=true. Restart all nodes
@@ -1611,7 +1611,7 @@ server_encryption_options:
 # **NOTE** this default configuration is an insecure configuration. If you need to
 # enable client-to-server encryption generate server keystores (and truststores for mutual
 # authentication) per:
-# http://download.oracle.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide.html#CreateKeystore
+# https://download.oracle.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide.html#CreateKeystore
 # Then perform the following configuration changes:
 #
 # Step 1: Set enabled=true and explicitly set optional=true. Restart all nodes
@@ -1689,7 +1689,7 @@ user_defined_functions_enabled: false
 #
 # It is strongly recommended to download and install Java Cryptography Extension (JCE)
 # Unlimited Strength Jurisdiction Policy Files for your version of the JDK.
-# (current link: http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html)
+# (current link: https://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html)
 #
 # Currently, only the following file types are supported for transparent data encryption, although
 # more are coming in future cassandra releases: commitlog, hints
@@ -1724,7 +1724,7 @@ transparent_data_encryption_options:
 # will use them to make sure other replicas also know about the deleted rows.
 # With workloads that generate a lot of tombstones, this can cause performance
 # problems and even exaust the server heap.
-# (http://www.datastax.com/dev/blog/cassandra-anti-patterns-queues-and-queue-like-datasets)
+# (https://www.datastax.com/dev/blog/cassandra-anti-patterns-queues-and-queue-like-datasets)
 # Adjust the thresholds here if you understand the dangers and want to
 # scan more tombstones anyway.  These thresholds may also be adjusted at runtime
 # using the StorageService mbean.