You must migrate a legacy on-premises application to AWS. The application runs on two servers behind a load balancer. The software requires a license file tied to the server NIC MAC address; the vendor takes 12 hours to issue a new license file. The application also uses configuration files that reference the database server by static IP address (hostnames are not supported). Which combination of steps will provide a highly available architecture for the application servers in AWS? (Choose two.)

The first correct option addresses the MAC address licensing constraint. By creating a pool of ENIs, each with a unique MAC address, and pre-requesting licenses for them, instances can attach a pre-licensed ENI at boot. Storing licenses in S3 ensures availability. This avoids the 12-hour vendor delay during instance launches, crucial for high availability. The second correct option solves the static IP dependency. Using AWS Systems Manager Parameter Store allows central management of the database IP. A bootstrap script can retrieve this IP and update configuration files during instance initialization, ensuring instances always connect to the correct database without hardcoding the IP into AMIs. The incorrect options fail to meet the requirements. Creating an AMI with pre-licensed ENIs or hardcoded IPs is not scalable or highly available; it doesn't account for new instances or IP changes. Requesting a new license at launch introduces unacceptable delays.