Thank you for responding, and no need to be sorry. I appreciate you taking the time to care.

At least now I understand why my program doesn't work for you. Again, both the lsc and lwe Test  programs  in the zip file need to be modified to run in your particular local setting (IP, Subnet, Gateway addresses), or on the AWS cloud before they are run

I really want my actual program to work on the cloud and am willing to put in the effort until I figure it out, or help Siemens identify the bug and get this resolved. 

Thanks again,

Denny

Actually there is something that would help me diagnose my issue fiurther, Would someone connect the the link below and let me know how it responds? This is the simple cloud LSC and LWE program I have included in my test.zip file in one of my latest posts. 

http://test-env.eba-ypmmspht.us-east-2.elasticbeanstalk.com/

When I click on the start-Stop check mark nothing happens in the cloud, however it works perfectly on my local web server.

Perhaps it's something to do with my connection to the niternet, but If someone tries it and it works, then I will know it's on my end.

Also, AWS support want me to look at me LWE application and access logs. (access.log) I can't find them on my machine. Does any one knw where they are located ot if you've ever hear of this?

Thank you for your help.

Password is LOGO. All capital letters.

Hi

I have some experience with LOGO connected to AWS. 

I followed examples provided by Siemens and I adapted to my needs.

At what point are you blocked?

Have you the right hardware?

AWS account is created?

Have you defined variables to connect to cloud?

Did you registered device on AWS?

Have you defined a working environment in AWS?

Did you load the page created with LWE in cloud?

What about rules and policies in cloud? Are defined?

Let me know, and maybe I can share my experience with you. 

Thank you. That is exactly how everyone of my LWE could applications respond, even the training apps from Siements.

I really appreciateyour help.

Denny

Just an update. I spent over 2 hours on a Mictosoft Teams call with a Siemens support engineer, and after trying everything, including re writing a new LWE app, he couldn't figure out what's wrong. Certainly not the LWE or LSC programs, so tge issue has been escalated to Siemens R&D. I'll keep you posted as I find out more. In the mean time I moved both programs to a different PC, just in case it was something to do with my PC configuration. Still had exactly the same issue in the cloud.

One thing I just noticed is that my root users region is different from my IAM user REGION. I use my IAM user account to create my thing and load my LWE app to the cloud. I wouldn't think that it would matter if the two accounts have different regions as long as the region I use in my thing and LWE app are the same. I'll try to make tge region in both accounts tge same after the Holidays.

Any thoughts on this?

Meant " would not matter" in previous post.

Just to let everyone know, with the help of Siemens Spport in the US, Germany and China we were able to identify why my LWE application would not work correctly after I downloaded it to the AWS cloud.. 

The problem is that when you download the AWS Access Keys for you account or sub-account the download comes in a .csv format. Both the Access Key and Secret Access Key cells have a space at the end of the string that should not be there. You should only use the actual characters. Therefore if you do a copy and paste(cntrl C, cntrl V ) from the cells into you LWE download setup, you'll also copy the space at the end. Unfortunately, LWE does not issue an error message, so you may be, like me, lost as to why your LWE app isn't working correctly after it's downloaded to the AWS cloud.

The good news is that the developers are going to modify LWE in the next vesion to issue an error message, or ignore the space at the end. THey are also going to update their LWE docuementation to tell users notto leave a space at the end of the access key strings.

I have to say that Siemens support stuck with me through thivk and thin to find a solution. They were great..

Thank you  Alan, Dave, Sven, Yin Li, and Zhao Xin