AWS Support plans and technical resources: re:Post, Knowledge Center, Prescriptive Guidance, Trusted Advisor and AWS Health

Why this matters

Every AWS account eventually hits a problem nobody on the team can solve: a bill that looks wrong, a service that behaves oddly, a migration with no obvious path. What happens next depends on two things this lesson covers. The first is which free resources you know about, because most questions already have an answer in AWS documentation, a Knowledge Center article or a re:Post thread. The second is which support plan the account holds, because that decides whether you can put a technical question to an AWS engineer at all.

For a manager or a salesperson, the support plan is a buying decision with real consequences. A company running a customer-facing system on Basic Support has no one at AWS to call about a technical outage, and finding that out during the outage is the expensive way. For a junior engineer, knowing the difference between AWS Trusted Advisor, the AWS Health Dashboard and AWS Support Center saves hours: one inspects your resources, one reports AWS's own events, and one is where you open a case.

The exam treats this area as a matching exercise. A scenario describes a need, such as community answers, vetted migration patterns, the most comprehensive support, or a way to report an attacker, and you pick the resource built for it.

The lesson

Official AWS websites and what they publish

AWS publishes a large body of free material, and all of it is open to anyone, with or without an account. The main sources are:

• AWS documentation, at docs.aws.amazon.com. Every service has its user guide, developer guide and API reference here. This is the authoritative description of how a service works and what it can do.
• Whitepapers and guides, technical papers written by AWS on architecture, security, cost and specific industries. The AWS Well-Architected Framework (lesson 2) is published this way.
• AWS blogs, including the AWS News Blog for launches and the AWS Security Blog for security guidance and announcements.
• The AWS Architecture Center, which collects reference architectures and diagrams for common designs.
• Pricing pages for each service, plus the AWS Pricing Calculator (lesson 24), which are where current prices live.

The point to carry into the exam is that these are self-service. Reading them costs nothing and needs no support plan.

AWS Support plans

A support plan is the level of help AWS itself gives your account. Every account has one, and the guide names four:

1. Basic Support, included with every account at no additional cost.
2. AWS Business Support+, the first paid tier.
3. AWS Enterprise Support, for business-critical workloads.
4. AWS Unified Operations, the most comprehensive option.

Think of them as a ladder. Each step up adds more direct access to AWS people, faster response when something breaks, and more proactive help, meaning AWS works to prevent problems instead of only reacting to them. Choosing a plan is a trade-off between that help and its cost, judged by how much the business would lose if a workload went down.

Response times and prices change, so do not memorise figures. Read the current comparison on the AWS Support plans page when you need them. Older study material may use plan names the current guide no longer lists. Use the four names above.

AWS Support Center

AWS Support Center is the place in the AWS Management Console where you open, track and reply to support cases. A case is a formal request to AWS, with a history of every message on it. Two kinds matter here:

• Account and billing cases, such as a question about a charge or a problem signing in. Every customer, including those on Basic Support, can open these.
• Technical cases, such as a service failing in a way you cannot explain. These need a paid plan.

Support Center also links to the support plans page for the account. On the exam, if the scenario says "open a case" or "contact AWS Support", the answer is Support Center. If it says "search for an answer", it is not.

Finding whitepapers, blogs and documentation

The skill here is knowing which source fits which need:

• To learn exactly how a feature behaves, or the parameters an API call accepts, go to the service's documentation.
• To understand recommended designs, strategy or the reasoning behind best practice, read a whitepaper.
• To hear about new services and features, or recent security guidance, read the AWS blogs.
• To see how others have built a common pattern, browse the Architecture Center.

All of these are reached from the AWS website and are maintained by AWS, which is what separates them from a third-party tutorial.

AWS Prescriptive Guidance, AWS Knowledge Center and AWS re:Post

These three are the named technical resources, and the exam expects you to tell them apart.

AWS re:Post is AWS's community question-and-answer service, at repost.aws. Anyone can ask a question, and answers come from other customers, AWS Partners and AWS employees. Questions and answers are moderated, and experienced contributors build a visible reputation. It replaced the old AWS discussion forums and needs no paid plan. A scenario that mentions a community, asking peers, or getting help without paying points here.

AWS Knowledge Center is a collection of articles and videos written by AWS that answer the questions customers ask most often, such as why an instance will not start or how to stop an unexpected charge. It now sits within re:Post, but the difference matters: the community writes re:Post answers, while AWS writes Knowledge Center articles. "AWS-authored answers to frequent questions" means Knowledge Center.

AWS Prescriptive Guidance publishes strategies, guides and patterns, written by AWS and its partners, for specific projects such as migrating a database or modernising an application. A pattern is a step-by-step recipe for one task. The guidance is vetted, which separates it from community answers. A scenario about migration or modernisation that wants proven, step-by-step direction points to Prescriptive Guidance (lesson 3 covers migration itself).

Support options: customer service, communities and the four plans

Some help is available to everyone:

• Customer service, around the clock, for account and billing questions.
• Communities, chiefly AWS re:Post.
• Self-service resources: documentation, whitepapers, the Knowledge Center and Prescriptive Guidance.

Basic Support is exactly that set, plus the AWS Health Dashboard and a core set of AWS Trusted Advisor checks. It does not include technical cases with AWS engineers, and it has no named AWS contact. A customer on Basic Support with a technical problem uses the self-service resources and re:Post.

AWS Business Support+ is the first plan that lets you open technical support cases, so you can bring a problem to AWS's support engineers. It suits accounts running production workloads that need a route to AWS when something breaks. Paid plans also unlock the full set of Trusted Advisor checks.

AWS Enterprise Support is designed for business-critical workloads. Its signature feature is a designated technical account manager (TAM): a named AWS contact who learns your environment, gives proactive guidance and helps you plan, rather than waiting for you to open a case.

AWS Unified Operations is the most comprehensive option. It is meant for mission-critical workloads and adds a dedicated team of AWS experts, proactive monitoring of your environment and the fastest incident response AWS offers.

In a scenario, the deciding words are usually these: "no additional cost" or "every customer" means Basic Support. "Technical cases" without the word "critical" points to Business Support+. "Technical account manager" means Enterprise Support at least. "Most comprehensive", "mission-critical" or "dedicated team" means Unified Operations.

AWS Trusted Advisor, and AWS Health through its dashboard and API

These three look similar because all of them produce alerts, but each answers a different question.

AWS Trusted Advisor inspects your own AWS environment and compares it with AWS best practices. Its checks fall into the categories cost optimisation, security, performance, fault tolerance, operational excellence and service quotas, which are the limits on how much of a resource an account may use. On cost, it flags waste, such as an idle load balancer, an EC2 instance doing very little work, or an Elastic IP address that is reserved but not attached to anything. It answers "what in my account should I fix?" Basic Support gets a core set of checks, and paid plans get the full set.

Do not confuse it with AWS Cost Explorer (lesson 24). Cost Explorer analyses what you have spent. Trusted Advisor looks at the resources themselves and tells you which ones are wasteful.

The AWS Health Dashboard reports AWS's own events. It has two views. Service health shows the general status of AWS services, open to anyone. Your account health shows events that affect your resources specifically, such as scheduled maintenance, an instance AWS plans to retire, or a service issue in a Region you use. It answers "is AWS doing something that affects me?" Knowing about scheduled changes early lets you plan, instead of paying for an emergency fix later.

The AWS Health API gives programmatic access to the same account health events, so your own operations tools can retrieve them and act automatically. Health events can also be delivered to Amazon EventBridge (lesson 21) to trigger automated responses.

The usual exam traps sit next to these. Amazon CloudWatch monitors metrics you choose, such as CPU use. AWS CloudTrail records the API calls made in your account. Neither reports AWS service events. Amazon Inspector scans workloads for software vulnerabilities, which is not a cost check.

Reporting abuse to the AWS Trust and Safety team

The AWS Trust and Safety team handles reports that AWS resources are being used for abuse. Examples include port scanning, where a machine probes your network for open doors; sending spam; hosting malware or phishing sites; and denial-of-service attacks. If an AWS IP address is attacking you, you report it to Trust and Safety through the abuse reporting route on the AWS website. You do not need to be an AWS customer to do so.

The direction matters. Trust and Safety deals with abuse coming from AWS resources. It is not a consulting team, and it is not where you go for help with your own architecture. If AWS contacts you because one of your resources is behaving abusively, perhaps because it has been compromised, respond promptly and fix the cause.

What the exam is really asking

Most scenarios here turn on one phrase. "Community" means re:Post. "AWS-written articles" means Knowledge Center. "Migration patterns" means Prescriptive Guidance. "Open a case" means Support Center. "Best-practice checks on my resources" means Trusted Advisor. "AWS events affecting my account" means the Health Dashboard, and "programmatically" adds the Health API. "Abuse from an AWS IP address" means Trust and Safety.