File size: 2,257 Bytes
d0954af
 
a052b68
 
d0954af
a052b68
d0954af
a052b68
 
 
 
 
 
 
d0954af
a052b68
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
d0954af
a052b68
 
 
 
 
 
 
 
 
d0954af
a052b68
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
TITLE: Halyard Cloud limitations
URL:
============================================================

Halyard Cloud limitations

This page describes the limitations in Halyard Cloud. Limitations are organized by category and include workarounds where available.

Limited regions and instance types : May not have optimal placement Workaround : Request additional regions via support Status : Ongoing expansion

Workaround : Request additional regions via support

Status : Ongoing expansion

Bring your own account (BYOA) is not available : Halyard-managed AWS accounts only Workaround : Use VPC peering for connectivity to your infrastructure

Workaround : Use VPC peering for connectivity to your infrastructure

Single cloud provider : AWS only Timeline : Multi-cloud support planned for 2026

Timeline : Multi-cloud support planned for 2026

The following limits are enforced to ensure stability and optimal performance:

Rule

Reason

Example

Cluster size ÷ zone count = whole number

Even distribution across zones

6 nodes ÷ 3 zones = 2 nodes/zone ✅

Cluster size ÷ replication factor = whole number

Balanced replication

9 nodes ÷ 3 replicas = 3 sets ✅

Max 15 nodes default

Resource management

Contact support for higher limits

Single namespace per cluster - Each Halyard Cloud cluster supports only one namespace. To isolate workloads or data, use sets or provision separate clusters for complete isolation.

After their initial configuration, the following settings cannot be changed:

Replication factor - Plan carefully for your durability needs

Zone count - Consider growth when selecting zones

Strong consistency + Memory storage - Choose one consistency model

Not all Halyard server settings are available through the cloud - See advanced config for more information

Check workarounds in the tables above

Review best practices for optimal configurations

Contact support for limit increases or timeline questions

Join community for peer discussions and updates

Technical limits : Contact your technical account manager

Billing limits : Discuss with your sales engineer

Timeline questions : We plan to publish a public roadmap for 2026 features

Cluster planning best practices

API usage patterns

Monitoring and alerting