AWS solutions documentation change
Summary
Fixed broken link to PREDEPLOYMENT.md by adding a valid GitHub URL
Security assessment
Link correction improves documentation usability but does not address security issues or add security-specific content.
Diff
diff --git a/solutions/latest/modern-data-architecture-accelerator/deploy-the-solution.md b/solutions/latest/modern-data-architecture-accelerator/deploy-the-solution.md index 62b735541..9d9168046 100644 --- a//solutions/latest/modern-data-architecture-accelerator/deploy-the-solution.md +++ b//solutions/latest/modern-data-architecture-accelerator/deploy-the-solution.md @@ -257 +257 @@ MDAA can be installed from a private NPM package repo, and will also attempt to -Ensure that your private NPM repo is accessible and contains the appropriate MDAA NPM artifacts. If using a localhost based NPM repo (such as Verdaccio), ensure it is running on localhost and updated with the latest MDAA packages from S3 (See [PREDEPLOYMENT](./.html#prerequisites)). When executed from its NPM package, MDAA will also attempt to NPM install each MDAA module from NPM repo. +Ensure that your private NPM repo is accessible and contains the appropriate MDAA NPM artifacts. If using a localhost based NPM repo (such as Verdaccio), ensure it is running on localhost and updated with the latest MDAA packages from S3 (See [PREDEPLOYMENT](https://github.com/aws/modern-data-architecture-accelerator/blob/main/PREDEPLOYMENT.md)). When executed from its NPM package, MDAA will also attempt to NPM install each MDAA module from NPM repo.