《亚马逊云科技(AWS):成功迁移的8个最佳实践(英文版)(21页).pdf》由会员分享,可在线阅读,更多相关《亚马逊云科技(AWS):成功迁移的8个最佳实践(英文版)(21页).pdf(21页珍藏版)》请在三个皮匠报告上搜索。
1、8 Best Practices to Make Your Cloud Migration a Success The benefits of the cloud are now reasonably well known.There are many compelling reasons to migrate applications from on-premises to the cloud and change the way IT is delivered and consumed across the organization.The resulting cost reduction
2、s are enticing enough for most companies on their own;however,the true value of the cloud is its ability to increase business agility,improve staff productivity,and boost operational resilience.Cloud is fundamentally changing the way business is conducted and is quickly becoming an enabler for compa
3、nies to go global,launch new products,and modernize their businesses.If youre thinking along the same lines,youre Introduction:Migrating to the cloud is now necessary for your business to thrive2in good company.Today,global organizations such as The Coca-Cola Compa-ny,BP,Enel,News Corp,and Twenty-Fi
4、rst Century Fox have made the journey from private data center to AWS and transformed their businesses.Understanding the best practices learned from those who have gone before you can help reduce the time and effort needed to reach the full benefits of cloud migration.Through our experience in helpi
5、ng thousands of businesses migrate to the cloud,weve captured eight best practices that you can use to help make your cloud adoption plan a success.Think of this eBook as a template for what you can achieve with AWS and how you can make sure your whole business is along for the ride.You can find mor
6、e perspectives from other business leaders and AWS experts at our AWS Executive Insights.“By migrating our entire IT infrastructure to AWS,we achieved digital transformation of our IT systems,which can servehundreds of millions of consumers rather than the previous 10,000 sales representatives.”Ke L
7、i,Manager of Cloud Service&IT Operations,Swire Coca-ColaMigrating to the cloud is much more than a technology or technical transition.When done properly,cloud migration can transform and modernize your entire organization,creating new efficiencies and capabilities that accelerate innovation througho
8、ut every business department.Its a big changeand in business,big changes dont stick unless theyre backed by firm commitments from leadership.So,before cloud migration can begin in earnest,youll need to ensure that you establish buy-in across all key stakeholders.Failing to do so will lead to false s
9、tarts,overextended timelines,and results that dont live up to expectations.To foster cloud migration buy-in,start by identifying concrete goals that everyone within your organization can support(see Best Practice#2 for more detail).Then create timetables and benchmarks for achieving those goals,alon
10、g with mechanisms that accurately measure progress and communicate it to the larger team.Inertia is a powerful corporate tool,so be sure to use it to your advantage.Dont procrastinatekeep initiatives continuously moving forward.When you encounter stalls,implement solutions or workarounds as quickly
11、as possible to avoid missing milestones and losing momentum(see Best Practice#7 for more on this).1Cultivate conviction&alignment across senior leadership3Nationwide is one company thats had success in fostering executive buy-in.“Having an IT executive sponsor for cloud is keybut having an executive
12、 sponsor in the business is transformational,”Ryan Hughes,VP of Cloud Solutions said.You can further solidify commitment from executives in your organization by appealing to their individual priorities.For example:Your CEO may be concerned about how to compete against disruptive startups and how art
13、ificial intelligence can change the companys business model Your CIO may be feeling pressure to deliver new services faster and more efficiently Your CFO may be looking for ways to be better prepared for a business downturn Your CMO may need better and faster insights on customer buying behavior to
14、dramatically improve time to market Your CISO may need more visibility,auditability,and control to reduce the risk of a data breach or information lossAs you start your cloud journey,you may not have buy-in from all of the executive team.But if you can demonstrate even to one leader that your cloud
15、adoption plan will deliver the benefits they are seeking,then you will have a powerful sponsor for your journey.This executive sponsor will be able to evangelize for you and keep the whole business focused on why youre moving to the cloud and what your organization can achieve when you get there.4Cu
16、ltivate conviction&alignment across senior leadership(contd)TIP:To keep stakeholders on board and cheerleading for you,youll need to achieve some quick wins that align with their prioritiessee Best Practice#4.Resources to help you get executive buy-in:ESG Research Insights Paper:Analyzing the Outcom
17、es Organizations Experience when Migrating Workloads to Cloud Infrastructure 5To ensure executive buy-inand,more importantly,overall cloud migration successyoull need to identify aggressive,top-down quantifiable goals that force your organization to move faster than it would organically.Lets take a
18、look at an AWS customer example to illustrate this point.Several years ago,former CIO and current CFO of GE,Jamie Miller,embarked on a quest to accelerate the companys journey into the cloud.She gathered the top technical leaders at the company and informed them that she intended to migrate 50 appli
19、cations to AWS in 30 days.Millers announcement was met with skepticism and predictions of failure.But she pushed on,confident that her goal could be met.While GE did ultimately fall eight applications short of Millers objective,the companys experience of migrating 42 applications to AWS in one month
20、 enabled it to codify its security and governance models and generate momentum.The teams skepticism transformed into excitement,with ideas for migrating and modernizing more applications flowing in from every direction.Today,GE is in the process of migrating more than 9,000 workloads to AWS while re
21、ducing its data center footprint from 34 to four.The GE Oil&Gas division has started this journey by migrating more than half of its core applications to AWS while achieving a 52 percent reduction in its total cost of ownership.1These efforts mark the realization of new,aggressive,top-down quantifia
22、ble goals that could never have been setlet alone achievedif Miller hadnt pressed the company to speed up its move to the cloud years ago.Thats why setting aggressive goals and remaining focused is so importantit empowers your organization to stop talking about migration and start doing it.Once thos
23、e efforts are underway,youll likely be surprised at how soon you can reach milestones and generate tangible,quantifiable business outcomes.And even if you do come up short,youll still quickly gain a wealth of experience that will inform your continuing efforts and solidify your business case.2Identi
24、fy top-down,quantifiable goals1 https:/ find it difficult to achieve your top-down quantifiable goals unless your whole team is on boardcommitted to achieving the vision,excited to build new skills,and prepared to work in completely new ways.The good news:All evidence suggests that most techies love
25、 working in the cloud.Whats not to love?The cloud offers a chance to learn new skills,test and play around with new ideas,explore new technologies,and improve the pace of your companys digital transformation.Most people will jump at the opportunity to grow.But you may find that there are those who r
26、esist change.Any resistance will,at best,hinder your progress and,at worst,derail the whole venture and growth plan.3Establish accountable leaders&train your teamsSo heres what you do:When you have buy-in for your transformation goals,you can clearly and firmly communicate the certainty of the cloud
27、 journey:Its non-negotiable,theres senior executive sponsorship,and the results will be transformative for the business.Of course,there are bound to be worriesyour data center team members will soon find themselves operating in a hybrid world,with progressively fewer on-premises resources to manage
28、and an abundance of new and innovative cloud technologies to master.Its essential that you articulate exactly how their roles will change,over what timescale,and,more importantly,highlight what opportunities they will have in the cloud-led world.You can help overcome those hurdles by staffing your t
29、eams with a single accountable lead.This personideally someone who is passionate about cloud transformation and has at least a basic level of cloud understanding and capabilitieswill be responsible for keeping their team focused on broad-er business goals while also measuring and reporting progress
30、to senior management.7Great cloud skills are scarce and are in huge demand.So the best approach is to upskill your team as fast as you can.Thankfully,technical employees tend to be fast,flexible,and eager learners.AWS Training and Certification offers the resources you need to develop your team,inno
31、vate in the cloud,and transform your organization.Our experts can help your team members leverage the fundamental IT skills and institutional knowledge they already have to transition to cloud roles and deepen their cloud expertise.We recommend the“Migrating to AWS”training to get started.Royal Phil
32、ips,a leading health technology company,exemplifies this best practice.“At Philips we are constantly innovating to help healthcare providers provide high quality care to their patients.Weve architected our HealthSuite platform using AWS Services.However,for some mission-critical healthcare applicati
33、ons we often need compute capabilities positioned close to the point-of-care.Data-residency rules also require us to handle some data processing within the healthcare facility either entirely or as a pre-processing step before moving data to the cloud,”said Rich Ridolfo,senior director of operations
34、 and infrastructure R&D,Philips Healthcare.“Today,we run these applications on separate infrastructure,and have to support separate development and infrastructure procurement models to deliver hybrid solutions to our customers.With AWS Outposts,we benefit from having a single set of AWS services,API
35、s,and management and security tools for applications running in the AWS Region and at our healthcare facilities,helping us accelerate the pace of healthcare innovation.”Bear in mind that your staff will need to develop more than just technical skills,such as learning the right strategies and pattern
36、s for moving applications to the cloud or using cloud-native services,and to optimally operate in the Cloud.An optimized cloud environment is one of continuous delivery,integration,and testingwhich means your developers will need to work in concert with your operations people in a DevOps culture.So,
37、for best results,integrate both technology and operational skills into your training plan.(Read more about DevOps in Best Practice#8.)Advance your IT staff:Learning Paths for Training and Certification How Can Government Grow and Recruit Digital Talent?Getting Started with Training for the Cloud Tra
38、ining the Entire Enterprise to Harness the Clouds Full Value Establish accountable leaders&train your teams(contd)AWS can help you with this first step by conducting an application portfolio analysis.We have the right tools to help you review all your applications and classify them into three basic
39、categories:1)easy to move,2)medium or hard to move,and 3)save for last.By focusing your initial efforts on the first categoryapplications that can easily lift-and-shift to the cloud,with minimal or no rearchitectingyou can score some early wins and gain measurable results to solidify your business c
40、ase.This will also help you crystallize your approach and uncover learnings that you can incorporate before attempting larger,more complex migrations.As discussed in Best Practice#2(top-down,quantifiable goals),achieving initial cloud migration success usually requires a push.Dont let your efforts g
41、et stuck in analysis paralysisjust get started!Ship something to production that has immediate,tangible benefits.You need to prove that the journey is worth it and that there are fantastic,tangible benefits from going to the cloud.To keep everyone engaged,its best to do this as quickly as possible.B
42、egin by identifying one or more applications that can move quickly and easily to the cloud and will deliver highly visible benefits to the organization.48Get quick and early wins to build experience and your business caseGet quick and early wins to build experience and your business case(contd)9AWS
43、Resources to help you get quick wins:How to Go Fast We All Start Somewhere Partnering for AI Innovation Intuit Case Study Nationwide:Executing a large-scale migration to AWS(video)DB Systel Case Study The AWS Partner Network also features dozens of Managed Services Providers(MSPs)that can offer you
44、options for managing your AWS environment.High-quality,fast issue resolution is a critical element of cloud success.With the pace of the innovation,issues or questions about services are inevitable.The unique,customer-obsessed approach AWS Support brings a single-tier resolution model to issue resol
45、ution,having support engineers stay with cases from start to finish and avoiding handoffs that slow resolution times.AWS,hand in hand with the AWS Partner Network,is how you can move faster and achieve success with your cloud adoption plan.For example,with AWS customer enablement services,National A
46、ustralia Bank was able to train over 4,000 IT staff members,achieve regulatory compliance approval,implement its first cloud-based data lake,and complete a large-scale migration project of over 30 applications in less than two months.10We understand that every migration is different;however,based on
47、 our experience with over a million active customers and helping organizations of all ages,industries,and geographies migrate to the cloud,we have seen a standardized migration process take shape.This process can generally be broken into three phases of activities:1)assess,2)mobilize,and 3)migrate a
48、nd modernize.Following the process across each of these phases is essential to success.Well explain why as we go,but lets start by taking a deeper look at these phases individually,showing you how AWS can help you properly implement them and achieve the best results.The first phase involves assessin
49、g your organizations current readiness for operating in the cloud.In the last Best Practice,we talked briefly about how AWS can help you with this phase by conducting an application portfolio analysis.Now,lets look at the assessment stage more holistically and see what other AWS services and product
50、s can help you along the way.5Trust the process&capitalize on modernization opportunitiesA number of AWS tools enable you to assess your on-premises resources and build a right-sized and optimized cost projection for running applications in the cloud.That initial assessment enables you to deep dive
51、into building your business case by understanding the right resources you will need to run your workloads on AWS.Our Migration Readiness Assessment is a process of gaining insights into how far along you are in your cloud journey,understanding your current cloud-readiness strengths and weaknesses,an
52、d building an action plan to close identified gaps.You can use the AWS Cloud Adoption Framework(CAF)and its six perspectives(business,people,governance,platform,security,and operations)as a guide to help ensure that you have a holistic view of the transformation initiative that is required for an ef
53、fective move to the cloud.Your assessment could lead to a deeper engagement with TSO Logic,an AWS company that will help you avoid inflated bills for your cloud infrastructure and use only the resources that your specific applications need.Refer to the AWS Migration Readiness Guide to learn more.11N
54、ext,youll need to mobilize your organization with a detailed migration plan and a refined business case.In this phase,youll address gaps in your organizations readiness that were uncovered in the assessment phase,with a focus on building your baseline environment(aka the“landing zone”),driving opera
55、tional readiness,and developing cloud skills.A strong,achievable migration plan starts with a deeper understanding of the interdependencies between applications and evaluates migration strategies to meet your business case objectives.One critical aspect of developing your migration strategy is to co
56、llect application portfolio data and rationalize appli-cations using the seven common migration patterns:relocate,rehost,re-plat-form,refactor,repurchase,retire,or retain.(Well get deeper into these“7 Rs”in the next section,Best Practice#6.)While not every decision in a migration can be automated,th
57、ere are a number of AWS tools you can use to drive smarter migration choices and processes.The AWS Application Discovery Service automatically collects and presents detailed information about application dependencies and utilization to help you make more informed decisions as you plan your migration
58、.AWS Migration Competency Partners,such as RISC Networks,Cloudamize,ATADATA,Slalom,Deloitte,and Turbonomic,also provide deep discovery and planning tools.AWS Migration Hub automates the planning and tracking of application migrations across multiple AWS and partner tools,allowing you to choose the m
59、igration tools that best fit your needs.Finally,its time to migrate and modernize your applications while optimizing operations along the way.During this phase,each of your applications will be designed,migrated,and validated.AWS Migration Hub allows you to quickly get progress updates across all of
60、 your migrations,easily identify and troubleshoot any issues,and reduce the overall time and effort spent on your migration projects.While migrating with AWS,you iterate on your new foundation,turn off old systems by cutting those over,and constantly evolve toward a modern operating model.Your opera
61、ting model becomes an agile set of people,processes,and technology that improves as you migrate more applications and gain invaluable experience operating in the cloud.Many enterprises use the migration effort to also modernize their businesses by refactoring their legacy technology portfolio.Taking
62、 this opportunity to modernize will accelerate innovation and increase agility,resiliency,and efficiency to transform your speed to market and customer outcomes.Some proven ways to do that include:Trust the process&capitalize on modernization opportunities(contd)Infrastructure automation(elastic inf
63、rastructure,containers,introducing AI/ML into automation)Agile development practices(DevOps,test automation,CI/CD,observability)Cloud-native architectural patterns(stateless,microservices,serverless,data lakes,AI/ML in applications)Product-based operating models(product teams,business outcome alignm
64、ent,full-stack vs.platform structures)Independent research by ESG demonstrates that enterprises that follow these prescribed migration procedures reap bigger rewards from their cloud migrations than ones that take a different approach.2 According to the study,organizations that adhere to migration b
65、est practices are:3.7 times more likely to be completely satisfied with cloud services in use 2.5 times more likely to report that typical savings for migrated workloads exceed 15 percent.2.9 times more likely to report that they typically eliminated downtime for migrated workloads 2.8 times more li
66、kely to report that the cloud has significantly improved their business By following migration best practices,Intuit Mint achieved fast,quantifiable results in its move to AWS,freeing up at least 15 percent of its database administrators time,lowering costs by 25 percent,and reducing the time needed
67、 to complete failover scenarios from 30 minutes to one minute.3As you iterate and migrate more applications,you will be able to drive repeatability and predictability in processes and procedures.Thats why its so important to trust the process and continue to go through the three phases described abo
68、vethe more you migrate,the better and faster youll get at it,easing the transition and helping you unlock the full benefits of the cloud.12Resources to help you modernize your architecture:AWS Management and Governance AWS Managed Services(AMS)AWS Marketplace Learn how AWS customers modernized their
69、 architectures:Capital One|Delaware North|McDonalds 2 Adam DeMattia,Mark Bowker,and Jennifer Graham.“Analyzing the Outcomes Organizations Experience When Migrating Workloads to Cloud Infrastructure.”ESG Research Insights Paper,2019.3 https:/ the process&capitalize on modernization opportunities(cont
70、d)Theres more than one way to migrate an app.Common migration patterns usually follow one of seven basic patternsbut when you migrate to AWS,youll gain a seventh option(relocate),rounding out what we refer to as“The 7 Rs.”Creating a detailed strategy that identifies the best pattern(s)for your appli
71、cations is essential to creating/sustaining momentum and capitalizing on opportunities for modernization along the way.As you embark on this major transformation,embrace hybrid architectures that will help you sustain your business,while migrating to the cloud.Below are the details on each of these
72、seven patterns as we see them adopted most often by our customers.1.Relocate:Regarding AWS migrations specifically,this option allows you to move vSphere-based applications to the cloud without changing them in any way.2.Rehost:Also known as“lift-and-shift,”this pattern is often used for large-scale
73、 migrations that need to be completed quickly.3.Re-platform:Sometimes called“lift-tinker-and-shift,”this option involves making a few cloud optimizations in order to achieve tangible benefits,but without changing the core architecture of the application.4.Repurchase:Casually referred to as“drop and
74、shop,”this is a decision to replace your current environment by moving to a newer version of software or purchasing an entirely new solution.5.Refactor:Also called“rearchitecting,”this pattern involves changing the way the application is architected and developed,usually in an effort to add or enhan
75、ce capabilities.This is often done with modern application development technologies and practices that generally function better in the cloud,such as serverless computing,microservices,containers,and continuous integration/continuous delivery(CI/CD).6Choose the appropriate migration pattern&embrace
76、hybrid IT1313RefactorRe-platformRepurchaseRehostRelocateRetainRetireLevel of effortMigrationplan(Backlog)6.Retain:Choose this option for applications you plan to keep on-premises.We recommend you remain open to migrating them laterbut for now,you can use AWS Outposts to combine them with your cloud
77、assets for a truly consistent hybrid experience.Well talk more about hybrid in just a moment.7.Retire:Simply decommission or archive unneeded portions of your IT portfolio.While most applications can be easily migrated to the cloud,some applications remain on-premisesnecessitating a hybrid IT archit
78、ecture.Inevitably,there will be a periodwhich could last for some yearswhere youre operating a hybrid architecture,with some applications and workloads in the cloud and others staying on-premises.Youll need to periodically prioritize and re-evaluate what to move and what to keep,especially as the pa
79、ce of innovation in the cloud opens up new opportunities virtually every day.During this time,youll need to continue to communicate your cloud-first plan:For every applicationfrom the newest web service to the oldest legacy systemthe question isnt“Why the cloud?”but“Why NOT the cloud?”Youll need a w
80、ell-thought-out strategy that sees you increasingly moving legacy applications into the cloudincluding the big,monolithic,complex legacy applications that are critical to your business,by using either the repurchase or the refactor approach.A small proportion of these legacy applications may need to
81、 live on-premises for a forseeable amount of time.These are the ones for which theres a good answer to the basic cloud-first question:“Why NOT the cloud?”It may be that the data is too sensitive,the application cant be rearchitected,the application has low latency or local data processing requiremen
82、ts,or the data cant be moved for data sovereignty regulations.Look into AWS Outposts here,to get rid of your legacy data center assets.To ensure you have a hybrid IT architecture that meets your needs today and tomorrow,youll want to choose a cloud provider that has the breadth and depth of services
83、 and features to address the broad spectrum of hybrid use cases,from integrating on-premises IT resources with cloud resources to delivering cloud services,APIs,and operating models to your on-premises and disconnected edge locations.And,since a hybrid architecture functions as an extension of your
84、IT environment,you need a cloud provider with a reliable and global infrastructure to support your business operations and a provider that helps you meet stringent security and compliance requirements.Getting everyone on board and having a well-thought-out,well-documented,and well-communicated hybri
85、d strategy will make this transition period easier to manage and faster to complete.14Choose the appropriate migration pattern&embrace hybrid IT(contd)15Choosing the right migration pattern(one of the“7 Rs”)for the right workloads can help you avoid stalls and slowdown in the process.Before we get i
86、nto methods to overcome stalls,lets understand why migration and modernization stalls usually happen in the first place.Since we referred to the methods of migration as“patterns,”well call these barriers“anti-patterns.”Anti-pattern#1:Continuous renewal of executive buy-in Youll need to ensure that y
87、our migration business case is strong enough to maintain continuity throughout personnel changes and the departure and arrival of critical leadership stakeholders.Failing to do so can trap you in a cycle of continuous executive buy-in renewal.When new leaders enter your organi-zation,youll lose prec
88、ious time representing the argument for migration and awaiting approval.Anti-pattern#2:Slow cycle plan with big projects Attempting to migrate too much at once over too long of a timelinethe so-called“Big Bang approach”can create substantial migration stalls.A workload usually consists of many compo
89、nents,modules,and dependencies(such as storage,load balancer,etc.).Trying to migrate and modernize everything simultaneously may mean dealing with too many challenges all at once.As migration timelines get longer,business benefits get further and further delayedjeopardizing your companys commitment
90、to the project.Some businesses find themselves stuck in this anti-pattern when they attempt to break monolithic applications into microservices.These businesses get into real trouble when they try to break all of the components down in offline modewhich may take several monthsand then bring the new
91、system online all at once.This creates too much risk,extends the time before value is passed on to the business,prevents your hypothesis from being validated,and causes the pains of the existing system continue to remain longer than necessary.A modern approachand a way out of this anti-patterncould
92、be to gradually chip away parts of a monolith in modular fashion onto a cloud-native architecture.Anti-pattern#3:Non-convergent pursuits Its tempting to jump into migration with the goal of addressing big problems to achieve flashy results.While setting your sights high is a good thing in general,ke
93、ep in mind that those“big problems”and“flashy results”take on very different forms across various parts of the organization.This anti-pattern occurs when disparate teams and departments within a business are looking toward migration to achieve non-convergant goals.Perhaps one team wants to fix appli
94、cation architecture and assumes that making it modular would help issues,while another believes adopting agile engineering processes is the silver bullet.At the same time,the Operations team may try to automate away the processes in order to appear to drive efficiency.These are all valid pursuits,bu
95、t pulling parts of organizations in different directions without having a convergent point is unlikely to produce desired results for anyone.7Avoid stalls,sustain&accelerate momentum Avoid stalls,sustain&accelerate momentum(contd)Anti-pattern#4:Serialized,dependent execution While non-convergant pur
96、suits are a major cause of migration stalls,pursuits that converge in too singular a fashion can be just as detrimental.If the entire migration effort is focused on one business impact or goal,it can become dependent on serialized executionwherein,if one element fails at a particular step,the whole
97、project is halted and unable to proceed.Creating a migration plan with several interdependent activities can slow down teams.Oranizations exhibiting this anti-pattern often address migration in serial orderbuilding automation,building the productivity platform,defining access tiers,and then finally
98、arriving at application architecture.This anti-pattern can manifest in a number of ways.Perhaps the organization is forced to wait on the development of a DevOps platform or for all the components of cloud foundation to be fully adopted before workloads can start to use them.Or the central IT team r
99、estricts the development teams access to services until the organization-wide foundation tier is built.No matter how it happens,businesses can avoid this anti-pattern by ensuring they balance non-convergant pursuits in a way that doesnt cause them to converge in a serial,waterfall-like process.So ho
100、w can you avoid these stalls?One way is to refactor existing infrastructure,architecture,portfolio,and organization in small increments to deliver business value quickly and continuously.This can be achieved by keeping your organization focused on what we like to call“The Five Dimensions,”and two el
101、ements of the“Modern Technology Strategy”:16The Five Dimensions1.Infrastructure automation Create reusable,repeatable mechanisms using automation and free up valuable engineering resources for repetitive,time-consuming,human-error-prone tasks.2.Builder springboards Use self-service reference archite
102、cture,templates,CI/CD,zero down time deployments,and built-in monitoring/logging/notifications to create a builder-friendly platform with reusable patterns and libraries that helps developers accelerate their ideas from inception to production.3.Ubiquitous access to data Identify the types of data y
103、ou need and their sourcesaggregations,trends,reports,archives,etc.Consider how much of this data needs to be real-time vs.periodic and how/if/when that data will be consistent across different geographies.Establish mechanisms that democratize data within your organization through consumable nuggets
104、of access patterns and insights,and empowering team members to choose the right tools for the right job.4.Architecture evolution Build modular,scalable,reliable architecture.This will enable rapid composition,easier experimentation,and multi-axis scaling,while containing issues to isolated modules t
105、hrough built-in support for failover and failback policies ultimately preventing the domino impact of failure from impacting the entire system.5.Organization for value Weve seen many customers make great strides across the previous four dimensions,but struggle with the organizational changes needed
106、to hold them all together.To avoid this,your business must establish fixed accountability and ownership of all services.This can be done by rethinking organizational approaches to your people,processes,and cultural practices,ensuring that all are working together to achieve the same valuesboth inter
107、nally and for your customers.Were not recommending that you attempt to apply all five of these dimensions to your entire organization all at once.Migration and modernization success means starting fast but also starting small.Choose a concrete task,project,goalor even a single application or feature
108、and see how you can rethink it to deliver on the five dimensions.Scale from there,applying your learnings as you go.1717Avoid stalls,sustain&accelerate momentum(contd)1818Learn more about how AWS and our partners have helped our customers move to AWS:SGN Case Study Sony DADC NMS Case Study Find the
109、right enablement partner:AWS Partner Network Migration Partner Solutions AWS Managed Services AWS Professional Services complexities involved,share the slices by spliting up your initial MVP team to seed new product teams.Harden shared services for infrastructure and tools.Finally,execute a change m
110、anagement plan that includes training and skills development.2.High frequency deliveries:Deliver more often to validate the hypothesis and value proposition.This will help enable innovation across all your lines of business.The“Five Dimensions”and“Two elements”are most successful when jointly sponso
111、red by both technology and business functions.Identify technology and business sponsors and set the tone for a value-driven sponsorship.Then organize teams within those partnerships around the creation of new features,services,or products.Conceptually,rallying around the five dimensions is critical
112、to sustaining momentum in your migration and modernization initiatives.But there are other ways to think about the five dimensions,other than how they have been outlined above.Another viewpoint weve found helpful is to deliver on the five dimensions from a value perspective.This larger objective can
113、 be broken into two elements:1.Vertical slicing:The best way to experience the flavors of all layers of the cake is to cut is verticallyand the same is true for cloud migration.To drive early business results,gain momentum,validate components across architecture,and to prove value across all five di
114、mensions,first prioritize use cases and carefully select an initial MVP scope.Then use resources to create new capabilities or enhance/simplify existing ones.Finally,deploy the MVP to customers,analyze the results,and iterate to optimize further.Now that team has learned the flavor of the different
115、Avoid stalls,sustain&accelerate momentum(contd)Now that youre(ideally)operating in a cloud-first world,a DevOps operating model becomes the norm.With this transition comes a frequent assumption that implementing DevOps“correctly”means giving developers the ability to manage the full lifecycle of the
116、ir applications and the platform services that support them.While there will certainly be specific use cases where this“full stack,full lifecycle”approach to DevOps makes sense,most enterprises will benefit from having a central team that handles the undifferentiated heavy lifting of configuring and
117、 integrating AWS platform services on the developers behalf.This is especially true for large enterprises with a varied application portfolio.This approach ensures the platform services supporting your applications adhere to corporate standards for architecture,operational excellence,security,and co
118、mplianceas well as financial controlswithout burdening developers with these platform governance concerns.Implementing a core team for these platform services frees development teams to focus on maximizing the business impactand valueof their applications.Developers can then migrate and optimize the
119、ir applications faster,using standardized,self-service enterprise capabilities.This core team within your company becomes your“Cloud Enablement Engine.”8Build your Cloud Enablement Engine19Your Cloud Enablement Engine(CEE)provides products and shared services to your internal customers.These product
120、s and services accelerate cloud adoption while keeping adoption sustainable and secure.There are two key components to your Cloud Enablement Engine:Cloud Business Office(CBO):The CBO provides products or services for business and financial management and governance and ongoing train-ing,as well as c
121、hange management to ensure the organization success-fully embraces adapting to life in the cloud.Cloud Platform Engineering(CPE):The CPE team configures and codifies the AWS platform to align with enterprise standards for architecture,operations,security,and finance.CPE then packages and continuousl
122、y improves these standards as self-service deployable products and consumable services.These products and shared services add up to a large responsibility for the Cloud Enablement Engine.That said,you dont(and shouldnt)build it all at once.At AWS,we frequently say,“think big,but start small.”Start w
123、ith a single,small“Cloud Foundation Team”made up of a product owner,financial analyst,organization change management specialist,and engineering manager and include architects and engineers who have the domain expertise to design and build products related to Platform,Operations,and Security.SAP Conc
124、ur started small and independently with individual teams that embraced the pure DevOps model.These highly effective agents of change helped create the organizational pressure to move fast.Cameron Etezadi,Chief Architect of the company,is quick to point out that he doesnt consider the instantiation o
125、f a Cloud Enablement Engine to be the endpoint,either.“Change is the new normal.”20AWS resources to help you get the most value from the cloud faster:Accelerate Large-Scale Migrations Derisking Enterprise Migration with AWS Managed Services Watch the video to learn more about CEE Resources to help y
126、ou establish a Cloud Enablement Engine:Get current insights from our Enterprise Strategy blog Build your Cloud Enablement Engine(contd)Once youve proven the cloud value to your business through the first applications your Cloud Foundation Team built and/or migrated,youll need a strategy in place to
127、keep your adoption plan moving forward and to see greater benefits from your cloud transformation.Many leading businesses,such as the ones listed throughout this eBook,have found that the answer is to free up their IT resources with a large-scale,rapid migration of their applications to AWS.When you
128、r team sees that youre committed to rapidly migrating to the cloud,they tend to get on board faster.More people develop cloud skills,and momentum accelerates.The benefits of breaking free from your legacy IT environment and practices are just too compelling to move slowly:Much lower IT costs Elevate
129、d security and operational resiliency The agility to move faster than competitors An on-demand environment for experimentation and innovation Near-infinite resources to support game-changing initiatives This is where every organization wants to beand when“cloud first”becomes your standard,youre ther
130、e.You can move fast,deploy new services globally,improve your time to market,free up real estate,innovate on the fly,and respond to changes faster than you would without a cloud-first strategy.Conclusion&next stepsSo what are you waiting for?Here are some resources that will help jump-start your jou
131、rney into the cloud:Evaluate your organizations cloud-readiness with an interactive assessment Begin your AWS Cloud migration training Learn more about AWS or start your migration today Prepare for the cloud:Cut through the mythology surrounding cloud security,compliance,culture,expertise,and perfor
132、mance.What are your cloud drivers?Reducing Risk in the Cloud by Overcoming the Status Quo Bias 5 Steps to Building a Culture of Security AWS Control Tower and AWS Security HubPowerful Enterprise Twins 12 Steps to Get Started With the Cloud Follow cloud pioneers:Migrating to Cloud Lessons from Netflix 21 2020,Amazon Web Services,Inc.or its affiliates.All rights reserved.