FAQs

AWS Builder Center (builder.aws.com) is the go-to site for builders to connect with the AWS community. It provides a seamless experience for discovering community-published articles, networking with like-minded professionals, and submitting product improvement ideas through the Wishlist. You can browse articles and search for builders without signing in. However, signing in with your Builder ID unlocks even more features!

After signing in, you can follow other builders and receive notifications, engage with content by liking, commenting, or reporting, and access Wishlist to view, upvote, and comment on product suggestions.

AWS Builder Center supports 16 languages: Arabic, Bahasa Indonesian, Chinese (simplified and traditional), English, French, German, Italian, Japanese, Korean, Portuguese, Russian, Spanish, Thai, Turkish, and Vietnamese. This setting affects both the interface and machine translation of community content. You can use the Translate button on content created by other builders to view it in your preferred language.

Go to the Settings page from the top navigation to select one of the supported languages to view AWS Builder Center's interface in your preferred language. The language you select will also be used when using Builder Center's on-demand machine translation feature for any community-created content. Content available for on-demand translation will appear with a Translate button. So, whether you're browsing through articles, reading wishes, or engaging with comments, you can simply click the Translate button to view the content in your preferred language. You must be signed into Builder Center to use this feature.

AWS Builder Center is compatible with the latest 3 versions of Microsoft Edge, Mozilla Firefox, Google Chrome, and Apple Safari browsers.

AWS Builder ID is your personal credential for learning, connecting, and experimenting with AWS outside of the AWS Management Console. It's separate from your AWS account or AWS Partner Network credential. If you already use Builder ID for AWS Skill Builder, or AWS re:Post, you can use the same Builder ID for AWS Builder Center. This single credential allows you to create a Builder Center profile, publish articles, create wishes, engage with content across multiple AWS communities, and more.

To check, visit the AWS Builder Center and click Sign In in the top navigation. Select Already have a Builder ID? Sign in and enter your email address. If an account exists, you'll be prompted for a password. If not, you'll be guided through the creation process. If you've previously used AWS Skill Builder, or AWS re:Post, you likely already have a Builder ID.

For new Builder ID creation:

1. On the AWS Builder Center top navigation, click Sign in.
2. On the Create AWS Builder ID page, enter Your email address. We recommend that you use a personal email.
3. Choose Next.
4. Enter Your name, and then choose Next.
5. On the Email verification page, enter the verification code that we sent to your email address. Choose Verify. Depending on your email provider, it might take a few minutes for you to receive the email. Check your spam and junk folders for the code. If you don't see the email from AWS after five minutes, choose Resend code.
6. After we verify your email, on the Choose a password page, enter a Password and Confirm password.
7. If a Captcha appears as additional security, enter the characters that you see.
8. Choose Create AWS Builder ID.

Once you have a Builder ID, signing in to AWS Builder Center is straightforward:

1. On the AWS Builder Center top navigation, click Sign in.
2. Enter your Builder ID email and password.
3. If required, complete any additional verification steps.
4. For first-time builders, you'll be prompted to choose an alias to complete your Builder Center profile.

Remember, your Builder ID is your key to accessing various AWS community programs. It allows you to create a Builder Center profile, publish articles, submit wishes, and engage with content across different AWS learning and community services. If you encounter any issues during sign-up or sign-in, AWS Builder Support is available to assist you.

No. Your AWS Builder ID is separate from any AWS account or AWS Management Console.

AWS Builder ID passwords must be between 8 and 64 characters long and include at least one character from each of these categories: lowercase letters, uppercase letters, numbers, and special characters (~!@#$%^&*_-+=`|(){}[]:;"'<>,.?/). Passwords are case-sensitive, and you cannot reuse your last three passwords.

To change your password:

1. Sign in to your AWS Builder ID credential  page.
2. Choose Security.
3. On the Security page, choose Change password. This takes you to a new page.
4. On the Re-enter your password page, under Password, enter your current password. Then choose Sign in.
5. On the Change your password page, under New password, enter the new password that you want to use. Then under Confirm password, re-enter the new password that you want to use.
6. Choose Change password. You're redirected to your AWS Builder ID profile.

To change your Builder ID email:

1. Sign in to your AWS Builder ID credential  page.
2. Choose My details.
3. On the My details page, choose the Edit button next to Contact information.
4. On the Edit contact information page, change your Email address.
5. Choose Verify email. A dialog box appears.
6. In the Verify email dialog box, after you receive the code in your email, enter the code in Verification code. Choose Verify.

If you have multiple Builder IDs, we recommend using the one associated with your personal email for AWS Builder Center and maintaining that as your primary ID.

To delete your Builder ID:

1. Sign in to your AWS Builder ID credential  page.
2. Choose My AWS Builder ID data.
3. On the My AWS Builder ID data page, under Deleting AWS Builder ID, choose Delete AWS Builder ID.
4. Select the check box beside each disclaimer to confirm that you are ready to proceed.

Important: Deleting your Builder ID permanently removes your access to all Builder ID-enabled experiences, including AWS Builder Center. This action cannot be undone.

Your AWS Builder Center alias is a unique identifier for your profile on builder.aws.com and is what makes your profile URL unique (/community/@youralias).

You are asked to set your alias the first time signing into Builder Center. If you created an alias prior to Builder Center, this will also be your Builder Center alias. Your Builder Center alias:

• Must be between 3 and 19 characters in length
• Must begin with a letter and can include lowercase letters (a-z) and numbers (0-9)
• Cannot include spaces or non-alphanumeric characters (~!@#$%^&*_-+=`|\(){}[]:;"'<>,.?/)
• Cannot violate the AWS Builder Terms

You are unable to change your alias.

After you sign in to AWS Builder Center, click your name in top navigation. Then click Manage Profile. You'll see your alias on this page.

1. Sign into AWS Builder Center by clicking the Sign in button on the top navigation. Follow the steps to sign in with your AWS Builder ID.
2. Click [Your name] in the top navigation to reveal a dropdown and select Manage Profile to open your profile.
3. Click the pencil icon in the desired section to edit.

In your Builder Center profile, your public information includes display name, alias, and optionally a headline, interests, about, social media links, and display location. Private information that is only visible to you includes first name, last name, email, phone and location.

To edit your profile, Sign into AWS Builder Center by clicking the Sign in button on the top navigation. Then click your name in the upper right corner to view the profile dropdown. Select Manage Profile. On your Builder Center profile, you can click the pencil icon in any area to update or edit your information.

There are two ways to share your profile with others. You can share your personalized profile URL (example: /community/@youralias) or show your QR code card. To find your QR code card, go to your profile page using your personalized profile URL. Then click the QR code button to view your QR code card.

To delete your AWS Builder ID:

1. Sign in to your AWS Builder ID profile at https://profile.aws.amazon.com .
2. Choose My AWS Builder ID data.
3. On the My AWS Builder ID data page, Deleting AWS Builder ID, choose Delete AWS Builder ID.
4. Select the check box beside each disclaimer to confirm that you are ready to proceed.

Your data in AWS Builder Center is governed by the AWS Builder Terms.

You can request the data associated with your Builder ID:

1. Sign in to your AWS Builder ID credential  page.
2. Choose Privacy & data.
3. On the Privacy & data page, choose the Request your data button.
4. A confirmation message appears at the top of the page that we received your request and will complete it within 30 days.
5. When you receive an email from us that the request has been processed, navigate back to the Privacy & data page of your AWS Builder ID profile. Choose the newly available button Download ZIP archive with your data.

Important: While your data request is pending, you will not be able to delete your AWS Builder ID.

Your articles, reactions and comments on articles, and badges are visible to anyone. Your wishes and comments on wishes are visible to anyone signed into Builder Center.

Builder Spaces is a dynamic, virtual place that connects you and AWS builders around shared interests, experiences, and goals. Spaces help you create, manage, and join meaningful AWS communities online. Whether you're digitizing an in-person group, organizing events, or building a new virtual community, Spaces provide the tools you need. Choose the community style that works for you. Inside a public, private or invite-only space, you can share ideas through posts, engage in discussions, and connect with like-minded individuals.

There are three space types: public, private, and invite-only.

• Public spaces are the most open and accessible type of Builder Space. Anyone can view and join public spaces. The space's content, member list, and discussions are visible to anyone who is signed in, even before joining. Public spaces can be changed to private or invite-only spaces.
• Private spaces require membership approval from the owner or admin. While anyone can discover and request to join private spaces, only members can view the space's content and member list. Private spaces can be changed to an invite-only space.
• Invite-only spaces represent the most exclusive and restricted space type. These spaces are completely hidden from general discovery and can only be accessed through direct invitations from admins or owners. Once set as invite-only, this designation is permanent and cannot be changed to public or private.

All spaces will be accessible to the Builder Moderation team.

Any space that is marked as verified will be managed by an AWS team and appear with a verified badge next to the space name.

There are 3 role types: Member, Admin, and Owner.

• Members are builders who have joined a public, private, or invite-only space. They have basic participation rights, must follow space rules, and can report inappropriate content but lack moderation powers. Members can report violations of the AWS Builder Terms to the AWS Builder Center moderators for review.
• Admins are members who receive additional space privileges from the space owner, including enforcing space rules, managing membership, and editing space details. Admins help to manage space membership.
• Owners are the original creators of a space and maintain sole, non-transferable ownership. They are responsible for managing all aspects of the space, including enforcing rules, maintaining quality, managing admins, and overseeing membership and invites to ensure the space fulfills its purpose. Owners are the only role allowed to archive the space.

There are three ways to join a space depending on the space type.

• Option 1: Receive an invitation
  For all space types (public, private, and invite-only), you may receive a membership invite to join a space. The invitation will appear on the Builder spaces landing page under the Invites and requests tab.
• Option 2: Click to join
  Public spaces: Choose Join from the space's detail page or from the Builder Spaces landing page and automatically become a member of the space.
• Option 3: Request to join
  • Private spaces: Choose Join from the space's detail page or from the Builder Spaces landing page to send a request to join the space. The admins and owner for the space will approve or decline your request. You will receive a notification for all approved requests.
  • Invite-only spaces: You cannot request to join invite-only spaces.

When signed in, you can create a space two ways:

• Option 1: From the top navigation
  1. Choose + on the Builder Center top navigation and choose Create a space.
  2. Populate the required details for your new space.
  3. Choose Preview to review what your space will look like when live.
  4. Then choose Create.
• Option 2: From the Builder Spaces landing page
  1. Go to the Builder spaces landing page (Connect > Builder spaces)
  2. Choose Create a space.
  3. Populate the required details for your new space.
  4. Choose Preview to review what your space will look like when live.
  5. Then choose Create.

All spaces created are reviewed by our AI moderation tooling and are subject to the AWS Builder Terms. Violations of these terms will prohibit creation.

Space rules are created and enforced by the Space's owners and admins. Rules are created for each space to align with the space's purpose. Builder Center moderators are not responsible for enforcing space rules.

As an admin or owner, there are different ways to manage a space:

Edit your space

Find the space you own and want to edit:

• Option 1: from the Builder spaces landing page
  1. Choose the three stacked dots next to the space and select Edit.
  2. Make desired changes.
  3. Choose Save.
• Option 2: from the space detail page
  1. Choose the title to open the space detail page.
  2. Choose the three stacked dots and select Edit.
  3. Make desired changes.
  4. Choose Save.

Grant / remove admin access (Owner only)

1. Go to the space detail page and select the Member tab.
2. Choose the three stacked dots next to the member and select Edit.
3. Make desired changes.
4. Choose Save.

Archive your space (Owner only)

Find the space you own and want to archive (Connect > Builder spaces > Your spaces tab).

• Option 1: from the Builder spaces landing page
  1. Choose the title to open the space detail page.
  2. Choose the three stacked dots next to the space you own and select Archive.
• Option 2: from the space detail page
  1. Choose the title to open the space detail page.
  2. Choose the three stacked dots and select Archive.

Builders can create various types of content in AWS Builder Center to share their knowledge and experiences with the AWS community. Using articles, builders can create a wide range of topics related to AWS products and services, best practices, tutorials, and real-world implementations. These articles can include text, code snippets, diagrams, and images to effectively communicate ideas and solutions. In addition to articles, builders can also contribute to discussions by commenting on existing content and providing valuable insights to other community members. AWS Builder Center also encourages builders to share their innovative ideas and feature requests through the Wishlist feature. Wishlist allows builders to propose new features to existing AWS products or services, to build the future of the AWS cloud together.

AWS Builder Center maintains a secure and respectful environment for all builders. When creating content, builders must adhere to the AWS Builder Terms. Content should also contain thoughtful and accurate information, respect for others, and protection of confidential information. Any attempt to manipulate features or content, including posting false or misleading information, is prohibited.

To ensure content quality, we may employ automated moderation to check for broken links, profanity, and appropriate title and description length. For accessibility, use clear headings with a logical structure (H1 → H2 → H3), provide alternative text for images, and ensure sufficient color contrast (minimum 4.5:1 ratio) for text. Write in plain language and break content into digestible chunks with short paragraphs and bullet points. For more detailed accessibility guidelines, refer to the WCAG 2.2 standards .

Low-quality content includes content that is repetitive, off-topic, and/or not adding any value to the builder community. This kind of content buries genuinely valuable content, making it harder for other builders to find content worth their time.

Per the Builder Terms, AWS has the right (but not the obligation) to reject, edit, or delete content in Builder Offerings at any time and for any reason without notice, including content that is poor quality or irrelevant to Builder Offerings.

In practice:

• Individual low-quality content, whether or not intended for badges or rewards, will be suspended/removed.
• A pattern of repeated low-quality content may result in suspension of a builder's profile, which restricts access to the rewards the builder might have accrued.

Content is suspended when it violates the AWS Builder Terms. A suspended article is removed from public view, and anyone who tries to open it directly will see a "page not found" message.

If the suspended article is part of a series, it's automatically removed from the public series view and the series reorders the remaining articles. For example, in a four-article series where article 3 is suspended, builders will see only articles 1, 2, and 4.

If you believe your content was suspended by mistake, you can appeal the decision through AWS Builder Support.

Articles are builder-generated content pieces that provide information, insights, tutorials, or discussions about various AWS products and services, features, and best practices. These articles serve several purposes:

• Knowledge sharing: Builders can share their experiences, tips, and tricks related to AWS products and services.
• Problem-solving: Articles often address common issues or challenges faced by builders and provide solutions.
• Tutorials: Step-by-step guides on how to implement specific AWS features or services.
• Best practices: Sharing optimal ways to use AWS resources and services.
• Service updates: Discussing new AWS features or services and their implications.
• Case studies: Sharing real-world examples of AWS implementations and their outcomes.
• Community engagement: Encouraging discussion and collaboration among builders.

The lifecycle of your article in Builder Center includes several management options, from creation through deletion. Here's how to manage your content at each stage:

To create an article:

1. On the AWS Builder Center top navigation, click + and select Create article
2. Populate all required fields
3. Click Preview to review how your article will look when published
4. Click Publish
5. Wait for the automated content moderation scan to complete

To edit an article:

1. Go to your Manage Content page
2. Select the Published tab
3. Click the three dots next to your article
4. Select Edit to make changes and re-publish
5. Wait for moderation scan to complete

To archive an article:

1. Go to your Manage Content page
2. Select the Published tab
3. Click the three dots next to your article
4. Select Archive Note: Archived articles are only visible to you and will remain in your archived tab until you choose to re-publish.

To delete an article:

1. Go to your Manage Content page
2. Select the Published tab
3. Click the three dots next to your article and select Unpublish
4. Go to the Drafts tab
5. Find your article and click the three dots
6. Select Delete Important: Article deletion is permanent and cannot be undone. Consider archiving instead if you might want to access the content later.

Your articles remain accessible through their original URLs even after editing, helping maintain stable links for shared content.

Builder Center allows you to create articles, posts, wishes, and comments in your preferred language. Since you can only publish content in one language, Builder Center offers a dynamic, on-demand localization feature to support builders with a different preferred language.

When builders with a different preferred language want to view your content, they can click a Translate button next to the content to automatically translate it using machine translation. This process is seamless and doesn't require you to create multiple versions of your content. The original language remains intact, preserving your intended meaning and style. Translations are generated in real-time, ensuring that even if you update your content, all language versions stay current. This feature supports a wide range of languages, making your content accessible to a global audience.

Article series work the same way. If a builder's preferred language differs from the series creator's, a Translate button appears next to the series title so they can translate it.

However, it's important to note that machine translations may not always capture nuances or industry-specific terminology perfectly.

Tags are keywords or labels that help organize and discover content in AWS Builder Center. You can add up to five tags to content you create, which helps other builders find your contributions more easily. Each tag has its own dedicated page showing all associated content. While tagging is optional, we recommend using specific, relevant tags that align with your content to increase its discoverability. Currently, all tags are pre-defined, and you cannot create new ones. To explore available tags, visit the Topics page.

View counts show how many times other builders have viewed your article. The count appears on your article page and in your profile's article list.

View counts are private to you as the author. Readers and other community members cannot see your view count.

A view is counted when someone clicks on and views your article, whether or not they're signed in. Your own visits don't count. If the same person views your article multiple times within a 24-hour window, it counts as one view. After 24 hours, a return visit counts again.

Look for the view count icon on your articles. You'll see it on the article detail page and on your profile's article list.

View counts include data starting from January 6, 2026. Views before that date are not included.

View counts are currently a private metric visible only to the author. They're designed as a personal tool to help you understand your content's reach and decide what to write next.

An article series is a way to group related articles into an ordered, sequential collection. Series help builders organize multi-part content such as step-by-step tutorials, learning paths, or deep-dive topics so readers can follow articles in the intended order. When an article belongs to a series, readers see a series component on the article page showing the series title, the position of the current article, and navigation to the other articles in the series.

Like your articles, a series needs to follow the AWS Builder Terms. Here are a few rules and best practices that are specific to series:

• Series titles must be between 1 and 255 characters and unique within your portfolio. You can't have two series with the same title, so if a title is too long or duplicates an existing series, you'll be prompted to choose a different one.
• An article can belong to only one series at a time. To move an article to a different series, remove it from its current series first.
• There's no limit on the number of series you can create, or on the number of articles you can add to a single series.
• Best practice: order your articles in the sequence you want builders to read them. A series is meant to guide builders through related content in a deliberate order, so arrange it the way it reads best.
• Best practice: give your series a clear, descriptive title so builders can tell what it covers at a glance.

Like articles, a series can be managed at every stage, from creation through deletion. Here's how to manage a series at each stage:

To create a new series:

1. Start creating a new article or open an already published or drafted article in edit mode from your Manage Content page
2. Go to the bottom of the article and expand the More Options section
3. Click Add New Series
4. In the Create series window, enter your series title. Series titles must be between 1 and 255 characters, cannot be the same title as another series.
5. Click Create series. This will create the series, but will not publish it.
6. To publish your series, you need to publish your article. If you are creating a series with an existing article, you will need to republish your article. The article where you created the series will be the first article in the series until you add and reorder the articles in your series.

Note: If you are not ready to publish your article yet, or you want to reorder and add more articles to the series, go to your Manage Content page > Published tab > filter by Series and click on the desired series to open the Edit Series page.

To add an article to an existing series (two options):

Option 1: Adding a brand new article

1. Begin creating your article.
2. Go to the bottom of the article and expand the More Options section.
3. Click the Select Existing Series dropdown and select the series you want.
4. Click Save to apply your updates or Cancel to discard them. If all or any of your articles are in draft state, they will not publicly appear in the series. When you publish draft articles to a series, the article series will update to show the article at the same time the article is published.

Note: To pick the position of your article in the series, you need to go to your Manage Content page > Published tab > filter by Series and click on the desired series to open the Edit Series page.

Option 2: Adding a published or drafted article

1. Go to your Manage Content page > Published tab > filter by Series and click on the series to open the Edit series page.
2. Click Add article.
3. Click the Choose your article dropdown to select one of your published or drafted articles.
4. To reorder your articles, click and drag the icon to the left of your desired article until it has moved higher or lower in your article series list.
5. Click Save. Your series should be automatically updated to show your newly added article and any order changes made.
6. Publish or re-publish your article for it to appear in the series publicly. If you save it as a draft, the article is added once you publish.

To edit a series:

1. Go to your Manage Content page > Published tab > filter by Series and click on the series to open the Edit series page.
2. Reorder an article: you can reorder articles by dragging and dropping each article to the desired position; the series list will renumber automatically (1, 2, 3, and so on).
3. Remove an article: Click the X next to the article you want to remove from the series. Removing an article from a series DOES NOT delete the individual article from Builder Center.
4. Add an article: Click Add article and select one of your published or draft articles that aren't already in a series. Reorder if necessary.
5. Click Save to apply your updates or Cancel to discard them.

To delete a series:

1. Go to your Manage Content page > Published tab > filter by Series and click on the series to open the Edit series page.
2. Remove all articles in your series by clicking the X next to each article. When you remove the last article, you will be asked to confirm if you want to remove the article because it will mean that you delete the series.
3. Click Remove article. Removing an article from a series DOES NOT delete the individual article.

Note: You cannot recover a deleted series. If you create a new series with the same title name as a deleted series, you will receive a new URL.

When an article is a part of a series, an article series information component will appear on the article page. The component shows:

• Series title
• Number of articles in the series
• Indicator marker on the current article being viewed from the series
• An initial list of up to 3 articles, with an expander button to view the full list
• Clickable navigation links to jump to any article in the series

This component is visible to everyone, including builders not signed into Builder Center. Authors can only modify the series (editing, reordering, and deleting) when signed into Builder Center.

No. Only published articles appear in the series component for builders. Any draft articles in a series remain hidden from the public until they are published by the author.

Polls are a lightweight way for builders to ask the Builder Center community a question and collect insights. A builder creates a question with two to five answer options, sets a deadline, adds tags, and publishes.

Other builders can vote directly from the Home feed or from the poll's dedicated page. Results show a vote count and a percentage for each option. Polls also support comments through the same commenting system as articles, so builders can discuss the topic alongside voting.

From the "+" (Create) menu, select "Poll" to open the Create a poll page. A poll requires:

• Question: 1 to 255 characters, with a live character counter.
• Answers: a minimum of 2 and a maximum of 5. Each answer is 1 to 255 characters and must be unique within the poll. Use the drag handle to reorder answers, or the remove (✕) control to delete one.
• Tags: a minimum of 1 and a maximum of 5, drawn from the existing article tag taxonomy.
• Timeframe: required. Choose 24 hours, 3 days, 1 week, 2 weeks (the default), or Custom. A custom deadline must be at least 4 hours and no more than 14 days from the publish time, and is specified in UTC.

Select "Preview" for a full-page, non-interactive rendering of exactly how the poll will appear, then "Edit" to return to the form.

On "Publish," the content is screened automatically for adherence to the Builder Terms. If an issue is found, "Fix error" returns you to the creation page with all input preserved, so you can resolve it before you publish. Once the poll publishes, the creator lands on the poll's dedicated page.

No. A poll cannot be edited once it is published. To change a question, an answer, or a deadline, delete the poll from Manage content and create a new one. Deletion is permanent: a confirmation modal precedes it, all votes are removed, the results are lost, and there is no undo.

Votes work the same way. Once you select "Submit answer," your vote is recorded and cannot be changed. The results stay on display with your selection highlighted.

While a poll is active, results are visible only to signed-in builders who have voted. Once the deadline passes, results are visible to everyone.

Browsing a poll's question, answers, and comments never requires signing in, but voting and commenting require a Builder ID. If you select an answer while signed out, a sign-in modal appears. After you sign in, you are returned to submit your vote and see the results.

Yes. Vote choices are not attributed to any builder, either publicly or to the poll creator. Creators see aggregate vote counts and percentages only.

Your own selection is highlighted for you with a check-circle icon, so you can see what you chose. Polls also appear in a builder's Profile → Activity stream with results bars, and individual votes are not disclosed there either.

Polls close automatically at their deadline in UTC. If you are viewing a poll when its deadline passes, it changes live with no page refresh: an "Ended" badge appears, the final results are revealed, and the answers are no longer selectable.

In-app notifications for poll activity are delivered on Builder Center by default. Email delivery depends on your notification settings. Under Settings → Notifications, the Content and Network categories each have an email toggle and a frequency of Daily or Weekly. If the toggle for the relevant category is off, no email is sent for those events and you see the notification in-app only. Polls fold into these existing categories, so there is no poll-specific settings row.

Because email is bundled, most poll emails do not arrive immediately. They are grouped into the next digest at the frequency you selected:

• Your poll ended: the poll creator is notified in-app, and by email in the Content digest.
• Someone commented on your poll: the poll creator is notified in-app, and by email in the Content digest.
• Someone replied to your comment on your poll: the poll creator is notified in-app, and by email in the Content digest.
• A poll you voted in ended: the voter is notified in-app, and by email in the Network digest.
• Someone you follow created a poll: the follower is notified in-app, and by email in the Network digest.
• Your poll was suspended or unsuspended: the poll creator is notified in-app, and by a standalone transactional email that is not bundled into a digest.

Wishlist is a dedicated feedback forum within Builder Center for the AWS community to influence product and service roadmaps. Wishlist allows builders to submit ideas, suggestions, or challenges they face while using AWS products and services. In Wishlist, builders can comment and upvote on wishes, elevating the most discussed and pressing wishes to the AWS product teams. Wishlist also facilitates collaboration by allowing builders to comment on wishes, contributing their insights, proposing workarounds, or recommending alternative approaches.

You must be signed into AWS Builder Center to view Wishlist, create, edit, and submit wishes.

Anyone signed into AWS Builder Center can search wishes or browse by Category, AWS Service, or Status on the Wishlist page. Your wish will appear on relevant tag pages. To track your own wishes, go to Your Wishlist tab to see your wishes and their statuses.

No. Instead, provide a comment on the similar wish outlining your idea so the community and the original author can see your comment. This gives fellow builders a chance to validate and up-vote your idea, and a chance for the author to iterate on their wish.

When creating wishes in AWS Builder Center, follow these guidelines:

1. Adhere to the AWS Builder Terms.
2. Your wish will undergo automated content moderation to check for:
   • Broken or malicious links
   • Profanity
   • Appropriate title and description length
3. Be authentic, respectful, and helpful to the community.
4. Before submitting a new wish:
   • Browse existing wishes to avoid duplication.
   • If you find a similar wish, consider commenting on it instead of creating a new one.
5. When writing your wish:
   • Clearly explain how your idea adds value or improves builder experience.
   • Provide details on how it reduces complexity or enhances AWS products and services.
   • Be specific about the problem you're addressing and the proposed solution.
6. After submitting:
   • Monitor responses for potential solutions or workarounds.
   • Engage with comments to clarify or expand on your idea.
   • Avoid making significant changes to your wish after receiving votes, as this may affect its integrity and evaluation.

Creating a wish:

1. Click + on the Builder Center top navigation and select Create wish.
2. Fill in all required fields.
3. Click Preview to review your wish.
4. Click Submit. Your wish will undergo automated content moderation.

Editing a wish:

1. Go to your Manage Content page.
2. Click the three dots next to the wish you want to change.
3. Select Edit and make your changes.
4. Re-publish the wish.

Deleting a wish:

1. Go to your Manage Content page.
2. Select Wishes from the Published tab.
3. Click the three dots next to the wish and select Delete.

Note: Deleted wishes cannot be recovered.

Important considerations for editing:

• The URL of your wish remains constant even after editing.
• If you make significant changes after receiving votes:
  1. It will require additional review time from the AWS product team.
  2. They'll evaluate if the changes alter the original intent of the wish.
• To maintain voting integrity, keep edits minimal once voting has begun.
• If you have a substantially different idea, create a new wish instead of altering an existing one.

You can only publish wishes in one language, although they can be translated on-demand by builders with different language preferences.

After creating a wish:

1. Your wish undergoes automated moderation checks for: broken or malicious links, profanity, and appropriate title and description length.
2. If it passes moderation, your wish is published and becomes visible to other signed-in builders.
3. If there are issues, you'll receive feedback to make necessary changes before publication.

Sharing and viewing wishes:

You can share the URL of your published wish. Anyone with the URL must be signed into Builder Center to view the wish.

Engaging with wishes:

Signed-in builders can vote on wishes to show their support. Builders can comment on wishes to provide feedback, suggest improvements, or offer alternative solutions. Comments also undergo a content review process to ensure they meet community guidelines. Authors can respond to comments, fostering discussion and collaboration.

Tracking wish progress:

Wishes may be assigned different status labels (e.g., Not Started, Ready, Live) as they progress through consideration and potential implementation. You can monitor your wish's status and community engagement through the Wishlist interface.

If you experience any issues with publishing or engaging with wishes, please contact AWS Builder Support for assistance.

You can delete your wish at any time. After signing into AWS Builder Center, go to your Manage Content page to view your articles and wishes. Click Delete next to the published content you wish to delete.

AWS Workshops provide free, step-by-step instructions crafted by AWS experts that explain how to deploy and connect AWS services effectively. Workshops are designed for builders of all skill levels to gain practical experience and develop solutions tailored to their specific business needs using AWS services.

Available workshops cover a wide range of AWS services, features, and use cases, allowing builders to follow guided tutorials within their own AWS accounts or complete in a time-limited AWS sandbox environment.

Accessing and reading workshops are always free. Completing the hands-on exercises is also free when you use a time-limited AWS sandbox environment requested directly from a workshop. If you choose to complete the exercises in your personal AWS account, it can be free when you stay within the AWS Free Tier limits and clean up resources promptly, but standard charges will apply for any resources you deploy that fall outside the Free Tier or that you leave running.

Workshops are classified into four different complexity levels:

• 100 - Beginner: No AWS experience needed
• 200 - Intermediate: Some AWS knowledge helpful
• 300 - Advanced: Solid AWS foundation required
• 400 - Expert: Deep AWS expertise expected

Go to the AWS Workshops page to explore the full workshops catalog. On the page, you can: 1) search by text; 2) sort by newest, oldest, or alphabetically; or 3) filter by Complexity Level, Language, Category, AWS Service and Features, Duration, and Access type.

You can also use the Builder Center search bar in the top navigation to find workshops. Results that match offerings (title, descriptions, AWS services and features) from the workshops catalog will appear in the search results under the Workshops tab.

If you don't find workshops based on your search or filtering, adjust some filters to broaden results, check your spelling, or try different search terms. If you are still unable to find a workshop that meets your needs, you can create a wish in the AWS Wishlist for a new workshop.

An AWS sandbox environment is a free, pre-provisioned, time-limited AWS account for you to safely complete hands-on workshop exercises, write code, and experiment without the need of a personal AWS account, credit card, or concerns about unexpected charges. Each environment is time-boxed to 8 hours, starting from when the environment is prepared and you are notified that it is ready, after which it is automatically de-provisioned.

To start an AWS Workshop in a sandbox environment:

1. Go to the AWS Workshops page.
2. Find your desired workshop that offers a sandbox environment.
3. Click Request free sandbox environment button above the Workshop title. Note: You will be prompted to sign into Builder Center if you have not done so before this step.
4. A modal will display key details, including the approximate 15-minute preparation time, the 8-hour active session window, and the weekly limit of one sandbox environment per builder. Click Request to confirm.
5. Once your request is submitted, you will receive an email and an in-app notification that AWS Workshops is processing your request. Most requests are ready in 15 minutes. More complex environments may take up to an hour.
6. When your sandbox environment is ready, you will receive a second email with a link to launch your sandbox and a flash bar in Builder Center.
7. Click Go to environment to begin the workshop.

You have 8 hours to complete the workshop in your sandbox environment from the moment you receive the email that your sandbox is ready. On the AWS Workshops page under the Your Workshops tab, you can find all past and active Workshops with sandbox environments you requested.

Yes. To ensure fair access for all builders, the following limits apply:

• One active sandbox environment at a time: You cannot request a new sandbox environment while you have one already active. You'll need to wait until your current 8-hour session ends before requesting another.
• One sandbox environment per week limit: You can request 1 sandbox environment per week. The weekly limit resets every Sunday.

Each free sandbox environment is active for 8 hours. The 8-hour period starts at the moment you receive the email and notification stating your sandbox environment is ready. After 8 hours, the provisioned AWS account powering the sandbox environment along with any resources in it are automatically de-provisioned.

We recommend completing the workshop or saving any code, configurations, or outputs to a location outside the sandbox account (such as your local machine or a personal AWS account) before your session expires.

At launch, the free AWS sandbox environment capability is enabled for a subset of workshops on Builder Center. We will scale this capability across additional workshops and post updates in Builder Center as new sandbox environments are enabled. To help us prioritize which workshops to enable next, builders can create a wish in the AWS Wishlist that other builders can upvote. In the meantime, if a workshop you're interested in doesn't currently offer a sandbox environment, you can still complete it using your personal AWS account.

On some occasions, a sandbox environment may fail to provision or complete preparation. If this happens, your weekly quota remains intact and is not consumed by the failed request. You can submit a new request for the same workshop or choose an alternate workshop, as your quota is preserved. If you continue to experience provisioning failures, please try again after some time or contact Builder Support.

Builder Center enables you to connect with other builders. When you follow someone, you'll receive notifications about their recently published articles. There is no restriction on the number of builders you can follow, allowing you to build a network that matches your interests and learning needs.

AWS Builder Center maintains different levels of visibility for your activities. Your published articles, article comments, and article reactions are visible to everyone visiting Builder Center. Your network connections, including who you follow and who follows you, are also public. However, some activities require builders to be signed in to view them. These include your published wishes, wish votes, wish comments, and reactions to wishes. This tiered visibility helps balance open knowledge sharing with community engagement.

AWS Builder Center provides a comprehensive notification system to keep you informed about community activity. You can decide if you receive updates about your content (including likes, comments, and status changes), network activities (such as new followers and their publications), and important Builder Center information. These notifications are delivered through both email and in-app channels. You can customize your notification preferences by signing into Builder Center and visiting the Settings page, where you can adjust both the types and frequency of notifications you receive.

AWS Builder Center offers multiple ways to discover and share content. To find articles, you can use the search function with keywords related to your interests, explore specific tags like compute or storage, or sort by date using the Latest feed. You can also visit builders' profiles to see all their contributions. When you publish an article, others can find it through these same methods - searching keywords in your title or content, clicking on your used tags, or visiting your profile page. You can also share direct links to your articles on social media or with colleagues, making it easy to spread knowledge within the community.

AWS Builder Support serves as your primary contact for general inquiries about AWS Builder Center, bug reports, and troubleshooting assistance with your builder experience. Before contacting support, we recommend reviewing our FAQs as many common questions are already addressed above.

The reporting process is straightforward - locate the three dots next to the content (article, article series, wish, post, comment, or series) or on the profile you wish to report, select Report, and complete the form with details about the violation. You must be signed in to report content that violates the AWS Builder Terms.

The AWS Builder Support team will review all submitted reports and take appropriate action if necessary. This process helps maintain the quality and safety of our community.

The Builder Center moderation team is committed to creating a safe community where Builders can connect, learn, and grow. Content suspension occurs when there is a violation of the AWS Builder Terms. If your profile is suspended, you will no longer be able to sign in to Builder Center or create content, though you can still view publicly available content and visit the site as a visitor. If you believe your content or profile was suspended by mistake, you can appeal the decision through AWS Builder Support. In your appeal, include specific details about your suspended content and explain why you believe the suspension was made in error. Our team will review your appeal and respond accordingly.

The AWS Builder Center moderation team will review any reported content and act if necessary.

AWS Capabilities by Region is a planning tool that provides detailed visibility into AWS services, features, API and CloudFormation resources availability across AWS Regions. It helps you make confident decisions about your global deployments by showing what capabilities are available where, with forward-looking roadmap information and specific timelines. You can also sign-up to availability notifications to receive automatic updates via in-app notifications and weekly email digests when services or features become available in the AWS Regions you care about, including AWS Regions that launch in the future.

You can analyze all applicable AWS Regions simultaneously. The tool supports side-by-side comparison of multiple regions, with us-east-1 selected by default. You can toggle between regions to identify common capabilities or spotlight critical differences that affect your deployments.

After selecting your target Regions, use the filters below the search box to control your view. On the Services and features tab there are three:

1. Availability. A multiselect of availability statuses. Select Available to see only what is live, or Unavailable to see everything that is not, which expands to the three specific states underneath it: Not Expanding, Planned, and Planning. Leaving the filter empty shows every status.
2. Planning timeframe. Narrows the comparison by when a capability is planned to arrive. The default is Any timeframe, and the other options are After 2026 Q3, After 2026 Q4, After 2027 Q1, and so on. Use it to separate capabilities arriving soon from those further out.
3. Region comparison. Controls how the Regions you have selected are compared. Show all capabilities displays all services and features. Show only common across selected regions shows only services and features with the same availability status in every selected Region. Show only differences between selected regions shows only services and features whose availability status differs across selected Regions, which is the fastest way to find the gaps between two Regions you are choosing between.

The API operations and CloudFormation resources tabs have Availability and Region comparison, without Planning timeframe, because availability there is either Available or Unavailable with no planned dates to filter by. All of the filters stack with each other and with search, so you can narrow by status, by timeframe, and by Region comparison at once.

Color-coded indicators make it easy to spot availability patterns. For a more compact view, click the gear icon next to the pagination control and enable "Condense region column (show icons only)" to display only status icons, allowing you to see more data at once.

It narrows the comparison to the availability statuses you care about, and it is a multiselect, so you can choose more than one. On the Services and features tab the statuses are grouped. Available is one option. Unavailable is the other, and it expands to the three specific reasons a capability is not available in a Region:

1. Not Expanding. There is no plan to bring the capability to that Region.
2. Planned. AWS has published an intent to expand, with a target quarter.
3. Planning. AWS is evaluating a launch, with no date yet.

Selecting Unavailable covers all three at once. Selecting one of the three narrows further, which is how you answer a question like "what is AWS planning for this Region but has not dated yet." Leaving the filter empty shows every status. There is a search box inside the filter, which helps once several statuses are listed. On the API operations and CloudFormation resources tabs the filter is simpler, because availability there is only Available or Unavailable.

Show only common across selected regions answers "what capabilities are available everywhere I am looking" so that you can move your service or workload for multi-region deployment. Show only differences between selected regions answers "what would need to change in my service or workload if I deployed this in one Region instead of another." Differences is usually the one to reach for when choosing between Regions, because it is a direct list of what you would lose or gain. Common is the one to reach for when confirming that a set of Regions you already run in behave consistently.

It narrows the comparison by when a capability is expected to arrive. The default is Any timeframe, which applies no restriction. The other options are quarters, After 2026 Q3, After 2026 Q4, After 2027 Q1 and onward. Each option is a lower bound rather than an exact match, so After 2027 Q1 covers everything planned from that quarter onward, not only that quarter. Use it to separate what is arriving soon from what is further out, for example by filtering Availability to Planned and setting a timeframe of After 2027 Q1 to see which capabilities will not be ready for a migration in the next two quarters.

AWS Capabilities by Region data is the authoritative source for regional availability information. The system updates as AWS launches new capabilities. If you have any concerns with the data please submit the support request.

The Availability filter uses shorter names for the same states: Available, Not Expanding, Planning for a launch being evaluated, and Planned for a capability dated to a quarter. Unavailable in that filter is a group covering the last three at once.

No. An AWS account is not required to explore regional capabilities and compare services across regions. However, signing up for availability notifications requires a free AWS Builder ID so alerts can be delivered to your account and email. If you're not signed in when you select a notification bell, you'll be prompted to sign in or create a Builder ID and returned to the same view to continue.

No, AWS Capabilities by Region and availability notifications are available at no cost. However, availability notifications require users to have a Builder ID, which does not incur any cost. The AWS Knowledge MCP Server is publicly accessible at no cost and does not require an AWS account, but usage is subject to rate limits.

Availability notifications are available on the Services and features tab. Select Notify me in the table header, and a bell appears in every cell where a capability is not yet available in that Region, with one extra column, All regions (incl. future), added at the end of the table. Select a bell to be notified when that capability becomes available in that Region, and select the same bell again to turn that notification off. There is no separate save step and no Region selection dialog; each selection takes effect immediately. Signing up for a service covers that service and every feature underneath it in the Regions you select. For example, signing up for Amazon Bedrock in a Region also covers Knowledge Bases, Guardrails, and every other Bedrock feature in that Region. Signing up for a feature covers that feature only, in the Regions you select. You can monitor any AWS Region available in AWS Capabilities by Region.

The Region columns shown are the ones in your comparison view, so adjust the Region picker to reach the Regions you want. Capabilities that are already available in a Region show a checkmark rather than a bell, because there is nothing left to notify you about.

Signing up for a service covers that service and every feature underneath it. Signing up for a feature covers that one feature. The relationship runs in one direction only: a service covers its features, but a feature does not cover its parent service and does not cover the other features of that service. So if you sign up for one feature, you are not enrolled in the rest of the service, and the service row stays available for you to sign up for separately.

It is the catch-all availability notification. Signing up for All regions means you are notified when a capability becomes available in any AWS Region, including Regions that AWS launches after you sign up. Use it when you want to hear about a capability wherever it goes next, rather than choosing Regions one at a time.

The individual Region notifications for that row are replaced by a single All regions notification, and selecting All regions again to turn it off does not bring them back. For example, if you sign up for a service in four Regions and then select All regions for that service, you have one notification rather than five. Turning the All regions notification off then leaves you with nothing for that service, and you would start again.

Because a broader notification you already have covers that cell. There are three ways a cell ends up covered:

1. You signed up for the parent service in that Region, which covers every feature of that service in that Region.
2. You signed up for the parent service under All regions, which covers every feature in every Region.
3. You signed up for that same row under All regions, which covers that row's individual Regions.

To manage the cell on its own, turn off the broader notification first. It is always visible as the filled bell on the service row above, or the filled bell in the All regions column.

Yes, in one case: a feature signed up under All regions, together with its parent service signed up in a single Region. Neither of those fully contains the other, so both are kept, and turning off one leaves the other running. Every other pairing of a service and its own feature collapses into a single notification, because one covers the other. Where two of your notifications overlap, you receive one alert rather than one per notification.

Because the service is available there but at least one of its features is not. The service cell shows a bell rather than a checkmark so you can sign up once at the service level and be notified when the remaining features land. When the service and all of its features are available in a Region, that cell shows a checkmark and there is nothing to sign up for.

The Region picker controls which columns are drawn, not what you are signed up for. Removing a Region from the comparison view hides its column, and any notification in that Region keeps running. Because the table only shows the Regions currently in your comparison view, notifications in other Regions are not visible there even though they are active. Manage Notifications is the complete list.

Notifications are delivered through two channels. In-app notifications appear within AWS Builder Center in near real time: a visual cue on the bell icon indicates new updates, and the notification panel groups alerts by service with details on capability type, Region, and availability date. Weekly email digests are sent to your Builder ID email address, consolidating all availability changes from the past week with deep links back to the comparison view. If no changes occurred during the week for services you signed up for, no email is sent.

You can manage notifications through the Manage Notifications button under Actions on the AWS Capabilities page, or through your AWS Builder Center settings, where you can filter by service name and remove alerts individually or in bulk. You can also turn a notification off directly from the comparison view by selecting Notify me and then the filled bell for that capability and Region. Bells shown in a lighter colour are already covered by a broader notification and cannot be turned off on their own; turn off the broader notification instead.

If you have signed up for notifications but are not receiving them, check the following in AWS Builder Center. Confirm email notifications are turned on in your AWS Builder Center settings. Open Manage Notifications to confirm you have active alerts for the services and Regions you expect. Review your email spam or junk folder, as weekly digest emails may occasionally be filtered, and add the sender address to your safe senders list. Remember that empty digests are not sent: if no capabilities you signed up for launched in your selected Regions during the week, no email is sent, which is expected.

Also check the level you signed up at. Signing up for a single feature notifies you about that feature only, not the other features of the same service, so sign up on the service row if you want everything for a service. Selecting All regions (incl. future) for a service or feature replaces any individual Region notifications you previously had for that row, so a Region you signed up for earlier may no longer be covered. Manage Notifications shows the full list, including Regions that are not currently shown as columns in your comparison view.

If you have confirmed all of the above and are still not receiving notifications, please reach out through the Builder Support page for further assistance.

Badges are achievement-based rewards that celebrate your engagement and milestones on AWS Builder Center. You earn them automatically by completing specific actions, including:

• Setting up your profile
• Commenting on articles and discussions
• Publishing articles
• Maintaining activity streaks
• Participating in challenges

Your earned badges are displayed on your profile page, showcasing your contributions to the AWS Builder Center community.

Badges on AWS Builder Center recognize participation and community engagement. They are not AWS certifications or skill-based validations.

Your earned badges are displayed on your public profile and visible to anyone who visits it. When you view your own profile page, you will also see available badges and your progress towards earning them.

When you're viewing your own profile, badges are displayed in three groups: 1) Badges earned; 2) Badges in progress; and 3) Badges not earned or started. When others view your public profile, they will see your earned badges only (most recent first).

Once you complete the qualifying action to earn a badge, that badge will be visible on your profile. You'll receive an in-app notification. If you also opted-in to receive email notifications, you'll receive an email based on the frequency you've selected for badge notifications.

If a badge you earned isn't displaying on your profile, you can contact Builder Center support with "I earned the badge '[badge name]' but it's not showing as earned." The AWS Builder Center team will investigate and update your profile.

Yes! You can share your achievements with others by sharing your public profile link. Your profile link can be posted on:

• Social media channels (LinkedIn, Twitter, etc.)
• Email signatures
• Professional networking sites
• Personal websites or portfolios
• Anywhere else you'd like to showcase your accomplishments

No, badges are associated with a specific Builder Profile and cannot be moved to another profile.

All streaks run on UTC. Activity counts toward the UTC calendar day (or week) in which it occurs, and daily streaks reset at 11:59:59 PM UTC. Any qualifying activity must be completed before that cutoff to count toward that day.

• Daily streaks: Complete at least one qualifying activity per UTC calendar day (before 11:59:59 PM UTC).
• Weekly streaks (e.g., publishing articles): These use fixed calendar weeks that run Monday 12:00 AM UTC through Sunday 11:59:59 PM UTC. Complete the qualifying activity at least once within each consecutive calendar week to keep the streak going. For a 4-week publishing streak, that means publishing at least one article in 4 consecutive Monday–Sunday (UTC) weeks - the specific day within the week doesn't matter. If a full calendar week passes with no qualifying activity, the streak resets.

Student Rewards is a free program that gives verified students the tools to learn AWS, build real projects, and earn a certification at no cost. Once you verify your student status on AWS Builder Center and complete your profile, you receive a welcome package, then earn additional rewards as you progress through Builder Center's badge system.

• Welcome package: a 12-month AWS Skill Builder subscription with full access to digital courses, game-based learning, labs, and exam prep content. Earned by completing student verification and your Builder Center profile.
• First milestone: $10 in AWS Credits. Earned by collecting 7 Builder Center badges.
• Second milestone: $20 in AWS Credits. Earned by collecting 14 Builder Center badges.
• Certification voucher: a $100 AWS Certification exam voucher, redeemable toward AWS Certified Cloud Practitioner. Earned by collecting all 21 Builder Center badges.

You can get started on the Student Rewards page.

There is no cost. No fee to participate, no cost to receive any reward. Creating an AWS Builder ID is free, and student verification is free. An AWS account is required to redeem some rewards. Creating an AWS account is also free, but AWS is a pay-as-you-go service. Once you begin using AWS, you will incur charges for resources consumed beyond the AWS Free Tier and beyond any credits you have applied.

• AWS Credits: you need an AWS account, because credits are applied inside an AWS account. If you do not already have one, you will need to create it to use your credits.
• Skill Builder subscriptions: in most countries these are redeemed directly on the Skill Builder portal. In Saudi Arabia, Turkey, and Ukraine, the subscription must be issued through an AWS account, even though it is provided at no charge. If your Builder Center profile lists one of those countries, you will be required to redeem the Skill Builder subscription through an AWS account.

For certification vouchers, no AWS account is needed. You apply the voucher when scheduling an exam through the AWS Certification portal.

Student Rewards is open to builders who:

• Are at least 18 years of age
• Are currently enrolled in an eligible institution
• Have an AWS Builder ID, which is free to create
• Complete student verification successfully

The following countries and regions are excluded from participation at this time: China, Cuba, Hong Kong, Iran, North Korea, Syria, Taiwan, the Crimea region of Ukraine, Tunisia, and the Donetsk People's Republic and Luhansk People's Republic regions of Ukraine. Builders under 18 are not eligible at this time. For eligible institutions, please refer to the SheerID documentation . Learners aged 13 and older can begin building cloud skills for free through AWS Educate, which has no institutional enrollment requirement.

No. An existing AWS account does not disqualify you. Builders who already have an AWS account, including accounts with paid usage, remain fully eligible. Credits earned through the program can be applied to your own AWS account, and you decide how to spend them across eligible AWS services.

No. Neither disqualifies you, and neither goes to waste. If you already have a Builder ID you keep it, then complete student verification and your Builder Center profile. Any badges you earned before verifying count retroactively toward Student Rewards milestones. If you have already earned 7 or more badges, the corresponding rewards appear in your rewards dashboard shortly after verification.

Verification takes three steps, and most students finish in a few minutes.

1. Step 1: Sign in or sign up. Go to Builder Center and select Sign in. An AWS Builder ID can be created for free with an email address, or with a Google, Apple, GitHub, or Amazon account. We recommend using a personal email address so that access to your Builder ID and any earned rewards continues after graduation.
2. Step 2: Verify your student status. Go to Edit profile > Student details, or use the Student verification link, then select Start verification and follow the steps provided by SheerID, the third-party verification service. You provide your institution name, enrollment details, and email address, and upload documentation if prompted. Note: when verifying your student status, we do recommend using your student email (if available) for the verification step. You can keep your personal email on your Builder ID and still verify with your student email without any issues.
3. Step 3: Complete your Builder Center profile. Upload a profile photo and complete the About section. Both are required to receive the Welcome package. These two actions also earn your first two badges – Photo Finisher and Hello, World!, which starts you on the path to the 7-badge milestone.

Once all three steps are complete, your verified student status is reflected on your Builder Center profile and the 12-month Skill Builder subscription appears in your rewards dashboard within minutes. If SheerID requests additional documentation (typically a class schedule or enrollment letter), verification usually completes within 24 to 48 hours.

No. The email address tied to your Builder ID does not need to be your student email to qualify for rewards, student verification, or your SBGL/SCGL membership.

We actually recommend using a personal email address, as this prevents you from being locked out of your account after graduation when your student email is deactivated.

When it comes time to verify your student status, we do recommend using your student email (if available) for the verification step. You can keep your personal email on your Builder ID and still verify with your student email without any issues.

SheerID  is a trusted identity verification service. You can read the SheerID privacy policy  for details. AWS does not store verification documents. Only the outcome, verified or not verified, is recorded in your Builder Center profile.

You can try again with alternate documentation. The most common reasons for rejection are that the institution is not eligible, the document submitted was unclear, or the enrollment dates do not reflect current enrollment. If you continue to have trouble, contact SheerID support .

Verified student status is visible only to you by default. To update student details such as your program or graduation date, go to Student details in your profile. Selecting the pencil icon in the Student details section opens those fields for editing. These fields help personalize your experience and do not affect your verification status.

Badges recognize actions builders take on Builder Center, such as uploading a profile photo, publishing a first article, commenting on content, or maintaining an activity streak. The full list, with the actions required for each, is available in your profile. Badges are available to all builders. For verified students, they also unlock rewards:

• 7 badges: $10 in AWS Credits
• 14 badges: $20 in AWS Credits
• 21 badges: a $100 AWS Certification exam voucher, available to claim, redeemable toward AWS Certified Cloud Practitioner

Verified students get a dedicated Rewards page where every earned reward appears. Each reward type takes one action to apply, covered in the next question.

Each reward type takes one action to apply:

• Skill Builder subscription: copy the coupon code from your rewards dashboard and redeem it on the Skill Builder portal.
• AWS Credits: copy the credit code and apply it in the AWS Billing and Cost Management Console  under Credits.
• Certification voucher: select Claim voucher when you are ready, then copy the issued code and apply it when scheduling your exam through the AWS Certification portal .

Skill Builder offers two ways to complete checkout, with an AWS account or without one. If checkout fails with an AWS account, retry using the other option, without an AWS account. That error is usually because the AWS account is on the AWS Free Tier free plan, which cannot complete a paid checkout flow even when the amount due is zero after your code is applied, so the code fails at the final step.

If you continue to see an error, contact Builder Support with your Builder ID, the reward type, and the error message shown at checkout.

When a code is applied at checkout, it is reserved for that session for 5 minutes. If you do not finish within that window, the reservation expires and the session times out or returns an error. The code is not lost and returns to your rewards dashboard. To avoid a repeat, complete checkout in less than 5 minutes.

If you continue to see errors after completing checkout in less than 5 minutes, contact Builder Support with your Builder ID, the reward type, and the error message shown at checkout.

• Skill Builder access: provisioned within minutes of completing verification and profile completion.
• AWS Credits: issued within 8 business days of being earned, with most students receiving them in 5 to 7 business days.
• Certification voucher: becomes available to claim as soon as you reach 21 badges. The code is issued within 8 business days of you selecting Claim voucher.

If you do not see an expected reward within these windows, contact Builder Support.

AWS Credits granted through Student Rewards are standard AWS Promotional Credits and can be applied to eligible AWS services across the AWS portfolio. You decide how to spend them. Credits are valid for at least 12 months from the date of issue, need to be applied to your AWS account, and are visible in the AWS Billing Console. Use of credits is subject to the AWS Customer Agreement  and the Builder Terms.

The certification voucher is redeemable toward the AWS Certified Cloud Practitioner or AWS Certified AI Practitioner exams and covers the full exam fee up to its $100 value. You apply the code when scheduling the exam through the AWS Certification portal. The voucher is redeemable for up to 6 months from the date it is claimed, not the date the 21-badge milestone was reached. Use of the certification voucher is subject to the AWS Customer Agreement , the Learner Terms , and the Builder Terms.

Each student can earn one $100 certification voucher. Replacement vouchers are not issued for a failed attempt.

If you do not pass, you can retake the exam under the standard retake policy on the AWS Certification site , and the retake fee is your responsibility. To prepare, you can use your Skill Builder subscription along with the free exam prep resources and study guides on the AWS Certification site.

No. Credits must be applied to your own AWS account. Skill Builder access is linked to your Builder ID, and certification vouchers are issued as single-use codes for the student identified during verification. Transferring, selling, or sharing rewards violates the Builder Terms and may result in suspension of your rewards, your AWS account, and your Builder ID. Builders suspended for violating Builder Center community or program terms are not eligible to receive further rewards.

Yes:

• Skill Builder access: active for 12 months from the date the coupon is redeemed.
• AWS Credits: active for 12 months and subject to standard AWS Promotional Credit expiry terms.
• Certification voucher: redeemable for up to 6 months from the date it is claimed.

Verified student status is valid for 11 months. You are prompted to re-verify 30 days before it expires, and we send reminders on Builder Center and by email.

When verification lapses:

• Rewards already earned are honored in full. AWS Credits, any voucher already claimed, and active Skill Builder access remain usable under their original terms.
• New rewards stop accruing until you complete re-verification.
• Re-verification does not trigger a second welcome package. The 12-month Skill Builder subscription is a one-time reward.

Graduation works the same way. Everything already earned stays with you, and you can redeem credits, use Skill Builder access, and sit the certification exam according to each reward's original expiration terms. What ends is eligibility for new rewards, once you can no longer re-verify as currently enrolled. Your Builder Center account stays active, and you are welcome to keep reading, publishing, commenting, and earning badges as a regular community member.

Student Rewards is an ongoing program. Any student who verifies receives the welcome package and can progress through the badge system for as long as they maintain verified student status. You agree to terms at three points: when creating an AWS Builder ID and claiming an alias in Builder Center (the AWS Customer Agreement and Builder Terms), when completing verification (the SheerID terms  and the Builder Terms), and when redeeming the Skill Builder coupon (the AWS Customer Agreement, Learner Terms, and Builder Terms).

For help:

• Verification issues such as rejections, documentation questions, or an institution not found: contact SheerID support .
• Reward issues such as a missing reward, a code that will not redeem, or dashboard problems: contact Builder Support. Include your Builder ID, the reward type, and a description of the issue.

• iPhone and iPad: App Store 
• Android: Google Play 

The app requires iOS 16.4 or later, or Android 12 or later.

Free. No in-app purchases, subscriptions, or paywalls.

Sign in with your AWS Builder ID. This is the same account you use on builder.aws.com. If you don't have one yet, you can create one for free when you open the app.

Yes. Everything syncs through your Builder ID. Articles you've published, Builder Spaces you've joined, badges you've earned, and people you follow are all available in the app.

In the app you can:

• Read and publish articles
• Join and create Builder Spaces
• Browse AWS Workshops
• Try sandbox environments with a free AWS account
• Take part in challenges
• Earn badges
• Discover events and meetups
• Submit Wishlist ideas to AWS product teams
• Explore AWS Capabilities by Region

16 languages: Arabic, Bahasa Indonesian, Chinese (simplified and traditional), English, French, German, Italian, Japanese, Korean, Portuguese, Russian, Spanish, Thai, Turkish, and Vietnamese.

Make sure your device's date and time are set automatically. If the issue persists, close and reopen the app. Visit AWS Builder Support for additional help.