Cloud developer tools
Cloud work involves a lot of identifiers and signed requests that are hard to read at a glance: an ARN with five colon-separated fields, an IAM policy with statements nested across services, a SigV4 request that fails with SignatureDoesNotMatch and no further detail, an S3 address in the wrong format for the SDK you're using. These tools take those opaque strings apart so you can see what they actually say.
The AWS tools cover the identifiers you hit daily: the AWS ARN Parser & Builder reads ARNs in bulk or assembles one from its five fields, the IAM policy viewer groups statements by actions and resources, and the S3 URL converter switches an address between path-style and virtual-hosted-style. When a signed request is rejected, the AWS SigV4 Debugger rebuilds the canonical request to find the mismatch. Azure resource parser and GCP resources & GCS URLs handle the equivalent job for the other two clouds.
9 tools
AWS identifiers and requests
-
AWS ARN Parser & Builder
Parse AWS ARN identifiers in bulk or assemble them from five fields
-
AWS SigV4 Debugger
Build AWS SigV4 canonical requests to diagnose signature mismatches
-
S3 URL converter
Parse S3 addresses and convert between path and virtual-hosted formats
-
IAM policy viewer
Extract and group IAM policy statements with actions and resources
-
CloudFormation template validator
Check CloudFormation templates for syntax and reference errors
Cloud Dev Helpers tools FAQ
SigV4 signatures break on small formatting mismatches: an unencoded character, a header left out of the signed set, or a canonical request built in the wrong order. The AWS SigV4 Debugger rebuilds the canonical request from your inputs so you can compare it against what your client actually sent.
An ARN packs partition, service, region, account ID and resource into one colon-separated string, and the resource part's format varies by service. The AWS ARN Parser & Builder splits ARNs into those five fields in bulk, or builds a valid ARN back up from them.
Path-style puts the bucket name in the URL path, while virtual-hosted-style puts it in the hostname, and some SDKs and regions expect one specifically. The S3 URL converter parses either format and converts an S3 address between the two.