A company uses an organization in AWS Organizations to manage a multi-account AWS environment. The company creates a new Amazon EBS backed Amazon Machine Image (AMI). The company shares the AMI across the organization. Employees must use the AMI to launch all new Linux-based Amazon EC2 instances across the entire organization. In one of the company's application accounts, an employee uses the new AMI to launch a new workload. The EC2 instance launches, but it is terminated immediately. What the MOST likely reason that the instance did not fully boot?
Select an option, then click Submit answer.
- ○ The user who launched the instance does not have ec2:RunInstances permissions within the application account.
- ○ The company encrypted the AMI by using an AWS KMS key that the user who launched the EC2 instance does not have access to.
- ○ There is a service control policy (SCP) that denies the user who launched the EC2 instance access to launch instances in the application account.
- ○ The user launched the EC2 instance into a subnet that does not have access to the internet.