Version dates
'2010-09-09' and '2012-10-17' stay strings rather than becoming YAML 1.1 dates.
Convert AWS CloudFormation templates to YAML that deploys exactly like the JSON original.
Each line of the output, in default formatting, next to the path of the value it holds. Click a row to copy the path.
Runs entirely in your browser, so nothing is uploaded. Fair-use limits apply (5 MB per input, rate-limited conversions) to prevent spam and bots.
Ref, Fn::Sub and Fn::GetAtt are written in their full form, which CloudFormation reads in YAML exactly as in JSON.
BucketName:
Fn::Sub: assets-${Environment}
Tags:
- Key: env
Value:
Ref: Environment
Resource:
Fn::GetAtt:
- AssetsBucket
- Arn BucketName: !Sub 'assets-${Environment}'
Tags:
- Key: env
Value: !Ref Environment
Resource: !GetAtt AssetsBucket.Arn Both versions deploy identically. Short-form tags are a CloudFormation extension, so the converter keeps the full form that any YAML tool can read.
The sample template is 36% smaller as YAML than as pretty-printed JSON, with no braces or quotes to scan past in a review.
# Validate the converted template with the AWS CLI
aws cloudformation validate-template --template-body file://template.yaml Compare the converter's output with the same template values written by hand, without quotes.
'2010-09-09' and '2012-10-17' stay strings rather than becoming YAML 1.1 dates.
${AWS::AccountId} placeholders inside Fn::Sub are kept character for character.
Inline IAM policies convert like the rest of the template, so actions and resources read as clean lists.
Converters, validators and step-by-step guides for every place JSON and YAML meet.
Paste the template JSON or upload template.json. Copy the YAML or download template.yaml, then deploy it like any other template. Resources, parameters and outputs stay exactly the same.
No. The converter writes the full form (Ref:, Fn::Sub:, Fn::GetAtt:), which CloudFormation accepts in YAML templates and which every YAML parser can read. The short-form tags are optional shorthand.
An unquoted 2010-09-09 is a date in YAML 1.1. CloudFormation expects the string, so the converter writes '2010-09-09'. IAM policy versions like '2012-10-17' are quoted for the same reason.
Yes, for templates in full-form syntax: switch the direction to YAML → JSON. Templates written with short-form tags such as !Ref need a CloudFormation-aware tool, because those tags are not standard YAML types.
Yes. Conversion runs in your browser and nothing is uploaded or logged, so account IDs, ARNs and parameter defaults stay on your machine.