What must the SysOps administrator do to use the custom AMI in the additional Regions?
Copy the AMI to the additional Regions.
Make the AMI public in the Community AMIs section of the AWS Management Console.
Share the AMI to the additional Regions. Assign the required access permissions.
Copy the AMI to a new Amazon S3 bucket. Assign access permissions to the AMI for the additional Regions.
Explanations:
To use the custom AMI in other Regions, it must be copied to each of the desired Regions. This is done through the “Copy AMI” feature in the AWS Management Console, which allows an AMI to be made available in other Regions.
Making the AMI public in the Community AMIs section would expose the AMI to all AWS users, but it does not facilitate using the AMI in different Regions for a specific user. This is not the correct approach for the scenario.
Sharing an AMI with specific accounts or Regions does not directly solve the issue of making the AMI available in different Regions. Copying the AMI to those Regions is required.
The AMI itself is not stored in Amazon S3, but in the EC2 service. Copying it to an S3 bucket is unnecessary and incorrect, as the AMI must be copied within the EC2 service itself to other Regions.
I believe the answer is:
Copy the AMI to the additional Regions.