I saw there was another thread about issues with cloud registration. Is this an resurfaced issue?

The system has internet connectivity and can reach the SMT but receives a forbidden.

This was tested with AMI (ami-8b559e9d) in us-east-1.

Last login: Thu May 18 16:59:23 2017 from
SUSE Linux Enterprise Server 12 SP2 for SAP Applications x86_64 (64-bit)

As "root" (sudo or sudo -i) use the:
  - zypper command for package management
  - yast command for configuration management

Management and Config: https://www.suse.com/suse-in-the-cloud-basics
Documentation: http://www.suse.com/documentation/sles12/
Forum: https://forums.suse.com/forumdisplay.php?93-SUSE-Public-Cloud

Have a lot of fun... or not :)
ec2-user@sles-test-02:~> cat /var/log/cloudregister
2017-05-18 16:57:50,005 INFO:Using API: regionInfo
2017-05-18 16:57:50,005 INFO:Using region server:
2017-05-18 16:57:50,009 INFO:Starting new HTTPS connection (1):
2017-05-18 16:57:50,779 INFO:Starting new HTTP connection (1):
2017-05-18 16:57:50,924 INFO:Modified /etc/hosts, added:     smt-ec2.susecloud.net   smt-ec2

2017-05-18 16:57:52,502 INFO:[Service] No SMT server found, nothing to do
2017-05-18 16:57:52,537 INFO:Writing SMT rootCA: /usr/share/pki/trust/anchors
2017-05-18 16:57:52,540 INFO:Starting new HTTP connection (1):
2017-05-18 16:57:52,544 INFO:Updating CA certificates: update-ca-certificates
ec2-user@sles-test-02:~> zypper lr
Repository priorities are without effect. All enabled repositories share the same priority.

# | Alias                   | Name                    | Enabled | GPG Check | Refresh
1 | nVidia-Driver-SLE12-SP2 | nVidia-Driver-SLE12-SP2 | No      | ----      | ----
ec2-user@sles-test-02:~> wget https://smt-ec2.susecloud.net
--2017-05-18 17:02:47--  https://smt-ec2.susecloud.net/
Resolving smt-ec2.susecloud.net (smt-ec2.susecloud.net)...
Connecting to smt-ec2.susecloud.net (smt-ec2.susecloud.net)||:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2017-05-18 17:02:47 ERROR 403: Forbidden.

ec2-user@sles-test-02:~> sudo /usr/sbin/registercloudguest --force-new
/usr/lib/python2.7/site-packages/requests/packages/urllib3/connection.py:264: SubjectAltNameWarning: Certificate for has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
Traceback (most recent call last):
  File "/usr/sbin/registercloudguest", line 367, in <module>
    if len(failed_smts) == len(known_smt_servers):
NameError: name 'known_smt_servers' is not defined