AWS IoT Core provides certificates for your things. When you delete an AWS IoT thing, the certificate attached to it will be available. If the policy attached to that certificate doesn't rely on the Thing's existance, which is not so uncommon, bad things can happen. Unused certificates are always dangerous.
You have a software running on an EC2 instance and simply you want to create a scheduled backup of a file (or files) to S3. Even if it's not a good backup strategy to use it on the production, it still saves time for POC's. I need this while I was testing a Django web app with sqlite database. Notice that sqlite is not a database service or a server, it's just a binary file as a database.
One of my front-end developer friends asked me to setup a thing that auto build Angular app from the Bitbucket git repo to show every updated version of the front-end to their customer. It's easily possible nowadays and let's see how I did accomplish their request using Bitbucket Pipelines, Deployments and AWS S3.
Nowadays, I'm focused on using AWS IoT MQTT over websockets to interact with IoT devices real-time on the browser. When use MQTT on a browser, the browser is actually being an MQTT client to subscribe messages from the broker. But when the broker is AWS IoT, it's not easy like connecting to a “plain” broker (like iot.eclipse.org)
I will show that how I handled the requirement of monitoring and configuration of my linux devices from a GUI using an open source tool; Cockpit. It's a Red Hat sponsored free software project. I'll go with a Raspberry Pi to show how it works. I've used a RPI with Raspbian 9 stretch lite; which is based on Debian 9.