This Guidance helps you implement the support capability so you can troubleshoot your cloud environment, integrate it into existing ticketing systems, submit tickets, and escalate issues to appropriate entities for timely responses, depending on the criticality and support level. Customized support capabilities will help you identify what your cloud environment needs to host production workloads. Customized support also helps you scale as your cloud usage increases.

Please note: [Disclaimer]

Architecture Diagram


Download the architecture diagram PDF 

Additional Considerations

Establishing a support capability within your organization is essential to achieving the correct operations. You can do this by defining your support requirements and documenting your support model for your cloud workloads. Integrating support for your cloud workloads in your new or current ticketing system will also help you escalate issues to the appropriate stakeholders when needed.

By using data collected through logs, the support capability will help you define KPIs and create dashboards to monitor the health of your environment. These dashboards also let you provide information about schedule maintenance windows.

Access to metrics and logs from your support team is essential. This will help you prepare for and respond to incidents quickly, minimizing or avoiding downtime of your production systems. Integrating support plans and tools from your cloud services provider, such as technical and billing support, into your support model will enhance your ability to identify cost-saving opportunities and learn from the collective experience of other customers in your industry.


The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

Was this page helpful?