What should a solutions architect do to accomplish this?
Install the conversion software as an Amazon S3 batch operation so the data is transformed without leaving Amazon S3.
Install the conversion software onto an on-premises virtual machine. Perform the transformation and re-upload the files to Amazon S3 from the virtual machine.
Use AWS Snowball Edge devices to export the data and install the conversion software onto the devices. Perform the data transformation and re-upload the files to Amazon S3 from the Snowball Edge devices.
Launch an Amazon EC2 instance in the same Region as Amazon S3 and install the conversion software onto the instance. Perform the transformation and re- upload the files to Amazon S3 from the EC2 instance.
Explanations:
Amazon S3 batch operations allow you to manage large-scale tasks such as copying, tagging, and deleting objects but do not support running third-party software like the vendor’s proprietary conversion tool.
Installing the conversion software on an on-premises virtual machine means that data must be transferred from Amazon S3 to the on-premises environment, resulting in high data transfer charges. This option increases the cost and complexity.
AWS Snowball Edge is a physical device designed for large-scale data migrations. However, it would require a separate setup and would still incur costs for shipping and handling. It also would not optimize the re-upload to S3.
Launching an Amazon EC2 instance in the same AWS Region as the S3 bucket allows for local processing of the data, minimizing data transfer charges because the data does not leave the AWS network. The conversion can be done efficiently within the same region, and re-uploading the transformed files to S3 can be done with minimal cost.
I rank that the answer is:
Launch an Amazon EC2 instance in the same Region as Amazon S3 and install the conversion software onto the instance. Perform the transformation and re- upload the files to Amazon S3 from the EC2 instance.