新手求助：如何基于已有EC2实例生成CloudFormation的YML/JSON模板？

Hey there! I get that figuring out how to turn an existing EC2 instance into a CloudFormation template can be tricky when you're just starting out—especially since launch templates don't let you export directly to YAML/JSON for CFN. Let's break down the easiest methods for you, step by step.

This is the most straightforward way if you prefer a GUI:

• Open the AWS CloudFormation console
• On the left sidebar, click Stacks, then select Create stack > With existing resources (import resources)
• Click Next, then in the "Identify resources" step, pick EC2 Instance as the resource type, enter your instance ID, and hit Next
• The console will automatically generate a basic CFN template (you can toggle between YAML and JSON in the editor)
• Even if you don't want to actually create a stack right now, you can copy the generated template from the editor and tweak it to add missing details like tags, security group associations, or user data

If you're comfortable with the command line, this gives you a starting point to build your template:

• First, make sure your AWS CLI is set up with the right permissions (you'll need ec2:DescribeInstances at minimum)
• Run this command to export your instance's details to a YAML file:

  aws ec2 describe-instances --instance-ids YOUR_INSTANCE_ID --query 'Reservations[0].Instances[0]' --output yaml > ec2-instance-details.yaml
  

• Note: This isn't a ready-to-use CFN template yet—you'll need to adjust it:
  • Add the required CFN top-level fields: AWSTemplateFormatVersion: '2010-09-09' and a Resources section wrapping your EC2 instance definition
  • Map the exported properties to the official AWS::EC2::Instance CFN properties (like ImageId, InstanceType, SecurityGroupIds)
  • Remove auto-generated fields that CFN doesn't need, such as InstanceId, LaunchTime, or State

• The generated template might not include all linked resources (like attached EBS volumes, security groups, or IAM roles). You can repeat the import wizard or CLI steps for these resources and add them to your template.
• Always test your template in a non-production environment first—launch a test stack to make sure it creates an instance matching your original configuration.
• Don't forget critical details: user data scripts, IAM instance profiles, VPC/subnet settings, and tags are all important to include for an accurate template.

内容的提问来源于stack exchange，提问作者Kiwi Rupela