Which deployment strategy meets these requirements?
Use AWS Systems Manager to create a new AMI with the updated OS patches. Update the Auto Scaling group to use the patched AMI and replace existing unpatched instances. Use AWS CodeDeploy to push the application code to the instances. Store the static data in Amazon EFS.
Use AWS Systems Manager to create a new AMI with updated OS patches. Update the Auto Scaling group to use the patched AMI and replace existing unpatched instances. Update the OS patches and the application code as batch job every night. Store the static data in Amazon EFS.
Use an Amazon-provided AMI for the OS. Configure an Auto Scaling group set to a static instance count. Configure an Amazon EC2 user data script to download the data from Amazon S3. Install OS patches with AWS Systems Manager when they are released. Use AWS CodeDeploy to push the application code to the instances.
Use an Amazon-provided AMI for the OS. Configure an Auto Scaling group. Configure an Amazon EC2 user data script to download the data from Amazon S3. Replace existing instances after each updated Amazon-provided AMI release. Use AWS CodeDeploy to push the application code to the instances.
Explanations:
This option meets all requirements: it uses AWS Systems Manager for AMI creation and patching, ensuring OS patches are applied quickly. The Auto Scaling group allows scaling based on demand. AWS CodeDeploy enables frequent code updates, and Amazon EFS can handle the 500 GB static dataset, which is accessible to all instances.
While it addresses patching and scaling, the strategy of updating OS patches and application code as a batch job every night does not allow for rapid updates or immediate application of patches within 48 hours, which is a requirement. Additionally, this could introduce delays in deployment and scaling responsiveness.
This option sets a static instance count for the Auto Scaling group, which does not meet the requirement for dynamic scaling based on demand. The user data script for downloading from S3 could introduce latency during startup, and the patching process might not guarantee compliance within the 48-hour window since it relies on AWS Systems Manager without a specified update frequency.
Although it uses an Auto Scaling group and CodeDeploy for code updates, replacing instances only after each updated Amazon-provided AMI release does not address the requirement for immediate OS patching within 48 hours. Moreover, it lacks flexibility in scaling since the Auto Scaling group needs to adapt to varying demands, which this option does not facilitate.
I think the answer is:
Use AWS Systems Manager to create a new AMI with the updated OS patches. Update the Auto Scaling group to use the patched AMI and replace existing unpatched instances. Use AWS CodeDeploy to push the application code to the instances. Store the static data in Amazon EFS.