The following building blocks are needed to set up a single-cluster deployment.
The building blocks link to a blueprint with an example configuration. They are listed in the order in which they need to be installed.
| We provide these blueprints to show a minimal functionally complete example with a good baseline performance for regular installations. You would still need to adapt it to your environment and your organization’s standards and security best practices. |
Understanding the concepts laid out in the Concepts for single-cluster deployments guide.
Keycloak requires a low latency network connection for the synchronous replication of data by the database and Keycloak clustering.
A P50 round-trip latency of less than 5 ms is suggested and below 10 ms is strongly recommended, together with a reliable network between the zones to avoid unexpected problems with latency, throughput or connectivity.
Network latency and latency spikes amplify in the response time of the service and can lead to queued requests, timeouts, and failed requests. Networking problems can cause downtimes until the failure detection isolates problematic nodes.
Suggested setup: A Kubernetes cluster consisting of two or more AWS Availability Zones within the same AWS Region.
Not considered: Kubernetes clusters spread across multiple regions on the same or different continents, as it would increase the latency and the likelihood of network failures. Synchronous replication of databases as services with Aurora Regional Deployments on AWS is only available within the same region.