AWS Security ChangesHomeSearch

AWS res documentation change

Service: res · 2026-03-28 · Documentation low

File: res/archive/release-minus-1/ug/launch-the-product.md

Summary

Updated CloudFormation template URL encoding, clarified DomainTLSCertificateSecretARN parameter as required for LDAPS, and added step for configuring tags during stack deployment.

Security assessment

The change clarifies that DomainTLSCertificateSecretARN is required for LDAPS (secure LDAP), which is a security feature for encrypting AD communications. This adds documentation about security configuration but doesn't indicate a specific security issue was fixed.

Diff

diff --git a/res/archive/release-minus-1/ug/launch-the-product.md b/res/archive/release-minus-1/ug/launch-the-product.md
index 9ff3d2658..0f6610b55 100644
--- a//res/archive/release-minus-1/ug/launch-the-product.md
+++ b//res/archive/release-minus-1/ug/launch-the-product.md
@@ -25 +25 @@ The AWS CloudFormation template deploys Research and Engineering Studio on AWS i
-  2. Launch the [ template ](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/quickcreate?templateURL=https://research-engineering-studio-us-east-1.s3.amazonaws.com/releases/latest/ResearchAndEngineeringStudio.template.json).
+  2. Launch the [ template ](https://console.aws.amazon.com/cloudformation/home#/stacks/quickcreate?templateURL=https%3A%2F%2Fresearch-engineering-studio-us-east-1.s3.amazonaws.com%2Freleases%2Flatest%2FResearchAndEngineeringStudio.template.json).
@@ -62 +62 @@ ComputersOU |  | Organizational unit within AD that instances will join.
-DomainTLSCertificateSecretARN |  | _(Optional)_ Provide a domain TLS certificate secret ARN to enable TLS communication to AD.  
+DomainTLSCertificateSecretARN |  |  _(Required for LDAPS)_ Provide a domain TLS certificate secret ARN to enable TLS communication to AD. Leave empty if not using LDAPS.   
@@ -75 +75,3 @@ CognitoUserPoolDomainUrl  |  | Cognito user pool domain for managed login. This
-  5. Choose **Create stack** to deploy the stack. 
+  5. Under **Configure stack options → Tags -_optional_** , add the tags (key-value pairs) you want to apply to RES deployed resources. Tag key `Name` and `res:*` are preserved by RES and could not be used as tag key.
+
+  6. Choose **Create stack** to deploy the stack.