You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the TED infrastructure, Redis has previously been the default caching engine. We now recommend moving to [Valkey](https://aws.amazon.com/elasticache/what-is-valkey/), a community-driven alternative to Redis.
129
+
130
+
For customers currently using Redis OSS cache, [here is how to update to Valkey](/guardrails/docs/guides/hosting-guardrails/updating-stacks/upgrade-to-valkey-cache).
131
+
126
132
## Step 16: Configure Advanced - Foundation Parameters and Overrides
127
133
128
134
The Foundation Parameters allow the TED stack to use SSM parameters defined in the TEF stack. You should only change these values if you did not use the default Resource Name Prefix (turbot) in the TEF stack.
The values of the parameters will initially be set to match previous run of the product. Review the [release notes](https://turbot.com/guardrails/changelog?tag=ted) for the TED versions between the existing version and the version you are updating to, and identify any new parameters that require a decision about how they will be set. Generally, new parameters will be created in a way to have the least disruption on an existing environment, but care should still be taken to understand these and read any new parameter descriptions to understand their impact.
> A frequent issue arises when databases employ auto-scaling storage. Discrepancies in storage figures between the stack and the product can occur if the database has expanded since installation.
88
88
> Upgrading to a major version can introduce significant changes and potential risks. You should not upgrade to a new major version without first consulting with Turbot Support.
89
89
> To ensure cost-efficiency, review and update instance types and ElastiCache Versions at least annually to align with the latest supported options.
90
90
91
+
### Upgrade to Valkey cache
92
+
93
+
As part of the TED infrastructure, Redis has previously been the default caching engine. We now recommend moving to [Valkey](https://aws.amazon.com/elasticache/what-is-valkey/), a community-driven alternative to Redis.
94
+
95
+
For customers currently using Redis OSS cache, [here is how to update to Valkey](/guardrails/docs/guides/hosting-guardrails/updating-stacks/upgrade-to-valkey-cache).
96
+
91
97
## Step 11: Update TED
92
98
93
99
After verifying any changes to existing parameters, select **Update** at the bottom of the screen.
@@ -103,21 +109,21 @@ You have initiated the installation of the new TED version. This triggers an upd
103
109
104
110
Select the TED Provisioned Product, select the **Outputs** tab, and use the **CloudFormationStackARN****Value** link to navigate to the CloudFormation stack and monitor the update progress.
The values of the parameters will initially be set to match previous run of the product. Review the [release notes](https://turbot.com/guardrails/changelog?tag=tef) for the TEF versions between the existing version and the version you are updating to, and identify any new parameters that require a decision about how they will be set.
64
64
65
65
Generally, new parameters will be created in a way to have the least disruption on an existing environment, but care should still be taken to understand these and read any new parameter descriptions to understand their impact.
You have initiated the installation of the new TEF version. This triggers an update of several nested CloudFormation stacks.
78
78
79
79
Select the TEF Provisioned Product, click the `Outputs` tab, and use the `CloudFormationStackARN` link to navigate to CloudFormation and monitor the update progress.
80
80
81
-
81
+
82
82
83
83
-[ ] Verify TEF stack status transitions to `UPDATE_IN_PROGRESS` upon modification and review the Events tab for expected parameter/resource updates.
52
+
53
53
54
54
Scroll down to **Advanced options**, leave the entire section as default and select **Next**
55
55
56
-
56
+
57
57
58
58
59
59
## Step 5: Submit Changes
60
60
61
61
In **Configure stack options**, review changes under **Changeset Preview** and select **Submit**.
0 commit comments