I am planning on enabling MFA on my root account at Amazon to increase my access security .
However a bit of caution says I should ask the Turnkey folks if this will interfere with the operation of the Turnkey Hub (day to day management or New instance Launching).
I've been using TKL for a year or so now, and really love it. I've been using it for a side business I have.
I have an instance that is 95% configured the way I want that can be used in my "real" job. I'm running a Mac with VMWare Fusion, so I downloaded a TKL appliance (LAMP) and restored my 95%-of-the-way-there backup to it on my local machine. I've gone in and made the edits/changes I needed to on it, and on the first of the year will be activating a new TKLBAM account for my "real" job.
Hello, I did not have time to patch my server during the small window that was recommended when the Oct 2014 critical sql injection bug was revealed. My server does not appear to be infected but of course you never know.
I want to make sure my server is put into an uninfected state. So would restoring from a TKBLM backup from just before the vulnerability went public be enough to roll back any potential malicious programs that may have been installed? I'm guessing no since TKBLM is kind of selective.
Trying to launch an instance using Turnkey hub, I've signed upto the Pay per use plan and activated it on Amazon. But soon as I press Launch I receive the following message. I've left it a week and tried every way possible to get it to work and it still doesn't work. I'm trying to launch a lamp stack, Ireland server, Medium M3. If not I'll just launch it manually on the ec2.
Error
Your Amazon EC2 account is not enabled for TurnKey Linux deployment.
I'm trying to get to Zurmo to load using the IP assigned to the appliance. When I try to connect I get
"The server at zurmo can't be found, because the DNS lookup failed. DNS is the network service that translates a website's name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network."