ACM.435 Creating and Running Containers in AWS CloudShell
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ ~~~~~~
⚙️ Part of my series on Automation of cybersecurity measures. THE Coded.
🔒 Related Stories: AWS Security | Application security | Abstraction
💻 Free content on Cybersecurity Jobs | ✉️ Register for Broadcast list
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ ~~~~~~
In the last article I moved my files into separate repositories so that it would be easier to allow users to edit tasks without changing the main execution framework. New jobs and job configurations can be added and edited independently and easily. Security, governance, flexibility, speed and convenience all rolled into one if everything goes according to plan.
I came to the conclusion that I didn’t want to deploy the framework to the root management account in a previous article. I want to use a basic script to deploy a few initial components and limit what I deploy in this account to the minimum required.
I want to try doing my initial deployment with a container. For now, I’ll pull the code into CloudShell, create the container, and run it. This is not my final solution.
About a week ago, AWS announced support for Docker in CloudShell. Well, I was using containers in CloudShell months ago, so I’m wondering if this just hasn’t been announced or if there really is something new here.
Anyway, it is now officially supported, but only in certain regions. This means you need to use one of the supported regions if you want to use my approach. I’m sure the list will grow over time.