How to Set Up Private AWS Repost: A Step-by-Step Guide

Select Language:

If your organization has an Enterprise Support or Enterprise On-Ramp Support plan with AWS, you can set up your own private version of AWS re:Post. This private version is helpful for teams that want a secure, internal place to ask questions and share knowledge about AWS services.

Here’s how to get your private re:Post up and running:

First, make sure you meet the basic requirements. You’ll need an Enterprise or Enterprise On-Ramp Support plan, and in the same AWS region where you want your private re:Post, you should enable AWS IAM Identity Center. You will also need to create an IAM role that has permissions to create, manage, and resolve support cases.

Once everything is ready, you can create your private re:Post. Access the re:Post Private console and click on “Create private re:Post.” Pick a pricing tier—either Free or Standard—and then fill out some details like the name of your re:Post, a brief description, and if you’d like, a custom subdomain. You can also choose optional settings such as data encryption and support case integration, and add tags if you find it helpful. After you’ve completed these steps, hit “Create this re:Post.”

Next, customize your private re:Post by signing in with your IAM Identity Center credentials. You’ll see a welcome page where you can start setting it up. Here, you can personalize the look with your organization’s title, description, logo, and colors. This is also where you can add tags, topics, and specific words you want to block from discussions. Choose relevant topics that fit your team’s needs to help users find answers quicker.

To bring your team into the private space, you should invite users. As the administrator, you can send email invitations to your team members. They will receive instructions on how to log in and register to join your private re:Post.

The whole process usually takes about 30 minutes. After it’s set up, you can access your private re:Post using either the AWS-generated subdomain or your custom one, if you chose to create one. This way, your team has a dedicated, secure place for AWS questions and collaboration.

For more detailed steps and information, you can refer to the official documentation provided by AWS.