Given these requirements, which steps should be taken together to enable a scalable architecture for the application servers?
(Choose two.)
Create a pool of ENIs, request license files from the vendor for the pool, and store the license files within Amazon S3. Create automation to download an unused license, and attach the corresponding ENI at boot time.
Create a pool of ENIs, request license files from the vendor for the pool, store the license files on an Amazon EC2 instance, modify the configuration files, and create an AMI from the instance. use this AMI for all instances.
Create a bootstrap automation to request a new license file from the vendor with a unique return email. Have the server configure itself with the received license file.
Create bootstrap automation to attach an ENI from the pool, read the database IP addresses from AWS Systems Manager Parameter Store, and inject those parameters into the local configuration files. Keep SSM up to date using a Lambda function.
Install the application on an EC2 instance, configure the application, and configure the IP address information. Create an AMI from this instance and use if for all instances.
Explanations:
Creating a pool of Elastic Network Interfaces (ENIs) allows for the reuse of MAC addresses, which is essential for the license files tied to the MAC address. By automating the process to download and attach an unused ENI at boot time, the application can scale horizontally while adhering to the licensing requirements.
While creating a pool of ENIs is a good strategy, modifying configuration files and creating an AMI from an instance with static IPs does not resolve the issue of needing unique MAC addresses for each instance to comply with licensing. Additionally, storing license files on an EC2 instance does not address the problem of scaling.
This option suggests requesting a new license file for each server at boot time. However, the 12-hour turnaround for license files from the vendor would lead to downtime and make scaling difficult, as new servers would not be able to start and operate until the license is received.
This option addresses the need for attaching an ENI from the pool for MAC address consistency and dynamically retrieves database IP addresses from AWS Systems Manager Parameter Store, allowing for easy scaling and updates to configuration without hardcoding IPs.
While installing the application on an EC2 instance and creating an AMI is valid for deployment, it does not address the licensing issue tied to unique MAC addresses or the requirement for static IP addresses. Each instance would not have the necessary licenses unless a valid solution for license management is implemented.
I have a feeling that the answer is:
Create a pool of ENIs, request license files from the vendor for the pool, and store the license files within Amazon S3. Create automation to download an unused license, and attach the corresponding ENI at boot time.