------------------------------------------------------------------------------------------
Split from LOGO!8.3 LWE to AWS cannot create environment in AWS.

Very doubtful that using Cloud features with Logo works in long term, even year or two.  AWS not controlled by Siemens and Amazon can change any moment AWS API or entire logic. I just imagine that after deploying project, which uses AWS, one needs to expect customer call at random moment, because "until end of August it worked, now not  anymore". Alternative way is to launch cloud service by Siemens for customers (like Unitronics now does, btw) and take care that at least 10 years every Logo with cloud support works without hiccups. This "works for me!" syndrome from software industry is not good for apparatus, which must work years and years without intervention.

Anyone remembers WAP (Wireless Application Protocol) today? Your project dependence from AWS Cloud looks to me like building ground for future trouble by yourself.

I hope that in future Siemens leaves this Cloud as "thing from the past" and integrates something useful like sending e-mail or MQTT support to BM or OpenVPN Client to CMR20X0.

For example adding Modbus/TCP to Logo! is really good move and helped tiny system integrators. Cloud support ... hmm...

M111

25 Euro per year will be more good for more Logo 8.3 popularitiy. Just my opinion.

>  The only thing that worked was receving the invoice (€25 in 1month)

 Well, my math gives different result.

Anyway, point of my frustation is different - this can't be reliable solution in long term, when AWS may change API any moment at will

https://support.industry.siemens.com/tf/ww/en/posts/about-logo-web-editor-to-cloud-aws-registration/268791/