Update AWS Bedrock documentation with IAM guidelines

What does this MR do and why?

Adds additional context around AWS IAM setup for self-hosted Bedrock models. Also adds a link out to official AWS Bedrock IAM documentation.

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Related to #505353 (closed)

changed milestone to %17.9

added Custom Models: GA Deliverable devopsai-powered documentation groupcustom models planning priority sectiondata-science typefeature workflowready for development labels

assigned to @julie_huang

added 1 commit

• ad9c337e - Update Bedrock documentation with guidance around IAM setup

Compare with previous version

	1 Message
	This merge request adds or changes documentation files and requires Technical Writing review. The review should happen before merge, but can be post-merge if the merge request is time sensitive.

Documentation review

The following files require a review from a technical writer:

• doc/administration/self_hosted_models/supported_llm_serving_platforms.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added docs-only label

marked this merge request as ready

changed title from Draft: Resolve "AWS Bedrock Authentication Documentation" to Update AWS Bedrock documentation with IAM guidelines

changed the description

removed docs-only label

requested review from @eduardobonet

Hey @eduardobonet would you mind reviewing this doc update please? Let me know if you think it could be worded better.

removed typefeature label

added typefeature label

added docs-only label

added typemaintenance label and removed typefeature label

added workflowin review label and removed workflowready for development label

@jglassman1 would you mind reviewing this doc update for Technical Writing? Thank you

requested review from @jglassman1

mentioned in issue #505353 (closed)

@mhamda @sean_carroll @julie_huang @eduardobonet it looks like we've got two MRs currently open that duplicate each other?

• !178395 (merged)
• !178411 (closed)

mentioned in merge request !178411 (closed)

added 1 commit

• 58189df5 - Apply reviewer suggestions for greater clarity

Compare with previous version

added 1 commit

• 8b5e0f40 - Apply reviewer suggestions for greater clarity

Compare with previous version

approved this merge request

Hi @jglassman1 ,

GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.

This message was generated automatically. Improve it or delete it.

added Technical Writing label

resolved all threads

enabled automatic add to merge train when checks pass

started a merge train

merged

mentioned in commit 8a9d75cc

added workflowstaging-canary label and removed workflowin review label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added workflowpost-deploy-db-staging label and removed workflowproduction label

added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label