DevOps & cloud · Automation
cloud-operations
/cloud-operations
Use when working with AWS, GCP, or Azure resource management, permissions, or deployments
- Author
- tspry ↗
- Repository
- superpowers-devops ↗
- Licence
- MIT
- Last repository change
- 20.10.2026
Assessment and security
100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.
Licence
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when working with AWS, GCP, or Azure resource management, permissions, or deployments
Original author description
Use when working with AWS, GCP, or Azure resource management, permissions, or deployments
How it works
- Mode Detection
- AWS
- GCP
- Azure
- Tooling Templates
Original SKILL.md headings · 90 lines, 426 words
SKILL.md preview
---
name: cloud-operations
description: Use when working with AWS, GCP, or Azure resource management, permissions, or deployments
---
# Cloud Operations
## Mode Detection
- **Repo mode** — check `tooling/README.md` for shipped AWS examples and prerequisites; generate other cloud configs from the project's conventions.
- **Chat mode** — user pastes cloud error or config. Diagnose and provide corrected config.
## AWS
### Essential debugging commands
```bash
# Check current identity
aws sts get-caller-identity
# List resources
aws ec2 describe-instances --query 'Reservations[].Instances[].[InstanceId,State.Name,Tags[?Key==`Name`].Value|[0]]' --output table
# CloudWatch logs
aws logs describe-log-groups
aws logs tail /aws/lambda/my-function --follow
# ECS
aws ecs describe-services --cluster my-cluster --services my-service
aws ecs describe-tasks --cluster my-cluster --tasks <task-arn>
```
### Common AWS errors
| Error | Fix |
|---|---|
| `AccessDenied` | Identify the denied principal, action, resource, and controlling policy layer before changing permissions |
| `ThrottlingException` | Implement exponential backoff retry |
| `InvalidClientTokenId` | Check AWS credentials and region config |
| `NoSuchBucket` | Wrong region or bucket name |
### AWS authorization denials
Do not treat `AccessDenied` as proof that the identity policy needs another action.
1. Preserve the full error and record the caller from `aws sts get-caller-identity`, requested action, resource ARN, account, region, credentials/session, and network path.
2. Distinguish an explicit deny from an implicit deny. Use any policy type named in the error, but do not assume it is the only applicable deny.
3. Evaluate the effective policy layers that apply: identity policy, resource policy, permissions boundary, session policy, Organizations SCP/RCP, VPC endpoint policy, and request conditions. For `sts:AssumeRole`, also inspect the target role trust policy.
4. Check action/resource shape and condition context, including region, tags, organization, source VPC/endpoint, and principal/session ARN.
5. Propose only the narrowest authorized change to the policy layer proven to cause the denial. An SCP or boundary denial is not fixed by broadening the role's identity policy.
6. Re-test with the same principal, session path, region, action, and resource. Use CloudTrail, the policy simulator, or authorization details when available; state when those sources are unavailable.
### IAM least privilege
Always scope policies to specific resources:
```json
{
"Effect": "Allow",
"Action": ["s3:GetObject", "s3:PutObject"],
"Resource": "arn:aws:s3:::my-bucket/*"
}
```
## GCP
```bash
# Check current identity
gcloud auth list
gcloud config get-value project
# View logs
gcloud logging read "severity>=ERROR" --limit=50
# GKE
gcloud container clusters get-credentials my-cluster --zone us-central1-a
kubectl get nodes
```
## Azure
```bash
# Check current identity
az account show
# View resources
az resource list --output table
# AKS
az aks get-credentials --resource-group my-rg --name my-cluster
```
## Tooling Templates
- `tooling/cloud/aws/` — IAM, ECS, Lambda, S3 configs
- `tooling/cloud/gcp/` and `tooling/cloud/azure/` — guidance only; no bundled configs
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · tspry/superpowers-devops | 100 | MIT |
| nikospavlopoulos/devops-mutant-powers | 100 | MIT |
Database snapshot: 13.11.2026 · package version 2bb5e141833f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100cloud-architect
Designs multi-cloud and hybrid cloud architectures across AWS, GCP, and Azure. Use when designing cloud infrastructure or when the user mentions cloud architecture, AWS, GCP, Azure, or multi-cloud. - 100migration-gcp-to-aws
GCP to AWS migration guidance with service mappings, gotchas, and assessment. Use when migrating from Google Cloud Platform, mapping GCP services to AWS equivalents, assessing GCP environments, or planning GCP-to-AWS migrations. - 95devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code. - 100gcp-cloud-functions
Deploy serverless functions on Google Cloud Functions. Configure triggers and manage deployments. Use when implementing serverless workloads on GCP. - 100gcp-cloud-functions
Deploy serverless functions on Google Cloud Functions. Configure triggers and manage deployments. Use when implementing serverless workloads on GCP. - 100gcp-cloud-functions
Deploy serverless functions on Google Cloud Functions. Configure triggers and manage deployments. Use when implementing serverless workloads on GCP.