Console-to-Codeを使って色々なリソースを作ってみる#AWSreInvent

 Here is the generated CloudFormation YAML:

```yaml
Resources:

  TestLaunchTemplate: 
    Type: AWS::EC2::LaunchTemplate
    Properties:
      LaunchTemplateName: test
      LaunchTemplateData: 
        KeyName: test
        ImageId: ami-0fa1ca9559f1892ec  
        InstanceType: t3.nano
        MetadataOptions:
          HttpTokens: required
          HttpEndpoint: enabled
          HttpPutResponseHopLimit: 2
        NetworkInterfaces:
          - DeviceIndex: 0
            Groups: 
              - sg-0e5c79f8cc2096406
```

Reasoning:
- The aws ec2 create-launch-template command is used to create a new launch template, so I have mapped that to an AWS::EC2::LaunchTemplate resource in CloudFormation
- The launch template name, key name, AMI ID, instance type, metadata options, and network interface configuration are all translated from the CLI command options to LaunchTemplateData properties
- The security group ID is specified for the network interface, so I have included that in the Groups list under NetworkInterfaces
- I have included the minimum required properties to match the CLI command, avoiding adding anything extra not specified

 Here is the generated infrastructure as code:

```yaml
Resources:
  ConsoletocodeVolume: 
    Type: 'AWS::EC2::Volume'
    Properties:
      AvailabilityZone: us-east-1a
      Iops: 3000  
      Throughput: 125
      Size: 1
      VolumeType: gp3
      Tags:
        - Key: Name 
          Value: Consoletocode
```

Reasoning:
- Created a ConsoletocodeVolume resource of type AWS::EC2::Volume based on the aws ec2 create-volume CLI command.
- Set AvailabilityZone, Iops, Throughput, Size, VolumeType properties based on corresponding CLI parameters.
- Added a Name tag with value Consoletocode based on the --tag-specifications parameter in CLI command.

```yaml
Resources:
  DLMPolicy: 
    Type: AWS::DLM::LifecyclePolicy
    Properties:
      Description: Consoletest
      ExecutionRoleArn: arn:aws:iam::XXXXXXXXXXXX:role/service-role/AWSDataLifecycleManagerDefaultRole  
      State: ENABLED
      PolicyDetails: 
        PolicyType: EBS_SNAPSHOT_MANAGEMENT
        ResourceTypes: 
          - VOLUME
        TargetTags:
          - 
            Key: Name
            Value: console
        Schedules:
          - 
            Name: Schedule 1
            CreateRule:
              Interval: 12
              IntervalUnit: HOURS  
              Times: 
                - 09:00
            RetainRule: 
              Count: 1
```

Reasoning: The CLI command creates a DLM lifecycle policy, so I created a LifecyclePolicy resource in CloudFormation with the same properties as specified in the CLI command. I used the ExecutionRoleArn, Description, State, and PolicyDetails directly from the CLI. For PolicyDetails, I broke it down into the nested objects for PolicyType, ResourceTypes, TargetTags, and Schedules.

 Here is the generated infrastructure as code:

```yaml
Resources:
  ConsoleTestKeyPair: 
    Type: 'AWS::EC2::KeyPair'
    Properties:
      KeyName: consoletest
      KeyType: rsa
```

Reasoning: The aws ec2 create-key-pair CLI command creates an EC2 key pair resource, so I translated that into a CloudFormation resource of type AWS::EC2::KeyPair with matching properties for the key name, type and format specified in the CLI command.

 Here is the generated YAML CloudFormation code:

```yaml
Resources:

  MyAutoScalingGroup: 
    Type: AWS::AutoScaling::AutoScalingGroup
    Properties:
      AutoScalingGroupName: consoletest
      MaxSize: 1
      MinSize: 1
      DesiredCapacity: 1
      HealthCheckGracePeriod: 300
      DefaultInstanceWarmup: -1
      LaunchTemplate: 
        LaunchTemplateId: lt-023a1cfaac9c1152c
        Version: $Default
      VPCZoneIdentifier: 
        - subnet-011c33fa9a5ad441a
        - subnet-05462110c6d1e4e18
      HealthCheckType: EC2
```

Reasoning:
- Created an AWS::AutoScaling::AutoScalingGroup resource named MyAutoScalingGroup based on the CLI command provided
- Set the Properties to match the options specified in the CLI command, including AutoScalingGroupName, MaxSize, MinSize, DesiredCapacity, HealthCheckGracePeriod, DefaultInstanceWarmup, LaunchTemplateId, Version, VPCZoneIdentifier, and HealthCheckType
- Used a YAML list for the VPCZoneIdentifier property to match the multiple subnet IDs provided in the CLI command
- Omitted creation of other resources not specified in the CLI command