AMI Naming Convention Compliance

AMI Naming Convention Compliance is a DevOps skill for Claude Code, published by CyberStrikeus in CyberStrike.

1.7K stars253 forkson CyberStrikeus/CyberStrikeAdded 2026/07/20+4% in starsRepository updated 2026/08/05

aiai-agentai-securitybug-bountycybersecuritydevsecopsethical-hackinghackinghacking-toolllmmcpmcp-servermitre-attackoffensive-securityowasppenetration-testingpentestred-teamsecuritysecurity-tools

Install in seconds

Install AMI Naming Convention Compliance

Copy AMI Naming Convention Compliance into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/CyberStrikeus/CyberStrike/tree/main/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/AWS/CIS_AWS_Compute_Services_Benchmark_v1.1.0/cis-aws-compute-2.1.1 ~/.claude/skills/cis-aws-compute-2.1.1

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/CyberStrikeus/CyberStrike.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .cyberstrike/skill/CIS_benchmarks/Cloud_Providers/AWS/CIS_AWS_Compute_Services_Benchmark_v1.1.0/cis-aws-compute-2.1.1/SKILL.md in CyberStrikeus/CyberStrike
Installs to: ~/.claude/skills/cis-aws-compute-2.1.1
Collection: One of 51 skills cataloged from this repository
Category: DevOps — 1075 skills

What AMI Naming Convention Compliance does

Checks that all Amazon Machine Images (AMIs) in your AWS account follow your organization's naming convention, helping maintain a consistent asset inventory.

AMI Naming Convention Compliance is cataloged under DevOps on DirSkills. AMI Naming Convention Compliance comes from a repository tagged ai, ai-agent, ai-security, bug-bounty and cybersecurity.

Documentation

README

Excerpt

Ensure Consistent Naming Convention is used for Organizational AMI

Description

The naming convention for AMI (Amazon Machine Images) should be documented and followed for any AMI's created.

The majority of AWS resources can be named and tagged. Most organizations have already created standardize naming conventions, and have existing rules in effect. They simply need to extend that for all AWS cloud resources to include Amazon Machine Images (AMI).

Impact

No significant operational impact. This is an organizational best practice that improves manageability and consistency of AMI resources.

Audit Procedure

Using AWS CLI

Run aws ec2 describe-images.

aws ec2 describe-images --owner self --region us-west-2

This is the opening of the README. Read the full README on GitHub.

Frequently asked about AMI Naming Convention Compliance

What else does CyberStrikeus publish alongside AMI Naming Convention Compliance?
AMI Naming Convention Compliance is one of 51 skills that DirSkills catalogs from CyberStrikeus/CyberStrike, the repository it ships in. Its siblings there include AMI Age Compliance, AMI Encryption Check and AWS Approved AMI Audit. Each one is a separate skill with its own page in this directory, installs the same way AMI Naming Convention Compliance does, and is maintained by CyberStrikeus in that same repository. The rest of the collection is listed on the CyberStrikeus/CyberStrike page.
How does AMI Naming Convention Compliance compare to other DevOps skills?
AMI Naming Convention Compliance ranks #291 by stars among the 1075 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of AMI Naming Convention Compliance against them. Open each page to compare what they document and how they install.