Registers an AMI. When you're creating an instance-store backed AMI, registering the AMI is the final step in the creation process. For more information about creating AMIs, see Create an AMI from a snapshot and Create an instance-store backed AMI in the Amazon EC2 User Guide.
See https://www.paws-r-sdk.com/docs/ec2_register_image/ for full documentation.
Usage
ec2_register_image(
ImageLocation = NULL,
BillingProducts = NULL,
BootMode = NULL,
TpmSupport = NULL,
UefiData = NULL,
ImdsSupport = NULL,
TagSpecifications = NULL,
DryRun = NULL,
Name,
Description = NULL,
Architecture = NULL,
KernelId = NULL,
RamdiskId = NULL,
RootDeviceName = NULL,
BlockDeviceMappings = NULL,
VirtualizationType = NULL,
SriovNetSupport = NULL,
EnaSupport = NULL
)Arguments
- ImageLocation
The full path to your AMI manifest in Amazon S3 storage. The specified bucket must have the
aws-exec-readcanned access control list (ACL) to ensure that it can be accessed by Amazon EC2. For more information, see Canned ACL in the Amazon S3 Service Developer Guide.- BillingProducts
The billing product codes. Your account must be authorized to specify billing product codes.
If your account is not authorized to specify billing product codes, you can publish AMIs that include billable software and list them on the Amazon Web Services Marketplace. You must first register as a seller on the Amazon Web Services Marketplace. For more information, see Getting started as an Amazon Web Services Marketplace seller and AMI-based products in Amazon Web Services Marketplace in the Amazon Web Services Marketplace Seller Guide.
- BootMode
The boot mode of the AMI. A value of
uefi-preferredindicates that the AMI supports both UEFI and Legacy BIOS.The operating system contained in the AMI must be configured to support the specified boot mode.
For more information, see Instance launch behavior with Amazon EC2 boot modes in the Amazon EC2 User Guide.
- TpmSupport
Set to
v2.0to enable Trusted Platform Module (TPM) support. For more information, see NitroTPM in the Amazon EC2 User Guide.- UefiData
Base64 representation of the non-volatile UEFI variable store. To retrieve the UEFI data, use the
get_instance_uefi_datacommand. You can inspect and modify the UEFI data by using the python-uefivars tool on GitHub. For more information, see UEFI Secure Boot for Amazon EC2 instances in the Amazon EC2 User Guide.- ImdsSupport
Set to
v2.0to indicate that IMDSv2 is specified in the AMI. Instances launched from this AMI will haveHttpTokensautomatically set torequiredso that, by default, the instance requires that IMDSv2 is used when requesting instance metadata. In addition,HttpPutResponseHopLimitis set to2. For more information, see Configure the AMI in the Amazon EC2 User Guide.If you set the value to
v2.0, make sure that your AMI software can support IMDSv2.The tags to apply to the AMI.
To tag the AMI, the value for
ResourceTypemust beimage. If you specify another value forResourceType, the request fails.To tag an AMI after it has been registered, see
create_tags.- DryRun
Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is
DryRunOperation. Otherwise, it isUnauthorizedOperation.- Name
[required] A name for your AMI.
Constraints: 3-128 alphanumeric characters, parentheses (()), square brackets ([]), spaces ( ), periods (.), slashes (/), dashes (-), single quotes ('), at-signs (@), or underscores(_)
- Description
A description for your AMI.
- Architecture
The architecture of the AMI.
Default: For Amazon EBS-backed AMIs,
i386. For instance store-backed AMIs, the architecture specified in the manifest file.- KernelId
The ID of the kernel.
- RamdiskId
The ID of the RAM disk.
- RootDeviceName
The device name of the root device volume (for example,
/dev/sda1).- BlockDeviceMappings
The block device mapping entries.
If you specify an Amazon EBS volume using the ID of an Amazon EBS snapshot, you can't specify the encryption state of the volume.
If you create an AMI on an Outpost, then all backing snapshots must be on the same Outpost or in the Region of that Outpost. AMIs on an Outpost that include local snapshots can be used to launch instances on the same Outpost only. For more information, Create AMIs from local snapshots in the Amazon EBS User Guide.
- VirtualizationType
The type of virtualization (
hvm|paravirtual).Default:
paravirtual- SriovNetSupport
Set to
simpleto enable enhanced networking with the Intel 82599 Virtual Function interface for the AMI and any instances that you launch from the AMI.There is no way to disable
sriovNetSupportat this time.This option is supported only for HVM AMIs. Specifying this option with a PV AMI can make instances launched from the AMI unreachable.
- EnaSupport
Set to
trueto enable enhanced networking with ENA for the AMI and any instances that you launch from the AMI.This option is supported only for HVM AMIs. Specifying this option with a PV AMI can make instances launched from the AMI unreachable.