AWS re:Post is a public technical knowledge community available at https://repost.aws/. It provides questions, answers, and technical articles about building and operating on AWS. The broader cloud concept is community-based self-service support: engineers reuse published solutions and exchange knowledge rather than opening a private support case for every question. For certification questions, associate re:Post with community discussions, troubleshooting knowledge, and answers contributed by community members and AWS experts.
A practical workflow begins by searching for the exact error message, service name, and relevant configuration. For example, an engineer investigating an Amazon S3 AccessDenied response might find explanations involving identity policies, bucket policies, explicit denies, or encryption permissions. The engineer should compare the answer with the actual request context and current service documentation, then test the proposed change safely. An accepted answer or an expert contribution is useful evidence, but it does not guarantee that a solution applies to every environment.
If existing material does not resolve the issue, an engineer can post a focused question with the expected behavior, actual behavior, relevant service and Region, and sanitized troubleshooting evidence. Reading public material does not require a paid AWS Support plan; participation requires signing in. Public questions must not contain access keys, passwords, customer records, or confidential logs. Community participants cannot inspect private account resources merely because a question has been posted.
Different technical resources serve different purposes. AWS documentation explains supported service behavior, configuration, and APIs. AWS Knowledge Center provides AWS-authored answers to common questions and troubleshooting problems, with articles accessible through re:Post. AWS Prescriptive Guidance provides implementation guidance, patterns, and strategies for scenarios such as migrations and modernization. Choose community discussion for shared experience, Knowledge Center for common troubleshooting procedures, and Prescriptive Guidance for structured implementation approaches.
Community support has important limits. A public question is not a private AWS Support case, and it does not provide a contractual response time or guarantee that an AWS engineer will investigate. Answers can be incomplete, outdated, or inappropriate for a particular security model. During a production incident, use community knowledge as a supplementary resource rather than waiting for an answer when an appropriate paid support escalation path is available.
Support-plan questions require a separate distinction. Basic Support includes customer service for account and billing questions and access to self-service resources, but it does not include technical support cases with AWS Support engineers. Paid options such as AWS Business Support+, AWS Enterprise Support, and AWS Unified Operations provide different levels of technical support and operational assistance. Select among them according to workload criticality, required response commitments, proactive assistance, and the scope of operational support needed; re:Post does not replace those entitlements.
For example, a general architecture question is suitable for re:Post, while a disputed invoice belongs with account and billing support. A production failure requiring account-specific investigation belongs in a technical support case under an eligible plan. A suspected AWS service disruption should also prompt a check of AWS Health. The key exam skill is matching the assistance channel to the problem, rather than treating every AWS help resource as interchangeable.
AWS Support