Elysia Tools
Navigation
Workflow Playbook
Check IPv4 and IPv6 addresses, CIDR values, MAC addresses, AWS ARNs, and Docker image references before downstream processing, while keeping format evidence separate from reachability, ownership, permissions, and image availability.
Hubs
This workflow is useful when a manifest, inventory export, form, or configuration contains several infrastructure identifier families. Begin with the raw value and its source field. Decide whether it is an IP or CIDR value, a MAC address, an AWS ARN, or a Docker image reference before selecting a validator.
Use ip-address-validator for IPv4, IPv6, and supported CIDR notation. Use mac-address-validator when a hardware identifier may use colon, hyphen, Cisco-style, or compact separators. Keep the input as received beside any normalized representation so a reviewer can distinguish a harmless display difference from a real parsing failure.
For cloud and container strings, aws-arn-validator checks ARN structure and docker-image-tag-validator checks image reference naming, repository paths, tags, and digests. Failures such as bad octets, an invalid prefix length, malformed separators, missing ARN components, or illegal image names should return to the source record for correction.
A format pass is a useful gate for parsing and configuration, but it is not a live infrastructure claim. It does not establish that an IP answers, a MAC is attached to a particular device, an ARN names an existing resource or grants access, or an image is present and pullable from a registry. For those questions, continue in network-triage-debugging, network-convert, or an authorized cloud and registry process. The broader validation-format workflow is a useful neighboring path when the identifier is not one of these four families.
Workflow playbook
Create a small table with the source field, raw value, expected family, and any environment or naming convention. Route each row to one of the four validators before changing its presentation.
Use the IP validator for IPv4, IPv6, and supported CIDR notation, then use the MAC validator for colon, hyphen, Cisco-style, or compact presentations. Keep raw and normalized forms side by side and investigate version, separator, or component errors.
Send AWS resource strings to the ARN validator and image references such as registry, repository, tag, or digest forms to the Docker validator. Review each structural field instead of treating a generic valid flag as a complete deployment check.
Record the exact rejected value, failed rule, corrected candidate, and reviewer decision. Only after the format gate passes should an authorized owner run separate network, inventory, IAM, or registry checks that answer questions this workflow cannot answer.
Route IPv4, IPv6, and CIDR candidates to ip-address-validator, MAC representations to mac-address-validator, AWS resource strings to aws-arn-validator, and image references to docker-image-tag-validator. A field label alone is not enough when imported data is ambiguous.
Trim surrounding whitespace only when that rule is documented. Preserve the raw value, CIDR prefix, MAC separators, ARN components, registry path, tag, and digest so the review can be reproduced and formatting loss is visible.
Use a pass to clear a syntax or structure gate only. If the next decision concerns reachability, device ownership, AWS existence or permissions, or whether a registry contains an image, hand off to an authorized operational check.