How to Choose the Best Cloud Service Provider for your Application Modernization Strategy

If the global pandemic taught us anything, it’s that digital transformation is a must-have for businesses to keep up with customer dCloud Service Provider for App Modernization Strategyemands and remain competitive. To do this, organizations are moving their workloads to and modernizing their applications for the cloud faster than ever.

In fact, according to a recent survey, 91% of respondents agree or strongly agree that application modernization plays a critical role in their organization’s adaptability to rapidly changing business conditions. But there are so many cloud service providers to choose from! How do you know which one is best for your application modernization objectives? Keep reading to find out!  

What is a Cloud Services Provider (CSP)? 

A cloud services provider is a cloud computing company that provides public clouds, managed private clouds, or on-demand cloud infrastructures, platforms, and services. Many CSPs are available worldwide, including Alibaba Cloud, Amazon Web Services (AWS), Google Cloud Platform (GCP), IBM Cloud, Oracle Cloud, and Microsoft Azure. However, three industry giants are noteworthy because of their services and global footprint: Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. 

What is a Cloud Services Provider (CSP)?

What is Application Modernization? 

Application modernization is the process of revamping an application to take advantage of breakthrough technical innovations to improve the overall efficiency of the application remarkably. This efficiency typically involves high availability, increased fault tolerance, high scalability, improved security, eliminating a single point of failure, disaster recovery, contemporary and simplified tools, new coding language, and reduced resource requirements, among other benefits. Many companies running legacy applications are now looking at how they can best modernize their monolith applications. 

Application Rationalization: The First Step to Modernization 

The best way to start any application modernization journey is with application rationalization. In this process, you identify company-wide business applications and strategically determine which ones you should keep, replace, retire, or consolidate. Once you identify those applications, you can list each one’s ease or difficulty level, total cost of ownership (TCO), and business value, enabling you to decide and prioritize which action to take. (Hint: Start with high value and minimal effort apps!) Doing this will also help you eliminate redundancies, lower costs, and maximize efficiency. 

The high-value apps that are difficult to move to the cloud will likely cause the most grief in your decision-making process. But, like Rome, your modernization strategy doesn’t need to be built in a day.

You can develop an approach to application modernization over time and still reduce costs and risks while moving your portfolio forward.  

It is crucial to evaluate your current application stack and determine the most suitable application modernization strategy to migrate to the cloud when it comes to application modernization in the cloud. Many on-premises applications are legacy monoliths that may benefit more from refactoring than a rehosting (“lift and shift”) approach. (Check out Rehost, Refactor, Replatform – What, When, & Why? | AppMod Essentials) 

Refactoring may require overhauling your application code, which takes some high-level effort but offers the most benefits. However, not all applications are ideal candidates for refactoring. Rearchitecting will become necessary for some obsolete applications that are not compatible with the cloud due to architectural designs made while building the app. In this scenario, the value proposition considers rearchitecting, dividing the application into several functional components that can be individually adapted and further developed. These small, independent pieces—or “microservices”—can then be migrated to the cloud quickly and efficiently. 

call to action

Determining the Best Cloud Services Provider for Your Application Modernization 

Each application modernization journey is unique, as is the process of choosing the best cloud service provider that meets your demands. What works for one business’ application may not be the best for yours, even if they are in the same industry. And just because a competitor has chosen one CSP over another does not mean you should. 

When evaluating the CSP that is best for you, consider the following: 

Service Level Agreements (SLAs): Determine if the CSP’s service level agreements suit your production workloads, whether the cloud service is generally available yet, and they retain satisfactory levels of support knowledge. Managing workloads in the cloud can sometimes be tedious. The managed services department may not have the required expertise to efficiently manage and monitor the cloud environment. It is critical to your business to do your due diligence to ensure your preferred CSP can administer their managed offerings with as close to zero downtime as possible. 

  • Vendor Lock-in: It is important to have alternatives to any single CSP and that you retain the flexibility to substitute for a better value proposition. 
  • Enterprise Adoption: Consider the likelihood of scalability of your use of the CSP across your organization. 
  • Economic Impact: Consider the positive business or financial impacts that result from the service usage at the individual, department, and company-wide levels. 
  • Automation and Deployment: Verify the CSP’s integration capabilities with your organization’s preferred automation tooling and availability of automated and local testing frameworks.  

CSP Application Modernization Design Considerations 

When modernizing existing applications to take the best advantage of the cloud, cloud technologies like serverless and containers are good options to consider. Serverless computing and containers are cloud-native tools that automate code deployment into isolated environments. Developers can build highly scalable applications with fewer resources within a short time. They both also reduce overhead for cloud-hosted web applications but differ in many ways. Private cloud, hybrid cloud, and multi-cloud approaches to application modernization are worth considering too. 

Serverless Computing and Containers 

Serverless Computing and Containers Serverless computing is an exaction model where the CSP executes a piece of code by dynamically allocating the resources and can only charge for the services used to run the code. Code is typically run in stateless containers. Various events such as HTTP requests, monitoring alerts, database events, queuing services, file uploads, scheduled events (cron jobs), and more can trigger them.

 

The cloud service provider then receives the code in a function to execute, which is why serverless computing is sometimes referred to as a Function-as-a-Service (FaaS) platform. Add that to your list of as-a-Service acronyms: IaaS, PaaS, SaaS, FaaS!   

The FaaS offerings of the three major CSPs are: 

Containers provide a discrete environment set up within an operating system. They can run one or more applications, typically assigned only those resources necessary for the application to function correctly. Because containers are smaller and faster than virtual machines, they allow applications to run quickly and reliably among various computing environments. Container images become containers at runtime and include everything needed to run an application: code, runtime, system tools, system libraries, and settings. 

Private, Hybrid, and Multi-Cloud 

The public cloud is a vital part of any modernization strategy. However, some organizations may not be ready to go directly to the public cloud from the datacenter. Cloud architects should consider private, hybrid, and multi-cloud strategies in those cases. These models can help resolve any architectural, security, or latency concerns. They will also reduce the complexity associated with the policies for specific workloads based on their unique characteristics.  

Conclusion 

Migration to the cloud is ideal for investing in application modernization as it can lower your overall operational costs and increase your application’s resiliency. But not all use cases—nor cloud service providers—are the same. You need to do your homework before choosing the best-suited one for your business.  

2nd Watch offers a comprehensive consulting methodology and proven tools to accelerate your cloud-native and app modernization objectives. Our modernization process begins with a complete assessment of your existing application portfolio to identify which you should keep, replace, retire, or consolidate. We then develop and implement a modernization strategy that best meets your business needs.

From application rationalization to application modernization and beyond, 2nd Watch is your go-to trusted advisor throughout your entire modernization journey. 

Contact us to schedule a brief meeting with our specialists to discuss your current modernization objectives. 

By Alex Ifebigh, 2nd Watch Sr. Cloud Consultant 

 

rss
Facebooktwitterlinkedinmail

Amazon Web Services (AWS) Outage Constitutes Multi-Region Infrastructure

When Amazon’s cloud computing platform, Amazon Web Services (AWS), suffered an outage this past Tuesday (December 7, 2021), the magnitude of the event was felt globally. What happened, and how can your business learn from this significant outage?

Why was there an AWS outage?

Reported issues within the AWS infrastructure began around 12:00 ET/17:00 GMT on Dec. 7, according to data from real-time outage monitoring service DownDetector.

Amazon reported that the “US-East-1” region went down in North Virginia on Tuesday, which disrupted Amazon’s own applications and multiple third-party services that also rely on AWS. The issue was an “impairment of several network devices” that resulted in several API errors and ultimately, impacted many critical AWS services.

AWS outage

What were the effects of the AWS outage?

The effects of the AWS outage were massive because any problem affecting Amazon impacts hundreds of millions of end-users. AWS constitutes 41% of the global cloud-computing business, and many of the largest companies in the world are dependent on AWS’s cloud computing services. These businesses rent computing, storage, and network capabilities from AWS, which means the outage prevented end-users ‘ access to a variety of sites and apps across the Internet.

The major websites and apps that suffered from the outage are ones we turn to on a daily basis: Xfinity, Venmo, Google, and Disney+, just to name a few.

On Tuesday morning, users were reporting that they couldn’t log on to a variety of vital accounts. Most of us were going through our normal daily routine of checking the news, our financial accounts, or our Amazon orders, only to frustratingly realize that we couldn’t do so. 

With so many large organizations relying on AWS, when the outage occurred, it felt like the entire Internet went down. 

Benefits of a High Availability Multi-Region Cloud Application Architecture

Even though the outage was a major headache, it serves as an important lesson for those who are relying on a cloud-based infrastructure. As they say, you should learn from mistakes.

Amazon AWS OutageSo how can your business mitigate, or even avoid, the effects of a major failure within your cloud provider?

At 2nd Watch, we are in favor of a high availability multi-region cloud approach. We advise our clients to build out multi-region application architecture not only because it will support your mission-critical services during an outage, but also because it will make your applications more resilient and improve your end-user experiences by keeping latencies low for a distributed

user base. Below is how we think about a multi-region cloud approach and why we believe it is a strong strategy

1. Increase your Fault Tolerance

Fault tolerance is the ability of a system to endure some kind of failure and continue to operate properly. 

Unfortunately, things happen that are beyond our control (i.e. natural disasters) or things slip through the cracks (i.e. human error), which can impact a data center, an availability zone, or an entire region. However, just because a failure happens doesn’t mean an outage has to happen.

By architecting a multi-region application structure, if there is a regional failure similar to AWS’s east region failure, your company can avoid a complete outage. Having a multi-region architecture grants your business the redundancy required to increase availability and resiliency, ensure business continuity and support disaster recovery plans.

2. Lower latency requirements for your worldwide customer base

The benefits of a multi-region approach goes beyond disaster recovery and business continuity. By adopting a multi-region application architecture, your company can deliver low latency by keeping data closer to all of your users, even those who are across the globe.

In an increasingly impatient world, keeping latency low is vital for a good user experience, and the only way to maintain low latency is keeping your users close to the data.

3. Comply with Data Privacy Laws & Regulations

“Are you GDPR compliant?” is a question you probably hear frequently. Hopefully your business is, and you want to remain that way. With a multi-region architecture, you can ensure that you are storing data within the legal boundaries. Also, with signs that there will be more regulations each year, you will stay a step ahead with data compliance if you utilize a multi-region approach.

How Can I Implement a Multi-Region Infrastructure Deployment Solution?

A multi-region cloud approach is a proactive way to alleviate potential headaches and grow your business, but without guidance, it can seem daunting in terms of adoption strategy, platform selection, and cost modeling. 

2nd Watch helps you mitigate the risks of potential public cloud outages and deploy a multi-region cloud infrastructure. Through our Cloud Advisory Services, we serve as your trusted advisor for answering key questions, defining strategy, managing change, and providing impartial advice for a wide range of organizational, process, and technical issues critical to successful cloud modernization.

Contact us today to discuss a multi-region application architecture for your business needs!

rss
Facebooktwitterlinkedinmail

What to Expect at AWS re:Invent 2021

Welcome back friends! AWS re:Invent turns 10 this year and once again 2nd Watch is here to help you navigate it like a pro. As we all know now, AWS re:Invent 2021 is back in person in Las Vegas. One addition this year, Amazon Web Services is also offering a virtual event option… well, kind of…. As it currently stands, only the keynotes and leadership sessions will be live streamed for the virtual attendees. Breakout sessions will only be live for in person attendees, but will be available on-demand after the event.

What to Expect at AWS re:Invent 2021

For the rest of this blog I will try to focus on my thoughts and limit my regurgitation of all the information that you can get from the AWS re:Invent website, such as the AWS Code of Conduct, but I think it’s worth noting what I think are some key highlights that you should know. Oh, and one more thing. I have added a small easter egg to this year’s blog. If you can find a Stan Lee reference, shoot me an email: dustin@2ndwatch.com and call it out. One winner will be picked at random and sent a $25 Amazon gift card. Now let’s get to it.

Some important things to note this year

Now that AWS re:Invent is (mostly) back in person, AWS is implementing proper health measures to prevent the spread of COVID. Make sure to review the health guidelines published by AWS. (https://reinvent.awsevents.com/health-measures/). Here is the summary for those that don’t enjoy more eye exercise than necessary. Refer to aforementioned link for more details and FAQ’s if you do.

  • All badge holders attending in person must be fully vaccinated for COVID-19 (2 weeks after final shot) which means you must provide a record of vaccination in order to receive your badge. AWS makes it clear that there are no ifs, ands or buts on this. No vax proof, no badge. ‘Nuff said!
  • Masks will be required for everyone at the event. Real ones. Unfortunately face lingerie and train robber disguises will not count.

Keynotes at Glance

This year’s keynotes give you the best of both worlds with both a live option for in person attendees and on-demand viewing option for virtual attendees. The 2021 keynotes include:

  • Adam Selipsky, AWS CEO
  • Peter DeSantis, Senior Vice President, Utility Computing and Apps
  • Wener Vogels, CTO, Amazon.com
  • Swami Sivasubramanian, Vice President, Amazon Machine Learning
  • Global Partner Summit presented by Doug Yeum, Head of AWS Partner Organization, Sandy Carter, Vice President, Worldwide Public Sector Partners and Programs, and Stephan Orban, General Manager of AWS Marketplace and Control Services

2nd Watch Tips n’ Tricks

Over the last 9 years we have watched the AWS re:Invent conference morph into a goliath of an event. Through our tenure there we have picked up an abundance of tips n’ tricks to help us navigate the waters. Some of these you may have seen from my previous blogs, but they still hold strong value, so I have decided to include them. I have also added a couple new gems to the list.

  • App for the win – I cannot stress this one enough. Download and use the AWS Events app. This will help you manage your time as well as navigate around and between the venues.
  • Embrace your extravert Consider signing up for the Builder Sessions, Workshops, and Chalk Talks instead of just Breakout sessions. These are often interactive and a great way to learn with your peers.
  • Watch for repeats AWS is known for adding in repeat Breakout sessions for ones that are extremely popular. Keep your eye on the AWS Events app for updates throughout the week.
  • Get ahead of the pack After Adam Selipsky’s Keynote there will likely be sessions released to cover off on new services that are announced. Get ahead of the pack by attending these.
  • No fomo Most of the Breakout sessions are recorded and posted online after re:Invent is over. Fear not if you miss a session that you had your eyes on, you can always view it later while eating your lunch, on a break or doing your business.
  • Get engaged – Don’t be afraid to engage with presenters after the sessions. They are typically there to provide information and love answering questions. Some presenters will also offer up their contact information so that you can follow up again at a later time. Don’t be shy and snag some contact cards for topics relevant to your interests.
  • Bring the XL suitcase – Now that we are back in person, get ready to fill that swag bag! You will need room to bring all that stuff home so have extra room in your suitcase when you arrive.
  • Don’t just swag and run – Look, we all love stuffing the XL suitcase with swag, but don’t forget to engage your peers at the booths while hunting the hottest swag give-a-ways. Remember that part of the re:Invent experience is to make connections and meet people in your industry. Enjoy it. Even if it makes you a little uncomfortable.
  • Pro tip! Another option if you missed out on a reserving a session you wanted is to try and schedule something else that is near it at the same time. This will allow you to do a drive by on the session you really wanted and see if there is an open spot. Worst case, head to your back up session that you were able to schedule.

Our re:Invent Predictions

Now that we have you well prepared for the conference, here are a couple of our predictions for what we will see this year. We are not always right on these, but it’s always fun to guess.

  • RDS savings plans will become a reality.
  • Specialty instance types targeted at specific workloads (similar to the new VT1 instance they just announced focused on video).
  • Security hub add-ons for more diverse compliance scanning.
    • Expanded playbooks for compliance remediation.
    • More compliance frameworks to choose from.
  • Potential enhancements to Control Tower.
  • Virtual only attendees will not get the opportunity for the coveted re:Invent hoodie this year.

In Closing…

We are sure that after December 3rd there will be an overwhelming number of new services to sift through but once the re:Invent 2021 hangover subsides, 2nd Watch will be at the ready and by your side to help you consume and adopt the BEST solutions for your cloud journey. Swing by our booth #702 for some swag and a chat. We are giving away Gretsch Guitars we are super excited to see you!

Finally, don’t forget to schedule a meeting with one of our AWS Cloud Solution Experts while you’re at re:Invent. We would love to hear all about your cloud journey! We hope you are as excited as we are this year and we look forward to seeing you in Las Vegas.

-Dustin Snyder, Director of Cloud Infrastructure & Architecture

rss
Facebooktwitterlinkedinmail

Back to the Basics: The 3 Cloud Computing Service Delivery Models

In recent years, the adoption of cloud computing services has increased tremendously, especially given the onset of the pandemic. According to a report from the International Data Corporation (IDC), the public cloud services market grew 24.1% year over year in 2020. This increase in popularity is credited to the benefits provided by cloud including flexibility, on-demand capacity planning, cost reductions, and ability for users to access shared resources from anywhere.

No matter where you are in your cloud journey, understanding foundational concepts like the different types of cloud service models is important to your success in the cloud. These cloud computing service models provide different levels of control, flexibility, and management capabilities. With a greater understanding of the models, their benefits, and the different ways to deploy these infrastructures, you can determine the method that matches your business needs best.

What are the 3 Cloud Computing Service Delivery Models?

Different cloud computing service delivery models help meet different needs, and determining which model is best for you is an important first step when you transition to the cloud. The three major models are IaaS, PaaS, and SaaS.

Infrastructure as a Service (IaaS)

IaaS is one of the most flexible cloud computing models. The infrastructure and its features are presented in a completely remote environment, allowing clients direct access to servers, networking, storage, and availability zones. Additionally, IaaS environments have automated deployments, significantly speeding up your operations in comparison to manual deployments. Some examples of IaaS vendors include Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform. In these types of environments, the vendor is responsible for the infrastructure, but the users still have complete control over the Identity Access Management, data, applications, runtime, middleware, operating system, and virtual network.

Platform as a Service (PaaS)

Another cloud computing service delivery model is Platform as a Service (PaaS). PaaS is a subset of IaaS, except customers are only responsible for Identity Access Management, data, and applications and it removes the need for organizations to manage the underlying infrastructure. Rather than having the responsibility over hardware and operating systems as with IaaS, PaaS helps you focus on the deployment and management of your applications. There is less need for resource procurement, capacity planning, software maintenance, and patching. Some examples of PaaS include Windows Azure, Google AppEngine and AWS Elastic Beanstalk.

Software as a Service (SaaS)

Perhaps the most well-known of all three models is SaaS, where the deployment is redistributed to third party services. The customer’s only responsibilities are Identity Access Management, data, and the task of managing software. SaaS offers the entire package offered between IaaS and PaaS, as infrastructure, middleware, and applications deployed over the web can be seamlessly accessed from any place at any time, no matter the platform. Vendors of SaaS include CRM services like Salesforce and productivity software services like Google Apps. One major benefit of SaaS is that it reduces the costs of software ownership and eliminates the need for IT staff to manage the software so your company can focus on what it does best.  Another benefit of SaaS that its relevance to businesses today, as SaaS is considered the best option for remote collaboration. With SaaS, your applications can be accessed from any geographical location and your company is not responsible for managing the hardware.

Cloud Computing Service Delivery Models

Choosing the Cloud Computing Model that is Right for You

 Each cloud computing service model has different benefits to consider when determining the model that will work best for your business needs, projects, and goals.

While IaaS gives you complete control over your infrastructure, some businesses may decide they do not need to fully manage their applications and infrastructure on their own. IaaS is considered a good fit for SMEs and startups who do not have the resources or time to buy and build the infra for their own network. Additionally, larger companies may prefer to have complete control and scalability over their infrastructure, so they too may opt for IaaS for a pay-as-you go, remote option with powerful tools. One downside to IaaS is that it is more costly in comparison to PaaS and SaaS cloud computing models, yet it does minimize costs in the sense it eliminates the need to deploy on-premises hardware.

IaaS Benefits

  • Reduced vendor lock-in
  • Platform virtualizations
  • On-demand scaling
  • GUI and API-based access
  • Increased security
  • Multi-tenant architecture

IaaS Disadvantages

  • Potential for vendor outages
  • The cost of training how to manage new infrastructure

PaaS is a good choice if you are looking to decrease your application’s time-to-market, because of its remote flexibility and accessibility. Thus, if your project involves multiple developers and vendors, each have quick accessibility to computing and networking resources through a PaaS. PaaS might also be used by a team of developers to test software and applications.

PaaS Benefits

  • Rapid product development through simplified process
  • Custom solutions
  • Highly scalable
  • Eliminates need to manage basic infrastructure
  • Future-proof
  • Multi-tenant architecture

PaaS Disadvantages

  • Security issues
  • Increased dependency on vendor for speed and support

SaaS is a feasible option for smaller companies that need to launch their ecommerce quickly or for short term projects that require quick, easy, and affordable collaboration from either a web or mobile standpoint. Any company that requires frequent collaboration such as transferring content and scheduling meetings will find SaaS convenient and accessible.

SaaS Benefits

  • On-demand service
  • Automated provisioning/management of your cloud infrastructure
  • Subscription-based billing
  • Allows for full remote collaboration
  • Reduced software costs
  • Pay-as-you-go

SaaS Disadvantages

  • Less control
  • Limited solutions

The 3 Cloud Computing Deployment Models

Another foundational concept of cloud are the deployment models. A deployment model is where your infrastructure resides and also determines who has control over its management. Like the cloud computing service delivery models, it is also important to choose the deployment model that will best meet the needs of your business.

There are three types of cloud computing deployment models:

Public Cloud

A cloud deployment means your applications are fully run in the cloud and accessible by the public. Often, organizations will choose a public cloud deployment for scalability reasons or when security is not a main concern. For example, when testing an application. Businesses may choose to create or migrate applications to the cloud to take advantage of its benefits, such as its easy set-up and low costs. Additionally, a public cloud deployment allows for a cloud service provider to manage your cloud infrastructure for you.

On-Premises/Private

 An on-premises cloud deployment, or private cloud deployment, is for companies who need to protect and secure their data and are willing to pay more to do so. Since its on-premises, the data and infrastructure are accessed and managed by your own IT team. Due to in-house maintenance and fixed scalability, this deployment model is the costliest.

Hybrid

 A hybrid cloud deployment connects cloud-based resources and existing non-cloud resources that do not exist in the cloud. The most common way to do this is between a public cloud and on-premises infrastructure. Through a hybrid cloud integration, you can segment data according to the needs of your business. For example, putting your highly sensitive data on-premises while putting less-sensitive data on the public cloud for accessibility and cost-effectiveness. This allows you to enjoy the benefits of the cloud while maintaining a secure environment for your data.

Next Steps

Determining the cloud computing service delivery model and deployment model best for your organization are both critical steps to the success of your company’s cloud computing journey. Get it right the first time by consulting with 2nd Watch. With a decade of experience as a managed service provider, we provide cloud services for your public cloud workloads. As an AWS Consulting Partner, Gold Microsoft Partner, and Google Cloud Partner, our team has the knowledge and expertise to efficiently guide you through your cloud journey. Contact us to learn more or talk to one of our experts.

-Tessa Foley, Marketing

rss
Facebooktwitterlinkedinmail

Well-Architected Framework Reviews

“Whatever you do in life, surround yourself with smart people who argue with you.” – John Wooden

Many AWS customers and practitioners have leveraged the Well-Architected Framework methodology in building new applications or migrating existing applications. Once a build or migration is complete, how many companies implement Well-Architected Framework reviews and perform those reviews regularly? We have found that many companies today do not conduct regular Well Architected Framework reviews and as a result, potentially face a multitude of risks.

What is a Well-Architected Framework?

The Well-Architected Framework is a methodology designed to provide high-level guidance on best practices when using AWS products and services. Whether building new or migrating existing workloads, security, reliability, performance, cost optimization, and operational excellence are vital to the integrity of the workload and can even be critical to the success of the company. A review of your architecture is especially critical when the rate of innovation of new products and services are being created and implemented by Cloud Service Providers (CSP).

2nd Watch Well-Architected Framework Reviews

At 2nd Watch, we provide  Well-Architected Framework reviews for our existing and prospective clients. The review process allows customers to make informed decisions about architecture decisions, the potential impact those decisions have on their business, and tradeoffs they are making. 2nd Watch offers its clients free Well-Architected Framework reviews—conducted on a regular basis—for mission-critical workloads that could have a negative business impact upon failure.

Examples of issues we have uncovered and remediated through Well-Architected Reviews:

  • Security: Not protecting data in transit and at rest through encryption
  • Cost: Low utilization and inability to map cost to business units
  • Reliability: Single points of failure where recovery processes have not been tested
  • Performance: A lack of benchmarking or proactive selection of services and sizing
  • Operations: Not tracking changes to configuration management on your workload

Using a standard based methodology, 2nd Watch will work closely with your team to thoroughly review the workload and will produce a detailed report outlining actionable items, timeframes, as well as provide prescriptive guidance in each of the key architectural pillars.

In reviewing your workload and architecture, 2nd Watch will identify areas of improvement, along with a detailed report of our findings. A separate paid engagement will be available to clients and prospects who want our AWS Certified Solutions Architects and AWS Certified DevOps Engineer Professionals to remediate our findings. To schedule your free Well-Architected Framework review, contact 2nd Watch today.

 

— Chris Resch, EVP Cloud Solutions, 2nd Watch

rss
Facebooktwitterlinkedinmail