AWS solutions documentation change
Summary
Simplified formatting and consolidated notes in the MLOps Workload Orchestrator documentation. Removed redundant line breaks and merged note sections into the parameter descriptions.
Security assessment
The changes are primarily formatting improvements and consolidation of notes. While the documentation mentions security best practices for S3 buckets (like blocking public access and enabling encryption), these were already present in the previous version and are not new security-related additions.
Diff
diff --git a/solutions/latest/mlops-workload-orchestrator/step-1-launch-the-stack.md index e428efbe1..15d8c792a 100644 --- a/solutions/latest/mlops-workload-orchestrator/step-1-launch-the-stack.md +++ b/solutions/latest/mlops-workload-orchestrator/step-1-launch-the-stack.md @@ -11,3 +11 @@ Follow the step-by-step instructions in this section to configure and deploy the - 1. Sign in to the [AWS Management Console](https://aws.amazon.com/console/) and select the button to launch the `mlops-workload-orchestrator-single-account.template` AWS CloudFormation template. - -[  ](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?templateURL=https:%2F%2Fs3.amazonaws.com%2Fsolutions-reference%2Fmlops-workload-orchestrator%2Flatest%2Fmlops-workload-orchestrator-single-account.template&redirectId=ImplementationGuide) + 1. Sign into [AWS Management Console](https://aws.amazon.com/console) and select the button to launch `mlops-workload-orchestrator-single-account.template` AWS CloudFormation template. [  ](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?templateURL=https:%2F%2Fs3.amazonaws.com%2Fsolutions-reference%2Fmlops-workload-orchestrator%2Flatest%2Fmlops-workload-orchestrator-single-account.template&redirectId=ImplementationGuide) @@ -30,15 +28,3 @@ Parameter | Default | Description -**MLOps configuration S3 bucket name** | <Optional input> | Specify the name of an existing S3 bucket where the `mlops-config.json` file will be uploaded to provision the pipeline. - -###### Note - -The S3 bucket must be in the same AWS Region as the stack being deployed. -**Name of an Existing S3 Bucket** | <Optional Input> | Optionally, provide the name of an existing S3 bucket to be used as the S3 assets bucket. If an existing bucket is not provided, the solution creates a new S3 bucket. - -###### Note - -If you use an existing S3 bucket for the bucket must meet the following requirements: 1) the bucket must be in the same Region as the MLOps Workload Orchestrator stack, 2) the bucket must allow reading/writing objects to/from the bucket, and 3) versioning must be allowed on the bucket. We recommended blocking public access, enabling S3 server-side encryption, access logging, and secure transport (for example, HTTPS only bucket policy) on your existing S3 bucket. -**Name of an Existing Amazon ECR repository** | <Optional input> | Optionally, provide the name of an existing Amazon ECR repository name to be used for custom algorithms images. If you do not specify an existing repository, the solution creates a new Amazon ECR repository. - -###### Note - -The Amazon ECR repository must be in the same Region where the solution is deployed. +**MLOps configuration S3 bucket name** | `<Optional input>` | Specify the name of an existing S3 bucket where the `mlops-config.json` file will be uploaded to provision the pipeline.NOTE: The S3 bucket must be in the same AWS Region as the stack being deployed. +**Name of an Existing S3 Bucket** | `<Optional Input>` | Optionally, provide the name of an existing S3 bucket to be used as the S3 assets bucket. If an existing bucket is not provided, the solution creates a new S3 bucket. NOTE: If you use an existing S3 bucket for the bucket must meet the following requirements: 1) the bucket must be in the same Region as the MLOps Workload Orchestrator stack, 2) the bucket must allow reading/writing objects to/from the bucket, and 3) versioning must be allowed on the bucket. We recommended blocking public access, enabling S3 server-side encryption, access logging, and secure transport (for example, HTTPS only bucket policy) on your existing S3 bucket. +**Name of an Existing Amazon ECR repository** | `<Optional Input>` | Optionally, provide the name of an existing Amazon ECR repository name to be used for custom algorithms images. If you do not specify an existing repository, the solution creates a new Amazon ECR repository. NOTE: The Amazon ECR repository must be in the same Region where the solution is deployed.