Given these requirements, which combination of steps should be taken to implement highly available architecture for the application servers in AWS?
(Choose two.)
Create a pool of ENIs. Request license files from the vendor for the pool, and store the license files in Amazon S3. Create a bootstrap automation script to download a license file and attach the corresponding ENI to an Amazon EC2 instance.
Create a pool of ENIs. Request license files from the vendor for the pool, store the license files on an Amazon EC2 instance. Create an AMI from the instance and use this AMI for all future EC2 instances.
Create a bootstrap automation script to request a new license file from the vendor .When the response is received, apply the license file to an Amazon EC2 instance.
Edit the bootstrap automation script to read the database server IP address from the AWS Systems Manager Parameter Store, and inject the value into the local configuration files.
Edit an Amazon EC2 instance to include the database server IP address in the configuration files and re-create the AMI to use for all future EC2 stances.
Explanations:
By creating a pool of ENIs, you can pre-request license files associated with each ENI. The bootstrap script can then automatically download and apply the correct license file for each new EC2 instance by attaching the appropriate ENI. This solution accommodates the need to retain the MAC address for licensing and handles the license file distribution.
Storing the license files on an EC2 instance is not ideal because it would tie the license to a specific instance, making scaling and failover difficult. Additionally, creating an AMI with the license already applied might violate the licensing terms or complicate the process for new instances.
Requesting a new license file on-demand could lead to significant delays, as it takes 12 hours to receive the new license. This approach doesn’t meet the requirement for high availability, as it introduces downtime during license acquisition.
Using AWS Systems Manager Parameter Store to store the database server IP and injecting it into the EC2 instance configuration ensures that the configuration is dynamic and can be updated without modifying AMIs. This is a more scalable and maintainable approach for managing static configurations like IP addresses.
Embedding the database server IP directly in an AMI is static and not scalable. This approach does not meet the requirements for high availability or flexibility in case the database IP needs to be changed. Parameter Store is a better option.
In my experience, the answer is:
Create a pool of ENIs. Request license files from the vendor for the pool, and store the license files in Amazon S3. Create a bootstrap automation script to download a license file and attach the corresponding ENI to an Amazon EC2 instance.