Skip to content

feat: Add bedrock-operation-review skill - #75

Open
sean-nixon wants to merge 2 commits into
aws:mainfrom
sean-nixon:feature/bedrock-operation-review
Open

feat: Add bedrock-operation-review skill#75
sean-nixon wants to merge 2 commits into
aws:mainfrom
sean-nixon:feature/bedrock-operation-review

Conversation

@sean-nixon

Copy link
Copy Markdown

Description

This PR adds the bedrock-operation-review skill, a comprehensive Amazon Bedrock operational review aligned with the AWS Well-Architected Framework and Bedrock best practices. The skill evaluates workloads across five pillars — Security, Performance, Service Quotas, Cost Optimization, and Resilience — covering resource discovery (foundation models, guardrails, inference profiles, provisioned throughput, custom models, agents, knowledge bases, and Prompt Management), CloudWatch metric analysis with threshold-based severity classification, service quota utilization, and cost optimization opportunities such as prompt caching, model distillation, and batch inference. All data is collected through AWS control-plane APIs only (Bedrock, Bedrock Agent, CloudWatch, Service Quotas, EC2), with no data-plane model invocations and no prompt/response content read, and reviews produce a severity-ranked, shareable Markdown report.

Type of change

  • New skill
  • New custom agent
  • Update to an existing skill or agent
  • Documentation or infrastructure change

Testing

Tested using Agent Skill Eval (report in PR). Manually tested in DevOps Agent to confirm the skill triggered and output was valid. Full investigation produced correct findings with proper severity ratings.

License confirmation

  • By submitting this pull request, I confirm that my contribution is made under the terms of the Apache License 2.0.

Sean Nixon added 2 commits September 4, 2026 09:39
Refine the Bedrock operational review skill's findings guidance and
supporting docs:

- Scope IAM findings to INFO and note that a comprehensive
  least-privilege audit is out of scope for this skill
- Correct model-access guidance: foundation models are enabled by
  default, so access should be controlled via IAM/SCP scoped to
  essential models rather than a per-model access request
- Correct the model-lifecycle EOL note to reflect per-model notice
  periods (6 months or 45 days per the model card) instead of a fixed
  period
- Fix the guardrail quotas reference link
- Correct "six pillars" to "five pillars" in the README and add a
  non-production sample-code disclaimer
- Set the 1.0.0 CHANGELOG date to 2026-09-10
- Anonymize absolute skill_path to a relative path in eval reports
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.

1 participant