AWS ARN Parser
Parse AWS ARN partition, service, region, account, resource type, ID, and qualifier
Parses ARN structure and common service constraints locally. It does not call AWS APIs or verify resource existence or permissions.
Partition, service, region, account, and resource will appear here.
About this tool
Split an ARN at its first five colons into partition, service, region, account and a raw service-specific resource. Leading whitespace is removed; spaces within or at the end of Resource are preserved, including S3 object keys. Common regionless and accountless S3 bucket/object forms receive a specific interpretation; regional S3 resources such as access points retain their resource type instead of being labelled as buckets. Generic colon/slash splitting is only a reading aid for service-specific grammar. Warnings cover selected account, partition and service conventions. The parser neither calls AWS nor checks resource existence, IAM permissions or complete service schemas. Editing the input clears the report; no ARN draft is stored.
Scenario Recipes
Review an IAM policy resource reference
Goal: Catch an account, region, or resource-type typo before policy deployment
- Paste the Resource ARN from the policy statement.
- Compare partition, service, account, region, resource type, and qualifier with the deployment target.
- Resolve warnings against current service documentation, then test the policy through the approved AWS review process.
Result: A field-by-field ARN review without requiring cloud credentials.
Frequently Asked Questions
What are the main ARN fields?
An ARN contains arn, partition, service, region, account ID, and a service-specific resource section.
Why can the resource contain more colons?
The first five colons delimit generic fields; everything after them belongs to service-specific resource grammar.
Does every ARN require region and account ID?
No. Global services and resources such as common S3 bucket ARNs can leave one or both fields empty.
Can the parser verify that a resource exists?
No. It performs local structural checks and never calls AWS or requests credentials.
Are warnings definitive validation errors?
No. They flag common conventions; consult current service documentation for specialized or newly introduced ARN forms.
Is the ARN uploaded?
No. Splitting, field extraction, JSON generation, and checks happen locally.
Keep browsing