What is AWS re:Post Private?
AWS re:Post Private was a managed, private knowledge community built specifically for individual organizations. Teams could ask technical questions, share knowledge, and benefit from curated AWS content without information leaving the organization.
Important notice (as of July 2026): AWS closed re:Post Private to new customers on July 30, 2026. According to the official AWS announcement, existing customers can continue using the service until June 30, 2027, after which it will be fully discontinued. The service is no longer available for new projects; organizations should evaluate alternatives for internal knowledge management early.
The service was based on the public AWS re:Post platform but offered a closed space with access control and the ability to curate public AWS content.
Core Features
- Private Community: Protected space for organization-internal knowledge
- Curated Content: Integration of relevant public AWS re:Post articles
- Access Control: Integration with IAM Identity Center and SSO
- Topic Organization: Structuring by teams, projects, or technologies
- Expert Identification: Internal experts for specific topic areas
Typical Use Cases (for existing customers)
Internal Knowledge Management: Central point of contact for AWS-related questions within the organization. Answers are documented and searchable for all team members.
Cloud Team Onboarding: New employees find curated content, best practices, and organization-specific guides in one place.
Cross-Team Collaboration: Different teams share experiences and solutions for common AWS challenges.
Benefits
- Private, controlled knowledge community (for existing customers until mid-2027)
- Combination of internal and curated public knowledge
- Seamless integration with existing SSO infrastructure
Integration with innFactory
As an AWS Reseller, innFactory supports existing AWS re:Post Private customers in using the service until its discontinuation, as well as planning and executing migrations to alternative knowledge management solutions.
Typical Use Cases
Frequently Asked Questions
Is AWS re:Post Private still available?
No, as of July 30, 2026, AWS re:Post Private is no longer available to new customers. According to AWS, existing customers can continue using the service until June 30, 2027, after which it will be discontinued. New projects should consider alternatives such as internal wikis or other knowledge management tools.
Who can access re:Post Private?
For existing instances, only authorized members of the respective organization. Administrators manage access through IAM Identity Center or email invitations, and content remains private and is not publicly visible.
What does re:Post Private cost?
The service is billed per authorized user per month, regardless of actual usage. Since new sign-ups are no longer possible, pricing is now only relevant for existing customers.
Can I include content from public re:Post?
Yes, for existing instances administrators can curate relevant content from public AWS re:Post and include it in the private community, combining internal knowledge with the broader AWS community.
Note: All product information on this page has been compiled with care, but is provided without guarantee and may be outdated or incomplete. Cloud services evolve rapidly — features, pricing, SLAs, and availability change frequently. Authoritative and up-to-date information can only be found on the official product page of AWS (official documentation). This page does not represent an offer by AWS.