Dev
Mock Cloud Resource ID Generator
Cloud resource IDs follow strict, provider-specific conventions that are easy to get wrong when writing them by hand: AWS ARNs use colon-separated segments with account IDs and partition names, GCP uses hierarchical slash-separated paths rooted at projects/{project-id}, and Azure uses long slash-separated paths starting at /subscriptions/{guid}. This generator produces correctly-formatted fake identifiers for all three providers so you can populate test fixtures, documentation, and mock API responses with IDs that pass format validation without pointing at any real account. The provider dropdown selects AWS, GCP, Azure, or All. AWS output covers EC2 instances, S3 buckets, Lambda functions, IAM roles, RDS databases, SQS queues, and SNS topics as ARNs. GCP output covers Compute instances, Cloud Storage buckets, Pub/Sub topics, Firestore documents, and Cloud Functions as resource paths. Azure output covers virtual machines, storage accounts, App Service sites, and SQL servers as full Resource Manager paths. All mode draws from all three providers in a mixed batch. The count input generates between 1 and 20 IDs per run. Use these to test an IAM policy parser against correctly-typed ARNs, fill Terraform module documentation with plausible resource references, or seed a cloud cost dashboard UI with varied provider data.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Choose a cloud provider — AWS, GCP, or Azure — or select All for a mixed set.
- Set how many resource identifiers you need.
- Click Generate to produce realistically-formatted fake resource IDs.
- Copy the IDs into your test fixtures, mock responses, or documentation.
Use Cases
- •Populating a cloud cost dashboard UI with realistic-looking AWS ARN sample data
- •Testing an IAM policy parser against correctly formatted multi-provider resource identifiers
- •Filling Terraform module README examples with plausible GCP resource path references
- •Seeding a mock Azure inventory database for Cypress integration tests
- •Building multi-cloud infrastructure tutorials without exposing real subscription IDs
Tips
- →Match the provider to the SDK or API your code targets so the ID format is realistic.
- →Use these to test parsing and validation, never to reference a real cloud resource.
- →Generate a varied batch to confirm your code handles different providers' ID shapes.
- →Pair with a mock API response generator to build complete, believable cloud fixtures.
- →Keep generated IDs out of production config — they point at nothing real.
FAQ
what does a valid AWS ARN actually look like
An ARN follows the pattern arn:partition:service:region:account-id:resource — for example, arn:aws:s3:::my-bucket. The generator produces ARNs matching this structure with randomised account IDs and regions, so they pass format validation without pointing to a real account.
can these fake resource IDs break anything if accidentally used in real cloud configs
No — the account IDs, project slugs, and subscription GUIDs are randomly generated and won't match any real cloud account. That said, always double-check before committing IaC files to production pipelines.
what's the difference between AWS ARNs, GCP resource paths, and Azure resource IDs
AWS ARNs use a colon-separated flat string starting with arn:; GCP uses a hierarchical slash-separated path like projects/{project}/locations/{region}/...; Azure uses a long slash-separated path rooted at /subscriptions/{guid}. Each format is provider-specific and this generator handles all three correctly.
which AWS resource types does the generator cover
AWS output includes ARNs for EC2 instances, S3 buckets, Lambda functions, IAM roles, RDS databases, SQS queues, and SNS topics. Each run draws one type at random, so generating multiple IDs gives you a mix across these resource categories.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.