Why can't I register my EC2 instance running SUSE to the SUSE update infrastructure so that I can install or update packages?

Last updated: 2021-10-12

I want to install or update packages on my Amazon Elastic Compute Cloud (Amazon EC2) SUSE instance. I'm unable to register my EC2 SUSE instance to the SUSE update infrastructure. How do I troubleshoot this?

Short description

To troubleshoot SUSE registration failure, use the AWSSupport-CheckSUSERegisration automation document. This automation document does the following:

  1. Verifies security group configurations.
  2. Verifies network access control list (network ACL) configurations.
  3. Verifies route table configurations.
  4. Verifies that the cloud-regionsrc-client package is up to date.
  5. Verifies that the base product symbolic link is correct.
  6. Verifies that there aren't multiple entries for smt-ec2.susecloud.net in the /etc/hosts file.
  7. Verifies that your EC2 instance can access the Instance Metadata Service (IMDS).
  8. Verifies that your EC2 instance has a billing code or AWS Marketplace product codes.
  9. Determines if your EC2 instance is behind an SSL proxy.
  10. Determines if the regional server's IPs, SMT server's IPs, and smt-ec2.susecloud.net are allowed from the SSL interception if there is any proxy.
  11. Determines if the proxy can resolve smt-ec2.susecloud.net to an SMT server IP address.
  12. Determines if SMT servers are accessible over HTTP.
  13. Determines if SMT servers are accessible over HTTPS.
  14. Determines if the smt-ec2.susecloud.net URL is accessible over HTTPS.

Resolution

Before you begin

  • Keep in mind that the instance you want to troubleshoot using the automation document must be a managed instance in the AWS Systems Manager console.
  • Copy the instance ID of the EC2 instance you want to troubleshoot. You need the instance ID to run the automation document.
  • (Optional) Create and specify an AWS Identity and Access Management (IAM) role for automation. If you don't specify this role, AWS Systems Manager Automation uses the permissions of the user who runs this document. For more information about creating roles for automation, see Running an automation by using an IAM service role.

Run the AWSSupport-TroubleshootSUSERegistration automation from the Systems Manager console

  1. Open the document in the AWS Systems Manager console. Be sure to open the document in the Region where your resources are located.
  2. In the navigation pane, choose Automation.
  3. Choose Execute automation.
  4. Enter AWSSupport-TroubleshootSUSERegistration in the search field, and then press Enter.
  5. Select AWSSupport-TroubleshootSUSERegistration in the search results.
  6. In the documents list, choose AWSSupport-TroubleshootSUSERegistration. The document owner is Amazon.
  7. In the Description section, verify that Document version is set to Default version at runtime.
  8. Select Execute Automation.
  9. In the Execute automation document section, choose Simple execution.
  10. In the Input parameters section, specify the following parameters:
    For InstanceID, specify or select the ID of the instance you want to troubleshoot.
    (Optional) For AutomationAssumeRole, specify the IAM role for this run. If a role isn't specified, AWS Systems Manager Automation uses the permissions of the user who runs this document.
  11. Choose Execute.
  12. To monitor the run progress, choose the running Automation, and then choose the Steps tab. When the run finishes, choose the Descriptions tab, and then choose View output to view the results. To view the output of individual steps, choose the Steps tab, and then choose View Outputs beside a step.

Run the AWSSupport-TroubleshootSUSERegistration automation from the AWS Command Line Interface (AWS CLI)

In the following command, replace i-xxxxxxxxxxxxxxxx with the EC2 instance that you want to troubleshoot. Replace us-east-1 with your instance's Region.

aws ssm start-automation-execution --document-name "AWSSupport-TroubleshootSUSERegistration" --document-version "\$DEFAULT" --parameters '{"InstanceId":["i-xxxxxxxxxxxxxxxx"],"AutomationAssumeRole":[""]}' --region us-east-1

Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.


Did this article help?


Do you need billing or technical support?