Pilih preferensi cookie Anda

Kami menggunakan cookie penting serta alat serupa yang diperlukan untuk menyediakan situs dan layanan. Kami menggunakan cookie performa untuk mengumpulkan statistik anonim sehingga kami dapat memahami cara pelanggan menggunakan situs dan melakukan perbaikan. Cookie penting tidak dapat dinonaktifkan, tetapi Anda dapat mengklik “Kustom” atau “Tolak” untuk menolak cookie performa.

Jika Anda setuju, AWS dan pihak ketiga yang disetujui juga akan menggunakan cookie untuk menyediakan fitur situs yang berguna, mengingat preferensi Anda, dan menampilkan konten yang relevan, termasuk iklan yang relevan. Untuk menerima atau menolak semua cookie yang tidak penting, klik “Terima” atau “Tolak”. Untuk membuat pilihan yang lebih detail, klik “Kustomisasi”.

Using the DevOps Guidance - DevOps Guidance
Halaman ini belum diterjemahkan ke dalam bahasa Anda. Minta terjemahan

Using the DevOps Guidance

To effectively use the DevOps Guidance in conjunction with the AWS Well-Architected Framework, follow these steps:

  1. Familiarize yourself with this document, the broader AWS Well-Architected Framework, and the individual Well-Architected Framework pillar whitepapers.

  2. Gather your organization's design documentation, operational procedures, and monitoring history related to DevOps practices (where available).

  3. Compare your organization's DevOps capabilities to the best practices, anti-patterns, and metrics described in this guidance.

  4. For each best practice, record whether it has been followed and prioritize evaluating those that are required.

  5. Use the provided suggestions to address the areas where your DevOps capabilities are not well-architected.

  6. If you require additional expert guidance, contact your AWS account team to engage a DevOps specialist Solutions Architect (SA).

After reviewing your DevOps practices against the DevOps Guidance, you will have a list of best practices that highlight areas where your organization and systems are well-architected, and where there may be room for improvement.

  • For the well-architected architectural components: Share your knowledge among your teams to amplify them across your organization.

  • For the best practices that your organization does not follow yet: Treat them as technical debt and potential risks to your adoption of DevOps practices. Follow your internal risk management process to continuously monitor and improve these risks.

  • For areas that require further in-depth analysis or assistance with remediation: Contact AWS Professional Services or consult with AWS Partners.

For more details, see The review process in the AWS Well-Architected Framework whitepaper.

Join the DevOps discussion

Engage with the AWS DevOps community for tutorials, best practices, and insight into how others are practicing DevOps. Join the discussion over at AWS re:Post if you have additional questions about the Well-Architected Framework DevOps Guidance or implementing DevOps on AWS. AWS DevOps experts regularly monitor the re:Post DevOps topic for discussion and questions that could be answered to assist our customers and partners following DevOps practices with AWS.

PrivasiSyarat situsPreferensi cookie
© 2025, Amazon Web Services, Inc. atau afiliasinya. Semua hak dilindungi undang-undang.