Cloud operations · v1.0.0

AWS Cloud Operator

Plan and operate bounded AWS app infrastructure changes with explicit identity, cost, previews, protected resources, verification, and recovery.

Release candidate
The workflow passed static publication checks, but download remains disabled until its license and final release manifest are approved.

The outcome

Complete one AWS commercial-application operation safely without silently changing accounts, overbuilding for future scale, drifting managed resources, exposing secrets, or harming neighboring projects.

Use it when

  • Use when a commercial app needs an AWS infrastructure plan, deployment, certificate, permission correction, service configuration, rollback, or production verification.
  • Use when AWS Bedrock access or model activation must be aligned with runtime identity, region, quotas, current cost, platform billing, and rollback.

It does not do

  • Does not replace the user’s final authorization for project scope, account access, external changes, or business consequences.
  • Does not represent repository static checks as runtime certification across every platform, provider account, or production environment.

Inputs

  • Named AWS profile or authenticated console context, exact account/role/region, project and environment, repository/IaC state, desired outcome, load assumptions, and spending tolerance.
  • Protected runtime access plus backup, health, and recovery context required by the approved operation.

Outputs

  • Validated AWS change manifest with caller identity, native preview, protected resources, cost impact, verification, and recovery.
  • Provider convergence, application health, security-boundary, neighboring-project, and post-change cost-control evidence.

Natural-language triggers

Use $aws-cloud-operator to compare a low-cost Lightsail pilot with the proposed ECS/RDS stack, preview the chosen change, deploy it, and verify existing apps remain healthy.
Use $aws-cloud-operator to diagnose this S3 AccessDenied, add only the required prefix permission, and verify both allowed and denied boundaries.
Use $aws-cloud-operator to prepare and verify an ACM certificate whose DNS is hosted in Alibaba Cloud.

Permission map

FilesWrite

May inspect and update explicitly scoped project or configuration files.

CommandsExecute

May run project, platform, validation, and deployment commands.

NetworkExecute

May call declared provider APIs and public verification endpoints.

AccountsChanges state

May read or change authorized provider-account configuration after required confirmation.

BrowserChanges state

May use provider consoles for states not exposed safely through an API or CLI.

External changesChanges state

Can create consequential external state; preview, confirmation, verification, and rollback are required.

Environment & requirements

Agents

  • Codex
  • Claude Code

Platforms

  • macOS
  • Linux
  • Windows

Required tools

  • AWS account
  • AWS CLI or console
  • Git

Data handling

May process AWS identity, resource inventory, cost, and deployment state; keys, private keys, customer data, and signed URLs must not enter artifacts or durable records.

Credential handling

Uses only existing secure credential channels authorized by the user; tokens, keys, cookies, private keys, and real user data must not be copied into the Skill, logs, reports, or public artifacts.

Declared network domains

console.aws.amazon.com amazonaws.com

Verification evidence

Passed repository structure, bilingual metadata, and reference checks; this Skill has not entered candidate-artifact generation or runtime verification.

Level
Checked
Checked
2026-10-12
Expires
2027-01-10
Source revision
fac86e9d2646

Environment

  • Repository structure and metadata validation on macOS

Targets checked

  • source metadata
  • package structure

Evidence IDs

  • public-catalog-schema-v3
  • source-repository-validation

Limits & support

Known limitations

  • The current verification level is a repository static check, not an end-to-end validation against a real provider account, physical device, or production environment.
  • Agents, platforms, and provider interfaces continue to change; each run must inspect current state and respect explicit confirmation gates.

Permission changes

  • No permission change is declared for this release; for a first public release, the permission map on this page is authoritative.

Channel
Submit through support@xiaoyuelabs.com or the on-site inquiry form.

Response target
Receipt is acknowledged within two business days; remediation timing is confirmed after reproduction and scope review.

Scope
Free support covers download integrity, documentation errors, and reproducible Skill defects; project adaptation, managed operation, and ongoing maintenance are separate services.

Release notes

v1.0.0
  • Added a cost-aware, brownfield-safe AWS application operations workflow spanning identity, inventory, IaC previews, deployment, IAM, certificates, secrets, observability, data services, and recovery.
  • Added stage-fit guidance that compares shared-host, pilot, and managed scale architectures before creating fixed-cost resources.
  • Added bounded Bedrock activation guidance and a secret-free AWS change-manifest validator that rejects root callers, production hotswap, protected-resource edits, unresolved risk, and incomplete recovery.

Install & verify

Release access

Available for evaluation, not yet packaged

v1.0.0

This workflow is listed so its scope, permissions, and service fit can be evaluated. It has not entered the first downloadable release batch and no public artifact exists.