[kmcginnes]

Summary

The deployment guides read like recommended setups, so each now says it is an example and points to the supported hosting model and general AWS guidance.

User-facing: the Docker, EC2, ECS Fargate and SageMaker guides open with a note that the guide is not a recommended production configuration.

 docs/
 ├── guides/
+│   ├── deploy-with-docker.md       # example paragraph
+│   ├── deploy-to-ec2.md            # example paragraph, replaces its own wording
+│   ├── deploy-to-ecs-fargate.md    # example paragraph
+│   └── deploy-to-sagemaker.md      # example paragraph
 ├── references/
+│   └── security.md                 # matching paragraph under Access Control
 └── agents/
+    └── documentation.md            # new deployment guides must carry it

Merge Danger

Door: two-way

The #supported-hosting links point at a section that Document the supported hosting model (#2459) adds, so merge after it.

Impact: docs only

Related

• Closes Clarify that deployment guides are examples #2460
• Related to Make the ECS Fargate guide private by default and split its IAM roles #2225
• Blocked by Document the supported hosting model #2459

[kmcginnes]

Approved