AWS fsx documentation change
Summary
Updated references from 'AWS Directory Service' to 'Directory Service' for terminology consistency
Security assessment
The changes are minor terminology updates removing redundant 'AWS' qualifiers from service names. No security vulnerabilities, mitigations, or security features are mentioned or modified. The existing security context about trust relationships and authentication flows remains unchanged.
Diff
diff --git a/fsx/latest/WindowsGuide/fsx-aws-managed-ad.md b/fsx/latest/WindowsGuide/fsx-aws-managed-ad.md index 37a5e1ee9..5669266e0 100644 --- a//fsx/latest/WindowsGuide/fsx-aws-managed-ad.md +++ b//fsx/latest/WindowsGuide/fsx-aws-managed-ad.md @@ -72 +72 @@ You join your file system to an AWS Managed Microsoft AD setup. You then establi -Your corporate domain takes the role of the trusted domain, and the AWS Directory Service managed domain takes the role of the trusting domain. Validated authentication requests travel between the domains in only one direction—allowing accounts in your corporate domain to authenticate against resources shared in the managed domain. In this case, Amazon FSx interacts only with the AWS managed domain. In a Kerberos authentication scenario, authentication requests originating from a corporate client get validated by the corporate domain, which then refers it to the AWS Managed Microsoft AD, and eventually the client presents its service ticket to your FSx for Windows File Server file system. For more information about trusts, see the post [ Everything you wanted to know about trusts with AWS Managed Microsoft AD](https://aws.amazon.com/blogs/security/everything-you-wanted-to-know-about-trusts-with-aws-managed-microsoft-ad/) in the AWS Security Blog. +Your corporate domain takes the role of the trusted domain, and the Directory Service managed domain takes the role of the trusting domain. Validated authentication requests travel between the domains in only one direction—allowing accounts in your corporate domain to authenticate against resources shared in the managed domain. In this case, Amazon FSx interacts only with the AWS managed domain. In a Kerberos authentication scenario, authentication requests originating from a corporate client get validated by the corporate domain, which then refers it to the AWS Managed Microsoft AD, and eventually the client presents its service ticket to your FSx for Windows File Server file system. For more information about trusts, see the post [ Everything you wanted to know about trusts with AWS Managed Microsoft AD](https://aws.amazon.com/blogs/security/everything-you-wanted-to-know-about-trusts-with-aws-managed-microsoft-ad/) in the AWS Security Blog. @@ -80 +80 @@ The following related resources can help you as you use AWS Directory Service fo - * [What is AWS Directory Service](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/what_is.html) in the _AWS Directory Service Administration Guide_ + * [What is Directory Service](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/what_is.html) in the _AWS Directory Service Administration Guide_