Earlier in December, Cloudhouse CEO, Mat Clothier, attended the AWS re:Invent 2021 conference in Las Vegas. As we look ahead to 2022, Mat shares his thoughts on the conference and what it means for the future of the Cloud.
As I headed off to AWS re:Invent at the end of November, I was delighted that it was an in-person event again, albeit on a much smaller scale than previous years. It’s hard to beat meeting face-to-face when it comes to sharing ideas, and I was looking forward to catching up with colleagues I hadn’t seen in a long time.
There was a great line-up of speakers and, although there were no major new product announcements, a couple of things stood out for me.
Firstly, it was great to hear from the new AWS CEO, Adam Selipsky, for his first keynote address. He demonstrated a real depth of understanding of the business, and from talking to others in attendance, there was a sense of reassurance to know that he gets it. There was a real feeling of optimism and positivity among the delegates.
Secondly, I think the conference made it clear that AWS has held on to its core values. It’s been through a period of huge growth, and now it’s reaching a level of maturity and refining its offering. From my point of view, I think the most interesting thing here is that the company has made a clear commitment to help people complete the process of moving to the Cloud. It is focusing efforts on elements that are less cloud native, things that been left behind so far. How can it best support people to fully make the move? It’s also encouraging that the company is making a play in mainframe migration service. This is going to be really important for customers with massive estates who are currently finding it difficult to move entrenched software. It’s great news that AWS plans to build tools to make completion happen, and it reinforces my opinion that we need to prioritise working towards this.
A focus on modernisation
A stand-out session for me was that with Adnan Ijaz, Director of Product Management in the AWS Commercial Services software team. His talk was a deep dive into Windows Engineering: AWS was the first major Cloud provider to offer Windows workloads. Adnan mentioned the launch of End-of-support Migration Programme for Windows Server (EMP), for which Cloudhouse is the Global Preferred Partner. I was delighted to hear him describe it as one of his favourite launches. As he went on to explain “It’s one of the things where we’re really proud of innovating for our Windows customers. Most recently, a lot of our focus has been on modernisation, helping customers move off of these legacy applications and turn them into more cloud native applications.” Something that really chimes with me and the Cloudhouse team!
I’m confident that 2022 will see the next phase in the evolution of the Cloud: bringing everyone on board. I’m looking forward to this next step of the journey.
Disclosure: Cloudhouse is the Preferred Partner for the Amazon Web Services (AWS) End-of-Support Migration Programme for Windows Server (EMP) service.
FREQUENTLY ASKED QUESTIONS
Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.
Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.
Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.
Contact us here with your requirements and we will provide you with a quote.
Packaging and Maintaining Applications
Cloudhouse provide the Professional Services to package applications.
Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.
Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.
Cloudhouse recommends the same team who manage the operations of native apps.
Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.
The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.
Full documentation is made available to Cloudhouse partners and customers as required.
Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.