Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Match AWS Pori - Rolf Koski - Cybercom

71 views

Published on

How to build Enterprise Cloud Governance model, without being boring or cumbersome

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Match AWS Pori - Rolf Koski - Cybercom

  1. 1. Match AWS – Pori 26.9.2018
  2. 2. powered by User Group Finland AWS User Group Finland Meetup https://www.meetup.com/awsfin/
  3. 3. Who am I? Rolf Koski Chief Technologist Cybercom – Cloud Services AWS Community Lead AWS APN Partner Ambassador https://therolle.com/ twitter: @therolle
  4. 4. No Cloud Moving to Cloud In the Cloud Delivery and Operations Trusted Cloud Partner 5 Advisory Services Enterprise Architecture Cloud Transition Migrations Optimization & Operations Efficiency Risk & Security Management DevOps teams Cloud Native Workloads Business Innovations OnboardingLean Way-of-Working Passionate Support 24/7 Proof of Concept
  5. 5. Advisory Services Cloud Services Professional Services Passionate Support Cloud Capacity
  6. 6. Passionate Support for AWS – Three different service levels – 24/7 Service desk – Local AWS Architects – Support is backed by Enterprise level AWS support
  7. 7. Without being boring or cumbersome Enterprise Cloud Governance
  8. 8. • Governance encompasses an organisation’s mission, long-term goals, responsibilities, and decision making. • Gartner describes IT governance as “the processes that ensure the effective and efficient use of IT in enabling an organization to achieve its goals”. What is Governance
  9. 9. How do Strategy, Governance and Operations relate?
  10. 10. Cloud Transition Strategy Governance Operations Onboarding Policies Management SECURITY
  11. 11. The Governance Challenge
  12. 12. • Define rules to provision resources • Discover resources and changes • Monitor compliance • React (manage, report, respond) to changes The Governance Challenge … but without compromising agility and innovation
  13. 13. Why would You need Governance?
  14. 14. • To be efficient • Reduce and manage risks • Ensure regulatory compliance • Being effective with cost • Enable and communicate correct way of doing IT • Reducing shadow and rogue IT • Enable speed and innovation without increasing risks Why would You need Governance?
  15. 15. Steps to Cloud Governance
  16. 16. Steps to Cloud Governance No Governance • Minimal interaction • Reactive environment • Manual administration • Unpredictable cost • No structure Adoption • Policies maturing • Rapid deployment • Education and communication • Common language forming Mature • Automation driven • Self service • Speed with control • Built in security • Built in compliance • Understanding
  17. 17. • Create Frameworks and Documents – Policies – Principles – Guidelines • Include Decision Makers and Influencers • Individuals • Other Entities • Create good atmosphere and spirit What you need to succeed?
  18. 18. • Documentation • Automation and Deployment • Compliance tracking • Monitoring • Logging • Analytics Creating Tooling
  19. 19. • Enable changing culture • Top down enablement - not enforcement • Increase communication • Promote autonomy • Executive sponsorship • Training and education Developing Culture
  20. 20. • Speed • Integration • Balance • Proactivity • Enablement Opportunities
  21. 21. Basic Definitions Service Design Rules Service Lifecycle Governance Roles Governance Processes Governance Metrics • Create a handbook of how your company acquires and uses cloud platforms • Utilize cloud best practices • Meet the requirements set for operations, availability, continuity and security • Control service operations in the cost efficient way
  22. 22. …provide the leadership, transformational capability, best practice, research, governance, support and training to the organisation for cloud native apps as well as on-premise/co- location workloads and those moving to the new construct; as well as those being retained, maintained or retired from their current legacy environment. This can be called for example Cloud Center of Excellence You will need to…
  23. 23. 24 Thank You!

×