Visibility and Control in the Cloud

  • Published on
    14-Apr-2017

  • View
    542

  • Download
    2

Embed Size (px)

Transcript

<p>PowerPoint Presentation</p> <p>Visibility and Control in the Cloud: How to get your boss comfortable with AWS</p> <p>AGENDAWhy are organisations moving to AWS?What it takes to maximise the Cloud opportunityThe AWS Adoption JourneyThe 5 steps to achieving organisation-wide visibility and control of AWSHow does CloudMGR help?</p> <p>Why Visibility and Control are essential for maximising the benefits of AWS ?</p> <p>Implementing AWS does not automatically mean improvements to speed, agility or cost savings without adequate management</p> <p>Cost Savings</p> <p>SpeedAgility</p> <p>The right choice of CloudVisibility and ControlEfficiencyInnovation</p> <p>Implementing AWS does not automatically provide an organisation with the benefits of cost savings speed, agility, efficiency and innovation. </p> <p>In our experience, these benefits are achieved gradually as organisations move through the stages of their Cloud adoption journey. </p> <p>Perhaps more important to realising the full range of benefits that full-scale cloud adoption offers is getting visibility and control of your Cloud environment at each stage</p> <p>ExploreAdoptExpandTransformTHE AWS ADOPTION JOURNEY</p> <p>Visibility &amp; Control</p> <p>The phases of the AWS Adoption Journey.</p> <p>Briefly describe the phases including mentioning that at the explore stage due to the limited adoption and usage visibility and control does not present a significant organisational challenge.</p> <p>Develop a visibility frameworkMove culture from CAPEX to OPEXCreate a governance structureBuild self service capabilityTap into the partner ecosystem5 REQUIREMENTS FOR VISIBILITY AND CONTROL</p> <p>Today were going to look at 5 specific visibility and control requirements that apply at various stages of the AWS adoption journey.</p> <p>These requirements arise progressively </p> <p>DEVELOP A VISIBILITY FRAMEWORKWhats actually running?</p> <p>Use tools to bring visibility to Cloud consumption:AWS ConsoleAWS APIThird party billing and cost management tools</p> <p>Standardise which services are used so that business units can build on and adapt them</p> <p>Control Shadow IT</p> <p>1</p> <p>One of the first Challenges that organisations experience in the adopt stage, as the usage of AWS first starts to spread from small, easy to control test environments to wider scale adoption is to work out, what is actually running? </p> <p>TAP INTO THE PARTNER ECOSYSTEMUse partner tools to simplify:Billing and cost managementSetting up a self service portalPerforming optimisation tasks</p> <p>2Technology PartnersLeverage the consulting partner network to:Perform migration tasksDevelop governance practicesOutsource service management</p> <p>Consulting Partners</p> <p>Tapping into the partner network can be valuable at all stages of the Adoption Journey.AWS has the largest and most sophisticated partner network of any public cloud platform. Within the partner ecosystem there is a lot of expertise that organisations can tap into in order to accelerate the pace of their Cloud adoption. Different types and different levels of partner services are applicable based on the unique characteristics of an organisation as well as their level of Cloud adoption.Early on the Cloud journey [customer example of how a partner is useful]Later as organisations expand their AWS adoption. [customer example of how a partner is useful]In fact for each of the 5 requirements we discuss today, partners can be the fastest way to achieve the necessary requirements so as to unlock the full benefits of the Cloud.</p> <p>MOVE FROM A CAPEX TO OPEX CULTURE3CAPEX has been the main business budgeting mechanism for IT</p> <p>OPEX requires a change in thinking from IT and Finance:</p> <p>Comfort with distributed access Resource responsibility beyond ITAvoid out of sight, out of mind thinking</p> <p>A major jumping off point, generally at the Expand stage, is moving from a CAPEX to an OPEX Culture: The capital expenditure (CAPEX) accounting approach has traditionally been the primary mechanism for IT budgeting for most companies, but a transition to the operating expenses approach (OPEX) does provide certain benefits.CAPEX Approach: Capital expenses are costs expended to obtain benefits that continue over a long period, rather than being exhausted immediately or short term. OPEX Approach: Ongoing costs for running a system, product or service fall under OPEX. Any process that involves a daily expense is an operating expense, including payroll, marketing, research and development. OPEX Advantage: Usage of AWS for cloud services isnt a perfect fit for the capital expenditures approach to accounting. While CAPEX may work for hardware, like PCs and servers, treating cloud computing costs as an operating expense is more logical from an accounting standpoint. However, making the switch requires a change in thinking for your IT and Finance departments. Its important to get buy-in from both units so theyre comfortable with distributed access to the environment and can help promote responsible consumption </p> <p>CREATE A GOVERNANCE STRUCTURE4Maintain compliance with best practices, corporate governance requirements and security by corporate users and service providers:Develop a usage and control policyControl risk with Cloud governance Manage access and permissionsReview compliance via regular audits</p> <p>Critical to success at the expand stage is creating an appropriate Governance StructureOrganizations must implement best practices for corporate governance requirement and security, for all organization users and service providers.Develop a Usage &amp; Control Policy: All employees must abide by usage and control rules that you set in place for cloud services, including those for shadow IT and IT-deployed systems.Manage Access: A strict permissions policy, including password protocol, ensures that you have control over access to the AWS cloud.Conduct Regular Audits: Review compliance with usage and access policies by conducting audits within the organization. Also, make sure all employees are aware that audits will be conducted for better performance and accountability.</p> <p>BUILD SELF SERVICE CAPABILITY5Give teams controlled access to manage their own resources:On demand accessAutomation toolsCost control mechanisms</p> <p>Self services gives teams the agility to experiment and be innovative</p> <p>In order to experience the transformational benefits of the later stages of Cloud adoption, organizations need to build Self-Service Capability: Self service provide different divisions within your organization controlled access to AWS to manage their own systems. Self-service capability gives your team the assurances they need to be innovative and experimental in development.On Demand Access: Make sure that your employees have access to AWS on an as-needed basis, so they have the required resources available when needed.Automation Tools: Automating certain routine tasks frees up time that staff can apply to other projects that require their attention.Cost Control Mechanisms: Within AWS, you can implement cost control mechanisms that ensure proper self-service usage.</p> <p>Develop a visibility frameworkHOW DOES CLOUDMGR HELP?Create a central control Dashboard</p> <p>Cloud Dashboards on what is running where !</p> <p>Insights with Actions </p> <p>Move from CAPEX to OPEX cultureHOW DOES CLOUDMGR HELP?Chargebacks and Cost Centers</p> <p>Enhanced billing and cost management lets users:</p> <p>Assign products and resources to Cost Centers within your businessAutomatically apply markups and bill customers for accounts you manageMonitor, compare and budget resource use by internal or external customersEasily set billing and budget alerts</p> <p>Build self service capabilityHOW DOES CLOUDMGR HELP?CloudMGRWhite Label</p> <p>Your Cloud Your Way</p> <p>Service Provider Model </p> <p>- Customer or Partner Model- Your Brand- Your BundleCorporate Model </p> <p>- Business Unit- User Role- Customised to meet user and Biz requirements</p> <p>Craig DevesonCEO, CloudMGR</p> <p> + 1 415 375 9797 craig@cloudmgr.com</p>