AWS iot-twinmaker: Add warning about regulated workloads and sign-up experience
Summary
Added guidance that the new AWS sign-up experience isn't suitable for regulated workloads, with links to advanced options.
Security assessment
This adds compliance documentation, a security-adjacent best practice for regulated environments, but doesn't address a specific vulnerability.
Evidence
+Our new AWS sign-up experience is not designed for regulated workloads. If you're using our new AWS sign-up experience, but you want to use AWS for regulated workloads, you can [sign up for AWS (advanced)](https://docs.aws.amazon.com/accounts/latest/reference/getting-started.html) or [activate advanced features](https://docs.aws.amazon.com/accounts/latest/reference/activate-advanced-features.html) for your AWS environment.
Diff
diff --git a/iot-twinmaker/latest/guide/SERVICENAME-compliance.md b/iot-twinmaker/latest/guide/SERVICENAME-compliance.md index dcd5c5af4..048243946 100644 --- a//iot-twinmaker/latest/guide/SERVICENAME-compliance.md +++ b//iot-twinmaker/latest/guide/SERVICENAME-compliance.md @@ -8,0 +9,2 @@ +Our new AWS sign-up experience is not designed for regulated workloads. If you're using our new AWS sign-up experience, but you want to use AWS for regulated workloads, you can [sign up for AWS (advanced)](https://docs.aws.amazon.com/accounts/latest/reference/getting-started.html) or [activate advanced features](https://docs.aws.amazon.com/accounts/latest/reference/activate-advanced-features.html) for your AWS environment. +