How? By using their cloud service: AWS brings the Mac mini to its cloud.
Perfect for those times you need access to a Mac for a short period of time (e.g. testing software).
Throughout my career I have been involved with Macs and cloud technology. I remember when Apple made Mac servers. There was even a separate MacOS for them. So I am loving this evolution and the repositioning of Macs in a data center.
Image from here which also has a write up on this.
I haven’t tried this yet, but I am seriously considering it. I already use AWS for other things, so it might be time to see if I can archive old files that I rarely use but don’t want to delete. I don’t feel like getting more hardware, and I don’t have much confidence in Apple’s iCloud. So this might be the solution: How to Use Amazon Glacier as a Dirt Cheap Backup Solution.
And if I go that route, I will need tools. This article should give me the information I need for that: The Best Tools for Uploading Files to Amazon Glacier – Digital Inspiration.
(Photo by Glen Carrie on Unsplash)
Posted in IT
Tagged amazon, AWS, backup, gracier, IT
Stratechery is always great and this piece is no different: The WeWork IPO – Stratechery by Ben Thompson.
What makes it good is that rather than just slamming WeWork superficially, as many takes have, it delves into what could possibly justify why WeWork is a good investment.
My take is that if WeWork had a different executive, it could be a successful company. I think the comparison to AWS is somewhat valid, and in the gig economy with lots of short term work, it could become very successful. (It worked really well for a recent project I was on).
That said, I believe the executive team of WeWork will not be able to handle any drying up of capital or a recession of any length. Or investors will wake up and ask themselves why WeWork should be valued way more than IWG/Regus. Time will tell, of course.
One last thing: my understanding is that WeWork had to start from scratch in terms of buying up / leasing real estate, but AWS did not start from scratch and took advantage of existing capacity Amazon currently had.
(Image link to the original piece in the article reference)
August 20, 2019 in ideas, new!
Tagged AWS, business, entrepreneur, ideas, investment, realestate, startup, strategy, WeWork
Finally got around to doing this, so I have update this page. Here’s your options. Option 3 worked for me.
Note, you will need some technical knowledge, an Amazon account, and one of these guides:
- Simple site hosting with Amazon S3 and HTTPS. This is good if you plan to host your DNS at AWS. I didn’t, so I ran into trouble.
- . This piece is similar and helped too but the SSL certificate was hosted elsewhere, so it only helped so much.
- This page finally helped me because I host with namecheap.com. I followed it and it worked great! It has more detail than some of the others.
You don’t have to use AWS. Other cloud providers offers something similar:
So, lots of options.
I used to be a haphazard reader and my reading had slacked off. In 2017 I decided to have a goal of reading more and recording the books I had read. For the record, I had a simple Excel spreadsheet. This was good, but not easy to share.
To build this page, All the books I have read since 2017 | Smart People I Know, I wrote a Python program to convert the Excel spreadsheet to HTML. After that, it make it look modestly better, I stole some ideas from here. I was going to put the HTML directly into WordPress, but there were formatting issues. I instead put the page in an S3 bucket at AWS. And voila! Done!
I just cleaned up an environment I had set up in Amazon years ago for a client. (The client wanted to use Amazon, so we did.) In doing so, I wanted to make sure I didn’t leave anything behind which would cause me to continue getting billed even though I was no longer actively using EC2. I believe that the following checklist was useful in insuring this.
My EC2 cleanup checkist:
- Delete my Elastic IPs
- Terminated instances – running and non-running (I did this before deleting volumes, since it deleted alot of them for me)
- Delete remaining volumes
- Delete my security groups ( 1 will be left – the default one)
- Deregister AMIs
- Delete snapshots (you need to deregister your AMIs before you do this)
- Check your account balance
- In a few days, check your account balance to see if there are any charges you haven’t accounted for
After following this checklist, my EC2 environment was cleaned up. Depending on how you are using EC2, you may have more things to delete. Checking your account balance will help there: if you left things behind, they may incur charges. An increase in your account balance will help flush them out.
One thing to consider: you may delete something, but it doesn’t show in admin console. If that is the case, logout and then in. I did that when I was having trouble deregistering my AMIs. I logged out and then in and when I checked them, they were now deregistered.