packer-cn/website/content/partials/builder/amazon/ebssurrogate/Config-required.mdx

<!-- Code generated from the comments of the Config struct in builder/amazon/ebssurrogate/builder.go; DO NOT EDIT MANUALLY -->

- `ami_root_device` (RootBlockDevice) - A block device mapping describing the root device of the AMI. This looks
  like the mappings in `ami_block_device_mapping`, except with an
  additional field:
  
  -   `source_device_name` (string) - The device name of the block device on
      the source instance to be used as the root device for the AMI. This
      must correspond to a block device in `launch_block_device_mapping`.
initial port 2020-03-18 18:46:47 -04:00			`<!-- Code generated from the comments of the Config struct in builder/amazon/ebssurrogate/builder.go; DO NOT EDIT MANUALLY -->`

📌 Hard Pin Website Dependencies (#9543) * Update and pin dependencies * Update NextJS Scripts * npm run lint * npm run format * docs generator: indent docs by two and make spacing better Co-authored-by: Adrien Delorme <azr@users.noreply.github.com> 2020-07-13 06:33:16 -04:00			- `ami_root_device` (RootBlockDevice) - A block device mapping describing the root device of the AMI. This looks
			like the mappings in `ami_block_device_mapping`, except with an
			`additional field:`
Document exception to encryption (#10395) * Update docs on ebs encrypt_boot to clarify that packer will not override global account settings * Update struct-markdown generator and regenerate partials with new website location. This overwrites some linting that got automatically applied when the files got moved 2020-12-16 01:35:34 -08:00
			- `source_device_name` (string) - The device name of the block device on
			`the source instance to be used as the root device for the AMI. This`
			must correspond to a block device in `launch_block_device_mapping`.