AWS res: Mark DomainTLSCertificateSecretARN required for LDAPS
Summary
Updates parameter documentation so DomainTLSCertificateSecretARN is labeled required for LDAPS (leave empty otherwise), and adds a step describing optional CloudFormation tags with reserved Name/res:* keys. Template launch URL also updated.
Security assessment
The change documents that a certificate secret ARN is needed to enable LDAPS (TLS) communication to Active Directory, clarifying how to secure the AD channel with encryption rather than plaintext LDAP.
Evidence
DomainTLSCertificateSecretARN | | _(Required for LDAPS)_ Provide a domain TLS certificate secret ARN to enable TLS communication to AD. Leave empty if not using LDAPS.
Diff
diff --git a/res/archive/release-minus-3/ug/launch-the-product.md b/res/archive/release-minus-3/ug/launch-the-product.md index 0a318878f..650cea759 100644 --- a//res/archive/release-minus-3/ug/launch-the-product.md +++ b//res/archive/release-minus-3/ug/launch-the-product.md @@ -27 +27 @@ 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). @@ -64 +64 @@ 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. @@ -77 +77,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.