PAS-C01 · Question #93
A company runs a three-system SAP S/4HANA landscape on Amazon EC2 instances. The landscape includes a development system, a QA system, and a production system. Each system runs on its own EC2…
The correct answer is A. An appropriate instance profile that contains the AmazonSSMManagedInstanceCore policy is not C. Systems Manager Agent (SSM Agent) is not installed on the EC2 instances. AWS Systems Manager requires two things to register and manage an EC2 instance: (1) the SSM Agent must be installed and running on the instance (Option C) - without it, the instance has no means to communicate with the Systems Manager service endpoint; and (2) the instance must…
Question
A company runs a three-system SAP S/4HANA landscape on Amazon EC2 instances. The landscape includes a development system, a QA system, and a production system. Each system runs on its own EC2 instance. The production instance hosts a critical system that must run 24 hours a day, 7 days a week. The development instance and the QA instance need to run only during business hours and can be stopped for the rest of the day. An SAP administrator plans to use AWS Systems Manager to implement an automated start-stop solution for the development instance and the QA instance. When the SAP administrator attempts to deploy the solution, the SAP administrator cannot find any SAP S/4HANA systems in Systems Manager. Which options are possible causes of this problem? (Choose two.)
Options
- AAn appropriate instance profile that contains the AmazonSSMManagedInstanceCore policy is not
- BThe EC2 instances are attached to a security group that has an outbound rule that does not
- CSystems Manager Agent (SSM Agent) is not installed on the EC2 instances.
- DThe AWS Data Provider for SAP agent is not installed on the EC2 instances.
- EAmazon CloudWatch detailed monitoring is not turned on for the EC2 instances.
How the community answered
(36 responses)- A89% (32)
- B6% (2)
- D3% (1)
- E3% (1)
Explanation
AWS Systems Manager requires two things to register and manage an EC2 instance: (1) the SSM Agent must be installed and running on the instance (Option C) - without it, the instance has no means to communicate with the Systems Manager service endpoint; and (2) the instance must have an IAM instance profile that includes the AmazonSSMManagedInstanceCore managed policy (Option A) - without the correct permissions, the SSM Agent cannot authenticate to the service. Option B (outbound security group rules) could block SSM if port 443 is blocked, but this would cause a connection error rather than the system simply not appearing; moreover, the question implies other deployments worked, making this less likely. Option D (AWS Data Provider for SAP) is unrelated to SSM registration. Option E (CloudWatch detailed monitoring) has no bearing on SSM connectivity.
Topics
Community Discussion
No community discussion yet for this question.