Cloud Resource Identifier Workbench
Review a local list of concrete AWS ARNs and Azure resource IDs, with structured fields and exact duplicate witnesses.
Loading tool…
How to use Cloud Resource Identifier Workbench
Review a local list of concrete AWS ARNs and Azure resource IDs, with structured fields and exact duplicate witnesses. Separate account/region fields from opaque ARN resource text and identify Azure provider/child/extension chains. Keep malformed or out-of-profile rows visible without contacting either cloud.
- Provide one concrete arn or azure resource id per line.
- Choose the supported mode and run the tool. Review its assumptions and any reported errors.
- Copy the result or download a separate output; reset to clear the current form.
Good to know
- 100 KB UTF-8, 1–500 nonblank lines and 2,048 printable ASCII characters per identifier. A final newline is accepted; leading/trailing whitespace is not silently removed.
- Concrete identifiers only: no wildcard, IAM variable, percent-encoded segment, backslash, fragment or template syntax. This is a selected structural profile; other valid provider identifiers may be refused.
- ARN resource text remains opaque: the tool does not guess a universal resource type/name split or certify service-specific syntax. Azure accepts resource type/name pairs under subscription, resource-group or provider-root scopes, including repeated providers extension segments. Bare scopes are outside the profile.
- Duplicate detection compares exact supplied strings. The report does not establish provider identity equivalence, resource existence, ownership, permissions, authorization or API/version support.
- The separate JSON report is limited to 500,000 characters, including formatting; reduce the source if the report exceeds that bound.
- Inputs are processed on this device and are not automatically saved or uploaded.
Common questions
Does a parsed identifier prove the resource exists?
No. The report describes the selected spelling and path structure only. It makes no cloud API call, checks no credentials and cannot prove existence or authorization.
Does this change my original input?
No. The tool returns a separate result. Review that output before using it in another application.
Keep going with related tools
All developer →Kubernetes Resource Reference Explorer
Trace selected Pod-template references and potential Service label matches across a supplied local manifest bundle.
DeveloperURL Parser
Inspect HTTP(S) URL components, normalized hostnames, and repeated query parameters without visiting a link.
DeveloperOpenAPI Operation Contract Explorer
Inspect local OpenAPI 3.1 operations, effective parameters, declared security alternatives and selected reference diagnostics.