Skip to content

feat: add bedrock-adoption-readiness production assessment skill - #63

Open
SruVed wants to merge 2 commits into
aws:mainfrom
SruVed:feature/bedrock-adoption-readiness
Open

feat: add bedrock-adoption-readiness production assessment skill#63
SruVed wants to merge 2 commits into
aws:mainfrom
SruVed:feature/bedrock-adoption-readiness

Conversation

@SruVed

@SruVed SruVed commented Aug 21, 2026

Copy link
Copy Markdown

Summary

Phase 1 MVP skill covering four dimensions: IAM governance, data retention (ZDR), quota and capacity headroom, and operational observability. Operates across both Standard Bedrock and Mantle surfaces with
multi-region discovery.

Testing

  • 3/3 manual activation tests passed in DevOps Agent
  • Full investigation produced correct findings with proper severity ratings
  • Focused prompts (IAM-only, quota-only) activated and ran correctly

Taskei

V2324033077 - accepted by Project Nebula team (reviewer: pbraz)

Checklist

  • SKILL.md has version and author in metadata
  • name in frontmatter matches directory name
  • description clearly states what/when to activate
  • README.md includes non-production disclaimer
  • CHANGELOG.md present
  • Tested in DevOps Agent (skill activates consistently)
  • No internal Amazon tool names in submitted content
  • No customer data, account IDs, or credentials
  • Working against latest main

| CW dimensions | `ModelId` | `Model`, `Project` |
| IAM prefix | `bedrock:`, `bedrock-runtime:` | `bedrock-mantle:` |
| Cost discriminator | No marker in USAGE_TYPE | `-mantle-` substring in USAGE_TYPE |
| Cross-region inference | Yes (`global.` prefix in ModelId) | No (in-region only) |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is incomplete. Global cross-region inference is only one mechanism. You also have geographic cross region inference (example us. prefix)

Ref


### 3.6 Guardrails

List Bedrock guardrails. Zero guardrails on a production deployment is a finding.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bedrock Guardrails are not available on Mantle endpoints. If customers use bedrock-mantle, this would flag incorrectly

Ref

| LOW | Minor optimization | Address when convenient |
| INFO | Observation, no action required | N/A |

## Phase 2 (Future)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Future work references should not be included


The DevOps Agent role needs read-only access. Most required actions are covered by `AIDevOpsAgentAccessPolicy` (v10+):

```json

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link to the existing policy document in the documentation, not copy it here. This can change over time.

- Severity-rated findings (CRITICAL/HIGH/MEDIUM/LOW/INFO)
- Structured report output with priority matrix and verdict

### Not included (Phase 2)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Future work should not be included.


**Phase 1 (this release):** D1 IAM, D2 ZDR, D3 Quota, D6 Observability - all API/metrics-driven, no dependency on customer configuration state.

**Phase 2 (future):** D4 Model Selection Fitness, D5 Cost Projection - require model invocation logging to be enabled.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Future work should not be referenced or included


### 3.7 VPC Endpoints

Check for VPC endpoints matching `com.amazonaws.<region>.bedrock-runtime`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- Add geographic cross-region inference prefixes (us., eu., ap.) alongside global.
- Scope guardrails check to Standard Bedrock only (not available on Mantle)
- List all 5 VPC endpoint service names per docs
- Remove all Phase 2/future work references
- Replace IAM policy JSON with link to managed policy doc
- Add doc reference for VPC endpoints
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants