Add warning section

Author: cmilesb

content/operate/rc/subscriptions/bring-your-own-cloud/_index.md

@@ -50,4 +50,15 @@ To set up Redis Cloud BYOC on Amazon Web Services (AWS):
 
 1. [Set your AWS Account as a BYOC Cloud account]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/cloud-account-settings" >}}) on Redis Cloud.
 
+## Avoid Redis Cloud BYOC service disruption {#avoid-service-disruption}
+
+{{< warning >}}
+Failing to follow the instructions in this section will cause your databases to become inaccessible, and Redis will not be able to ensure cluster and database stability. Please read them carefully.
+{{< /warning >}}
+
+To keep your Redis Cloud BYOC service and all databases running without issues:
+- Do not stop, delete, or modify Redis-managed resources through the cloud provider - including VPCs, subnets, virtual machines, and other infrastructure.
+- Do not change roles or access policies.
+
+If you make any infrastructure changes, whether or not they are listed above, it may violate our SLA commitments. See [Appendix 1 in our Terms of Service](https://redis.io/legal/cloud-tos/#Appendix-1) for more details.
 

content/operate/rc/subscriptions/bring-your-own-cloud/cloud-account-settings.md

@@ -21,11 +21,9 @@ To do this, you need:
 
 You need to create these resources before adding the cloud account to your subscription.  To learn more, see [Create IAM resources]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/iam-resources" >}}).
 
-{{<note>}}
-Once an AWS account has been configured as a cloud account, you must _not_:
-- Manually change the configuration of required resources, such as security groups<br/>
-- Manually suspend or stop (terminate) provisioned resources</br>
-{{</note>}}
+{{<warning>}}
+After an AWS account has been configured as a cloud account, you **must not** change the configurations of provisioned resources or stop or terminate provisioned instances. If you do, your databases will be inaccessible and Redis will not be able to ensure database stability. See [Avoid service disruption]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/cloud-account-settings#avoid-service-disruption" >}}) for more details.
+{{</warning>}}
 
 ## View cloud account settings
 

content/operate/rc/subscriptions/bring-your-own-cloud/iam-resources/_index.md

@@ -27,10 +27,7 @@ Save the access key in a secure location so that you can enter it when you [regi
 {{< warning >}}
 We use the provided credentials to configure your AWS environment and provision required resources.
 
-To make sure that we can manage your AWS resources, you must not:
-
-- Manually change the configurations of provisioned resources, such as security groups
-- Manually stop or terminate provisioned instances
+You **must not** change the configurations of provisioned resources or stop or terminate provisioned instances. If you do, your databases will be inaccessible and Redis will not be able to ensure database stability. See [Avoid service disruption]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/cloud-account-settings#avoid-service-disruption" >}}) for more details.
 {{< /warning >}}
 
 For help creating an AWS user, see the [AWS IAM documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html).

content/operate/rc/subscriptions/bring-your-own-cloud/iam-resources/aws-console.md

@@ -10,6 +10,12 @@ weight: $weight
 ---
 Follow these steps to manually create IAM resources using the [AWS console](https://console.aws.amazon.com/).
 
+{{< warning >}}
+We use the provided credentials to configure your AWS environment and provision required resources.
+
+You **must not** change the configurations of provisioned resources or stop or terminate provisioned instances. If you do, your databases will be inaccessible and Redis will not be able to ensure database stability. See [Avoid service disruption]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/cloud-account-settings#avoid-service-disruption" >}}) for more details.
+{{< /warning >}}
+
 ## Step 1: Create the IAM instance policy
 
 First, create a policy to use for the new instance role:

content/operate/rc/subscriptions/bring-your-own-cloud/iam-resources/cloudformation.md

@@ -66,3 +66,9 @@ VersionStages:
 The JSON object is the value (less the single quotes) of the `SecretString` key. i.e. it is <nobr>`{"password":"S3cr3tP@$$w0rd"}`</nobr>.
 
 The password is the value associated with that key (less the double quotes): `S3cr3tP@$$w0rd`.
+
+{{< warning >}}
+We use the provided credentials to configure your AWS environment and provision required resources.
+
+You **must not** change the configurations of provisioned resources or stop or terminate provisioned instances. If you do, your databases will be inaccessible and Redis will not be able to ensure database stability. See [Avoid service disruption]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/cloud-account-settings#avoid-service-disruption" >}}) for more details.
+{{< /warning >}}

content/operate/rc/subscriptions/bring-your-own-cloud/iam-resources/terraform.md

@@ -10,6 +10,12 @@ linkTitle: Terraform
 ---
 You can use [HashiCorp Terraform](https://www.terraform.io/intro/index.html) to create identity and access management (IAM) resources to support AWS cloud account access to Redis Cloud subscriptions.
 
+{{< warning >}}
+We use the provided credentials to configure your AWS environment and provision required resources.
+
+You **must not** change the configurations of provisioned resources or stop or terminate provisioned instances. If you do, your databases will be inaccessible and Redis will not be able to ensure database stability. See [Avoid service disruption]({{< relref "/operate/rc/subscriptions/bring-your-own-cloud/cloud-account-settings#avoid-service-disruption" >}}) for more details.
+{{< /warning >}}
+
 The following example uses the `terraform-aws-Redislabs-Cloud-Account-IAM-Resources` module, located in Amazon&nbsp;S3: