at AWS in Ireland (eu-west-1), we have a severe issue where we are booting suse ec2 instance in a private subnet. We use userdata script to setup connectivity via proxy. We suspect that configuring the proxy via userdata is too late or not accepted by
the suse in-region smt repo servers, so the server boots with no repos present in the config.

This same userdata proxy configuration works fine for the base redhat ami in the same private subnet in the same aws account and region using the same proxy.

Details of our config:

ec2 host running userdata:
AMI: suse-sles-12-sp2-v20161214-hvm-ssd-x86_64 (ami-9186a1e2)

ec2 proxy:
- Amazon Linux 2016.09 updated to 2016.12
- squid 3.5.20

Thank you for any guidance you can provide to connect via proxy at boot or force
smt registration and onboarding of repos after booting.

-------------------------------------------------------

output from /var/log/cloudregister:

2017-02-09 11:47:57,608 INFO:Using API: regionInfo
2017-02-09 11:47:57,609 INFO:Using region server: 54.244.244.107
2017-02-09 11:47:57,613 INFO:Starting new HTTPS connection (1): 54.244.244.107
2017-02-09 11:48:12,628 ERROR:No response from: 54.244.244.107
2017-02-09 11:48:12,628 INFO:Using region server: 54.253.118.149
2017-02-09 11:48:12,629 INFO:Starting new HTTPS connection (1): 54.253.118.149
2017-02-09 11:48:27,644 ERROR:No response from: 54.253.118.149
2017-02-09 11:48:27,645 INFO:Using region server: 50.17.208.31
2017-02-09 11:48:27,645 INFO:Starting new HTTPS connection (1): 50.17.208.31
2017-02-09 11:48:42,661 ERROR:No response from: 50.17.208.31
2017-02-09 11:48:42,661 INFO:Using region server: 54.247.166.75
2017-02-09 11:48:42,662 INFO:Starting new HTTPS connection (1): 54.247.166.75
2017-02-09 11:48:57,676 ERROR:No response from: 54.247.166.75
2017-02-09 11:48:57,676 ERROR:None of the servers responded
2017-02-09 11:48:57,676 ERROR: Attempted: ['54.244.244.107', '54.253.118.149', '50.17.208.31', '54.247.166.75']
2017-02-09 11:48:57,676 ERROR:Exiting without registration
2017-02-09 11:49:00,469 INFO:[Service] No SMT server found, nothing to do
2017-02-09 11:49:00,636 INFO:[Service] No SMT server found, nothing to do
2017-02-09 11:49:00,960 INFO:[Service] No SMT server found, nothing to do
2017-02-09 11:49:02,140 INFO:[Service] No SMT server found, nothing to do
2017-02-09 11:50:53,950 INFO:[Service] No SMT server found, nothing to do