AWS ARN Parser

AWS ARN Parser & Builder

Decompose any Amazon Resource Name into its parts, or assemble one from form fields. Covers IAM, S3, Lambda, EC2, RDS, DynamoDB, SQS, SNS, KMS, ECR, EKS, CloudWatch Logs.

Decomposed
partitionaws
servicelambda
regionus-east-1
account123456789012
resource typefunction
resource idmy-function
resource pathfunction:my-function
Service: lambda
Format: function:<name>[:<version-or-alias>]
Regional: yes
Account required: yes
Examples
Sanity checks
  • partition aws
  • region us-east-1
  • account 123456789012
Try a sample

What This Tool Does

AWS ARN Parser is built for deterministic developer and agent workflows.

Decompose any AWS ARN into partition, service, region, account, resource type, and resource ID. Or build an ARN from form fields with copy-to-clipboard. Covers IAM, S3, Lambda, EC2, RDS, and more.

Use How to Use for execution steps and FAQ for constraints, policies, and edge cases.

Last updated:

This tool is provided as-is for convenience. Output should be verified before use in any production or critical context.

Agent Invocation

Best Path For Builders

Browser workflow

Runs instantly in the browser with private local processing and copy/export-ready output.

Browser Workflow

This tool is optimized for instant in-browser execution with local data handling. Run it here and copy/export the output directly.

/aws-arn-parser/

For automation planning, fetch the canonical contract at /api/tool/aws-arn-parser.json.

How to Use AWS ARN Parser

  1. 1

    Paste an ARN

    Drop any AWS ARN into the input box and the parser splits it into partition, service, region, account, resource type, and resource id. Sample ARNs for each supported service are one click away.

  2. 2

    Read the decomposition

    Each segment is shown on its own row with the original ARN preserved at the bottom. Sanity checks flag non-standard partitions, account IDs that are not 12 digits, and unrecognized regions.

  3. 3

    Switch to Build mode

    Use the Build tab to assemble an ARN from form fields. Datalists suggest known services and regions. The output updates live and is validated against the embedded service format catalog.

  4. 4

    Copy to clipboard

    Click Copy to grab either the input ARN or your built ARN. Paste into IAM policies, CloudFormation, Terraform, or scripts without retyping a single character of the format.

  5. 5

    Cross-reference the format

    When a service pattern is recognized, the right pane shows the canonical resource format and example ARNs from the docs. Useful when you remember the service but not whether it is db: or db/.

Frequently Asked Questions

What is AWS ARN Parser?
It decomposes any AWS ARN into partition, service, region, account, resource type, and resource id, and can build a new ARN from form fields. Covers IAM, S3, Lambda, EC2, RDS, DynamoDB, SQS, SNS, KMS, ECR, and EKS.
Does it work with non-standard partitions?
Yes. The aws, aws-cn (China), and aws-us-gov partitions are all supported in both parse and build modes. Other partition strings parse without error but get flagged in sanity checks.
Does it send my data to a server?
No. Parsing and building happen entirely in your browser. ARNs often contain account IDs and resource names, so keeping them local matters.
How does it tell resource type from resource id?
It splits on the first slash or colon after the account segment. So function:my-fn becomes type=function id=my-fn, while role/Admin becomes type=role id=Admin. Both forms are common in AWS docs.
Can I round-trip an ARN through Build mode?
Yes. Paste an ARN in Parse mode, then switch to Build and the structure is shown side by side. Useful for templating: change the account or region field and copy the new ARN to paste into IaC.