2. 2
Program
Tidsplan
Utforsk ChatGPT og fremtidens språkteknologi
16:15-17:00 (45 min)
Pause
17:00-17:15 (15 min)
AWS er på full fart inn i det norske markedet – hvordan starte reisen?
17:15-17:45 (30 min)
Digitale tvillinger - store muligheter og stor risiko
17:45-18:15 (30 min)
Pause
18:15-18:30 (15 min)
Fotball, miljø og bærekraft med AI?
18:30-19:00 (30 min)
«Burger og Bar»
19:00
3. 59
AWS er på full fart inn i det
norske markedet –
hvordan starte reisen?
v/Håkon Eriksen Drange, Principal Cloud Architect
8. 64
• Beskriver hva som må til for å
lykkes med skytransformasjoner
• Basert på erfaring og beste
praksis hos AWS
• Systematisk fremgangsmåte for å
oppnå kunders forretningsmål
• Input til prioriteringer for “cloud
readiness” veikart
AWS CAF
Kilde: https://aws.amazon.com/cloud-adoption-framework/
13. AWS Well-Architected Framework
Creating a software system is a lot like constructing a building.
If the foundational elements are not solid, structural problems can undermine the integrity and function of the
building.
Similarly, if you neglect the Well-Architected Framework pillars when architecting technology solutions, it can become
challenging to build a system that delivers relevant functionality and meets your expectations.
Incorporating these pillars will help you produce stable and efficient systems, allowing you to focus on functional
requirements.
Kilde: https://docs.aws.amazon.com/wellarchitected/latest/framework/the-pillars-of-the-framework.html
14. 70
• Verktøy for å utvikle skyinfrastruktur i henhold til beste praksis
• Konsistent og systematisk fremgangsmåte for å evaluere arkitektur og
implementere sikre, skalerbare og kostnadseffektive systemer
• Idé og designfase
• Før produksjonssetting
• Ved omfattende endringer
• Input til produktbacklogprioritering
AWS Well-Architected Framework
«WAF»
Kilder: https://aws.amazon.com/blogs/mt/how-to-perform-a-well-architected-framework-review-part1/
https://aws.amazon.com/blogs/architecture/accelerating-well-architected-framework-reviews-using-integrated-aws-trusted-advisor-insights/
15. 71
AWS Well-Architected Framework kategorier
Operational Excellence Reliability
The ability for taking advantage of cloud
technologies to protect data, systems, and
assets in a way that can improve your security
posture.
The ability to support development and run
workloads effectively, gain insight into their
operations, and to continuously improve
supporting processes and procedures to deliver
business value.
The ability of a workload to perform its
intended function correctly and consistently
when it’s expected to.
Security
Performance Efficiency Sustainability
The ability to run systems to deliver business
value at the lowest price point.
The ability to use computing resources
efficiently to meet system requirements, and to
maintain that efficiency as demand changes
and technologies evolve.
The ability to continually improve sustainability
impacts by reducing energy consumption and
increasing efficiency across all components of a
workload by maximizing the benefits from the
provisioned resources and minimizing the total
resources required.
Cost Optimization
19. 75
• Kategorier med spørsmål
• Spørsmål med beste praksis anbefalinger.
• Hver beste praksis anbefaling har teknisk implementasjonsveiledning
Struktur
AWS Well-Architected Framework
20. 76
Any workload that has some form of network connectivity, whether it’s the internet or a private network, requires multiple layers of
defense to help protect from external and internal network-based threats.
Users, both in your workforce and your customers, can be located anywhere.
You need to pivot from traditional models of trusting anyone and anything that has access to your network.
When you follow the principle of applying security at all layers, you employ a Zero Trust approach.
Zero Trust security is a model where application components or microservices are considered discrete from each other and no
component or microservice trusts any other.
Security Pillar – Infrastructure protection
SEC 5: How do you protect your network resources?
21. 77
Beste praksis
1. SEC05-BP01 Create network layers
2. SEC05-BP02 Control traffic at all layers
3. SEC05-BP03 Automate network protection
4. SEC05-BP04 Implement inspection and protection
Security Pillar – Infrastructure protection
SEC 5: How do you protect your network resources?
Kilde: https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/protecting-networks.html
22. 78
Teknisk implementasjonsveiledning:
• Inspect and filter traffic at each layer.
• Network perimeter, NACLs
• Public subnets, load balancers
• Private subnets, security groups
• Enable AWS GuardDuty and configure automated alerts
• GuardDuty is a threat detection service that continuously monitors for malicious activity and unauthorized behavior to protect
your AWS accounts and workloads
• Configure VPC Flow Logs for network traffic logging
• Deploy AWS WAF (Web Application Firewall) to load balancers
Security Pillar – Infrastructure protection
SEC05-BP04 Implement inspection and protection
Kilde: https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/sec_network_protection_inspection.html
23. 79
A reliable workload starts with upfront design decisions for both software and infrastructure.
Your architecture choices will impact your workload behavior across all of the Well-Architected pillars. For reliability,
there are specific patterns you must follow.
The following questions focus on these considerations for reliability:
REL 3: How do you design your workload service architecture?
REL 4: How do you design interactions in a distributed system to prevent failures?
REL 5: How do you design interactions in a distributed system to mitigate or withstand failures?
Reliability Pillar – Workload architecture
24. 80
Controlled changes are necessary to deploy new functionality and to ensure that the workloads and the operating
environment are running known, properly patched software.
If these changes are uncontrolled, then it makes it difficult to predict the effect of these changes, or to address issues
that arise because of them.
Beste praksis:
1. REL08-BP01 Use runbooks for standard activities such as deployment
2. REL08-BP02 Integrate functional testing as part of your deployment
3. REL08-BP03 Integrate resiliency testing as part of your deployment
4. REL08-BP04 Deploy using immutable infrastructure
5. REL08-BP05 Deploy changes with automation
Reliability Pillar – Change Management
REL 8: How do you implement change?
Kilde: https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/implement-change.html
25. 81
Cloud Financial Management (CFM) enables organizations to realize business value and financial success as they
optimize their cost and usage and scale on AWS.
Best practices
1. COST01-BP01 Establish a cost optimization function
2. COST01-BP02 Establish a partnership between finance and technology
3. COST01-BP03 Establish cloud budgets and forecasts
4. COST01-BP04 Implement cost awareness in your organizational processes
5. COST01-BP05 Report and notify on cost optimization
6. COST01-BP06 Monitor cost proactively
7. COST01-BP07 Keep up-to-date with new service releases
8. COST01-BP08 Create a cost-aware culture
9. COST01-BP09 Quantify business value from cost optimization
Cost Optimization Pillar – Practice Cloud Financial Management
COST 1: How do you implement cloud financial management?
Kilde: https://docs.aws.amazon.com/wellarchitected/latest/cost-optimization-pillar/welcome.html?ref=wellarchitected-wp
26. 82
The economic benefits of just-in-time supply should be balanced against the need to provision to account for resource
failures, high availability, and provision time.
Depending on whether your demand is fixed or variable, plan to create metrics and automation that will ensure that
management of your environment is minimal – even as you scale.
Beste praksis:
1. COST09-BP01 Perform an analysis on the workload demand
2. COST09-BP02 Implement a buffer or throttle to manage demand
3. COST09-BP03 Supply resources dynamically
Cost Optimization Pillar – Manage demand and supply resources
COST 9: How do you manage demand, and supply resources?
Kilde: https://docs.aws.amazon.com/wellarchitected/latest/cost-optimization-pillar/manage-demand-and-supply-resources.html
30. 86
Raskere utvikling og lansering
• Redusere “brannslukking”
• Identifisere
kapasitetsutfordringer
• Bruke automatisering til å
eksperimentere
• Realisere verdi oftere
Redusert risiko
• Få innsikt i hvilke områder i
arkitekturen som kan innebære
risiko
• Adressere risiko før eventuell
negativ påvirkning på
virksomheten
Databaserte beslutninger
• Skape bevissthet om hvordan
arkitekturvalg og avveininger kan
ha ulike konsekvenser
• Mulighetsrom på kort og lang sikt
• Knyttet til forretningsmål
Nytteverdi
Å integrere WAFR i utviklingsprosesser kan hjelpe utviklingsteam på flere måter
Lær AWS beste praksis
• Gjøre team kjent med beste
praksis basert på tusenvis av
historiske gjennomganger
32. 88
Drawing from Amazon's own
transformative journey and the
expertise gained by AWS in
managing cloud services at
global scale.
AWS Well-Architected
Framework DevOps Guidance
offers a structured approach that
organizations of all sizes can
follow to cultivate a high-
velocity, security-focused culture
capable of delivering substantial
business value using modern
technologies and DevOps best
practices.
AWS Well-Architected DevOps Guidance
Lansert i går
Kilde: : https://docs.aws.amazon.com/wellarchitected/latest/devops-guidance/devops-guidance.html
35. 91
• Skytransformasjon kan være overveldende
• Decision guides inneholder en oversikt over ulike
tjenester på AWS-plattformen med råd om hva en
kan bruke for ulike formål og bruksområder.
Link: https://aws.amazon.com/getting-started/decision-guides/
Decision Guides
AWS Getting Started Resource Center