Overview of AWS Trusted Advisor Priority | Amazon Web Services
Overview of AWS Trusted Advisor Priority | Amazon Web Services
AWS Trusted Advisor Priority helps you focus on the most important recommendations to optimize your cloud deployments, improve resilience, and address security gaps. Available to AWS Enterprise Support customers, Trusted Advisor Priority provides prioritized and context-driven recommendations that come from your AWS account team as well as machine-generated checks from AWS services. In this demo, we will provide an overview of Trusted Advisor Priority.
Learn more: https://go.aws/3A5sr6O
Subscribe:
More AWS videos - http://bit.ly/2O3zS75
More AWS events videos - http://bit.ly/316g9t4
ABOUT AWS
Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers — including the fastest-growing startups, largest enterprises, and leading government agencies — are using AWS to lower costs, become more agile, and innovate faster.
#AWS #AmazonWebServices #CloudComputing
Content
0.634 -> AWS Trusted Advisor Priority helps you focus on the
3.25 -> most important recommendations to optimize your cloud deployments,
6.55 -> improve resilience
7.89 -> and address security gaps.
9.9 -> Available to AWS enterprise support customers,
12.43 -> it provides prioritized and context driven
14.73 -> recommendations that come from your AWS account team,
17.034 -> as well as machine generated checks from AWS services.
20.99 -> In this demo, we will provide an overview of trusted advisor priority.
25.33 -> As an enterprise support customer,
26.99 -> we can access trusted advisor priority by heading to the trusted advisor page
30.69 -> in the AWS console and clicking on the trusted advisor priority link.
35.13 -> Let's see what a typical enterprise support customer with a large
37.8 -> footprint across multiple accounts and regions on AWS would experience.
42.87 -> On the top left of this dashboard,
44.52 -> we find two metrics linked to recommendations requiring an action.
48.13 -> The number of recommendations pending a response
50.61 -> and the ones currently in progress
53.06 -> On the right side,
54.13 -> the overview block provides statistics such as the number
56.85 -> of recommendations rejected and resolved in the last 90 days
60.16 -> or the average time to resolve a recommendation
63.38 -> At the bottom,
64.29 -> we'll find the active prioritized recommendations that members of the
67.46 -> customer's AWS account team such as technical account managers,
70.97 -> solution architects,
72.48 -> customer solutions managers and account managers have identified
76.36 -> based on their knowledge of the customer's accounts,
78.4 -> business critical workloads and business goals.
81.65 -> Let's look at this recommendation.
84.29 -> As we can see in the detail page, this recommendation comes from Trusted
87.51 -> Advisor which has detected that an RDS snapshot is currently marked as public,
91.71 -> meaning it can be accessed by any AWS account or user.
95.62 -> The recommended action is to modify the permissions,
98.22 -> mark the snapshot as private and then specify
101.01 -> the accounts that we want to give permissions to.
103.99 -> To modify permissions for our snapshots directly, we can use an existing runbook.
108.62 -> The affected resource can be found at the bottom.
111.33 -> Because of the severity and potential impact,
113.55 -> we accept the recommendation and we provide our contact details.
117.42 -> To remediate, we execute the runbook by clicking on the link provided.
121.8 -> We fill in the snapshot identifier,
124.47 -> provide the account ID
125.65 -> that we want to share the snapshot with and finally click on execute.
131.56 -> The runbook has been executed successfully.
134.09 -> We can now resolve the recommendation in order to close it.
137.45 -> Let's look at another recommendation on the list pertaining to an
140 -> RDS instance which has been deployed in a single availability zone.
143.69 -> Multi AZ deployments
144.93 -> enhance database availability by synchronously replicating to a
147.95 -> standby instance in a different availability zone.
150.74 -> If our application requires high availability, then we
153.36 -> should modify it to enable multi AZ deployment.
156.31 -> The description provides a link to the AWS documentation on that topic.
160.34 -> Since it's related to a critical
161.73 -> workload, we will accept this recommendation and contact
164.5 -> the appropriate team so they can examine this recommendation and assess the risk.
169.52 -> Let's go back to the list of recommendations and
171.5 -> review this one created by our AWS account team.
174.79 -> They recommend we perform an AWS Well Architected review on an existing workload.
179.18 -> After reaching out internally to the key stakeholders,
182.11 -> we were informed that this particular workload is
184.39 -> actually scheduled to be decommissioned next month.
186.8 -> Therefore,
187.5 -> we decided that we don't need to invest time and effort
189.89 -> in an AWS Well Architected Review for this particular workload,
192.88 -> and we reject the recommendation by providing the
195.15 -> reason and filling in our contact details.
199.04 -> To learn more about trusted advisor priority, please visit the link shown below.
Source: https://www.youtube.com/watch?v=Jb1gb1g9Nw0