Recognise early indicators that multi-region cloud architecture is drifting away from its intended design.
Designing Multi-Region High-Availability Cloud Architectures
Turn multi-region cloud architecture from a stated policy into a practice your organisation can evidence.
📍 Tunis🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Security and delivery speed are traded against each other in multi-region cloud architecture whether or not anyone says so. The documentation for this part of technology and systems delivery is accurate only until the next release. The content is relevant to those who own this area of technology and systems delivery and to those who are held accountable for its results. Participants take away a working set of documents supporting multi-region cloud architecture, ready to be adapted internally. Discussion is anchored to worked examples of this aspect of technology and systems delivery rather than to abstract argument. Comparative studies of this strand of technology and systems delivery across sectors find the same handful of failure points recurring. It establishes a shared vocabulary for multi-region cloud architecture so that teams can disagree productively about it. The version of this part of technology and systems delivery described in the manual and the version practised on the floor tend to diverge over time. The programme ends where implementation begins, with this area of technology and systems delivery broken into steps someone can start on Monday.
Expected Learning Outcomes
Test the organisation's response to multi-region cloud architecture under conditions that are less than ideal.
Adapt recognised practice on multi-region cloud architecture to local constraints without hollowing it out.
Document multi-region cloud architecture to the level a new engineer could operate it.
Assess and manage third-party and cloud dependencies in multi-region cloud architecture.
Design the architecture of multi-region cloud architecture around its failure modes, not only its happy path.
Apply access control and least privilege throughout multi-region cloud architecture.
Who Should Attend
IT governance and audit staff reviewing multi-region cloud architecture.
Software engineers and technical leads building multi-region cloud architecture.
Members of committees that take decisions affecting multi-region cloud architecture.
IT managers and service owners responsible for multi-region cloud architecture.
Infrastructure and platform engineers operating multi-region cloud architecture.
Consultants and advisers supporting clients on multi-region cloud architecture.
Course Modules
Multi-region cloud architecture: requirements, targets and service levels
2 sessions · 8 pointsSession 1Setting availability and recovery targets for multi-region cloud architecture honestly
- Confirm that those complying with multi-region cloud architecture understand why it exists.
- Confirm every release of multi-region cloud architecture can be rolled back within a defined time.
- Define incident severity levels for multi-region cloud architecture and the response each triggers.
- Agree the indicators that will show whether multi-region cloud architecture is improving.
Session 2Dependencies and supply chain risk in multi-region cloud architecture
- Measure current load on multi-region cloud architecture and project it forward twelve months.
- Agree the smallest change to multi-region cloud architecture that would be visibly useful.
- Rank the weaknesses in multi-region cloud architecture by consequence rather than by ease of fixing.
- Check that multi-region cloud architecture still works when volumes rise unexpectedly.
Multi-region cloud architecture: monitoring, alerting and observability
2 sessions · 8 pointsSession 1Least privilege in multi-region cloud architecture without blocking the work
- Identify where judgement in multi-region cloud architecture is legitimate and where it is not.
- Apply change control to multi-region cloud architecture including emergency changes.
- Verify six months later that changes to multi-region cloud architecture have held.
- Assign responsibility for keeping documentation of multi-region cloud architecture current.
Session 2Closing out multi-region cloud architecture and capturing what was learned
- Assess the exit route from any cloud or vendor dependency in multi-region cloud architecture.
- Restore a backup of multi-region cloud architecture in a test environment and time it.
- Review access rights on multi-region cloud architecture and remove what is no longer needed.
- Establish what evidence demonstrates multi-region cloud architecture is under control.
Multi-region cloud architecture: backup, recovery and continuity
2 sessions · 8 pointsSession 1Documenting multi-region cloud architecture so someone else can operate it
- Identify the single points of failure in multi-region cloud architecture.
- Document the runbook for multi-region cloud architecture to the level a new engineer could use.
- Test the failover for multi-region cloud architecture rather than assuming it works.
- Record the technical debt in multi-region cloud architecture and schedule repayment.
Session 2Comparing multi-region cloud architecture with recognised practice
- Confirm that reporting on multi-region cloud architecture reaches the people who can act.
- Review logging on multi-region cloud architecture for coverage and retention.
- Inventory third-party dependencies inside multi-region cloud architecture and their update status.
- Build the internal briefing that explains multi-region cloud architecture to those affected.
Multi-region cloud architecture: security, identity and least privilege
2 sessions · 8 pointsSession 1The change to multi-region cloud architecture that caused the last outage
- Compare the cost of multi-region cloud architecture with the cost of its absence.
- Distinguish symptoms from causes when multi-region cloud architecture underperforms.
- Remove steps in multi-region cloud architecture that add effort without adding assurance.
- Estimate the resource multi-region cloud architecture requires to run as designed.
Session 2Keeping multi-region cloud architecture alive after the initial push
- Confirm data retention and deletion rules applied within multi-region cloud architecture.
- Configure alerting on multi-region cloud architecture that reflects what users experience.
- Confirm the support model and escalation path for multi-region cloud architecture.
- Collect evidence on the present handling of multi-region cloud architecture before proposing changes.
Choose the package that suits you
Silver Package
At least 3 people
USD1,250
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Gold Package
At least 3 people
USD1,850
- 5-night stay in a 5-star hotel
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Complete your registration
We will contact you within one business day to confirm.