If you’re using ElastiCache Serverless for Valkey, you might notice that it doesn’t currently support reading the maxmemory-policy during runtime. For example, when using the INFO command on a serverless cache, you’ll only see a small set of data. In traditional node-based ElastiCache clusters, the INFO memory command shows the maxmemory_policy, making it easier for applications to detect and adapt. But with serverless caches, this isn’t possible, creating a compatibility issue, especially for applications that check the eviction policy before operating. To work around this, the best approach is to assume that serverless caches always use the “volatile-lru” policy.