Cloud decisions need the evidence behind the console.
Use an authenticated AWS account in Strawberry to investigate the console pages, documentation, incident material, and cost questions that belong in the same decision.
01
A resource name does not explain production risk.
An instance, bucket, or alarm can look harmless in isolation.
The real question is what service it supports, what changed, and who would be affected.
Strawberry can review the AWS pages you open with incident notes and architecture material, then prepare a source-linked investigation brief.
02
Cost anomalies require a business explanation.
A sudden line-item increase may be expected after a launch, or it may be a configuration mistake. A number alone cannot decide which.
Strawberry can place the visible AWS billing context beside deployment notes and usage evidence to prepare a finance-and-engineering review.
03
An access review should identify what needs an owner.
A permissions page is too important for a vague cleanup request.
The team needs a clear record of the principal, scope, reason, and reviewer.
Strawberry can turn the AWS console material you provide into a proposed access-review pack while the actual change stays under AWS controls.
04
An incident retrospective should keep its sources.
After a cloud incident, context disappears when screenshots and tabs are reduced to an untraceable summary. The next responder needs the original trail.
A Strawberry skill can standardise the retrospective preparation, and a routine can assemble the agreed browser and document inputs for the incident lead.
AWS Strawberry