# Sign in with AWS Builder ID AWS Builder ID is a personal profile that provides access to select tools and services including [Amazon CodeCatalyst](https://codecatalyst.aws/), [Amazon Q Developer](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/what-is.html), and [AWS Training and Certification](https://www.aws.training/). AWS Builder ID represents you as an individual and is independent from any credentials and data you may have in existing AWS accounts. Like other personal profiles, AWS Builder ID remains with you as you progress through your personal, educational, and career goals. Your AWS Builder ID complements any AWS accounts you may already own or want to create. While an AWS account acts as a container for AWS resources you create and provides a security boundary for those resources, your AWS Builder ID represents you as an individual. For more information, see [AWS Builder ID and other AWS credentials](differences-builder-id.md). AWS Builder ID is free. You only pay for the AWS resources you consume in your AWS accounts. For more information about pricing, see [AWS Pricing](https://aws.amazon.com/pricing/). If you or your organization implement IP or domain filtering, you may need to allowlist domains to create and use an AWS Builder ID. For details about allowlisting domains, see [Domains to add to your allow list](allowlist-domains.md). **Note** AWS Builder ID is separate from your AWS Skill Builder subscription, an online learning center where you can learn from AWS experts and build cloud skills online. For more information about AWS Skill Builder, see [AWS Skill Builder](https://skillbuilder.aws/). **Topics** + [ ## To sign in with AWS Builder ID ](#sign-in-builder-id-all) + [ ## Region availability for AWS Builder ID ](#regions-aws_builder_id) + [ # Create your AWS Builder ID ](create-builder-id.md) + [ # AWS tools and services that use AWS Builder ID ](builder_id-apps.md) + [ # Edit your AWS Builder ID profile ](edit-details-builder-id.md) + [ # Change your AWS Builder ID password ](change-password-builder-id.md) + [ # Delete all active sessions for your AWS Builder ID ](delete-sessions-builder-id.md) + [ # Delete your AWS Builder ID ](delete-builder-id.md) + [ # Manage AWS Builder ID multi-factor authentication (MFA) ](mfa-builder-id.md) + [ # Privacy and data in AWS Builder ID ](privacy-builder-id.md) + [ # AWS Builder ID and other AWS credentials ](differences-builder-id.md) ## To sign in with AWS Builder ID 1. Navigate to the [AWS Builder ID profile](https://profile.aws.amazon.com/) or the sign-in page of the AWS tool or service that you want to access. For example, to access Amazon CodeCatalyst, go to [https://codecatalyst.aws](https://codecatalyst.aws). 1. Choose how to sign-in to your AWS Builder ID + [I have an existing account](#sign-in-builder-id-email) + [I have a Google Account](#sign-in-builder-id-google) + [I have an Apple Account](#sign-in-builder-id-apple) + [I have a GitHub Account](#sign-in-builder-id-github) + [I have an Amazon Account](#sign-in-builder-id-amazon) ### I have an existing account 1. For existing accounts, enter the email you used to create your AWS Builder ID and choose **Sign in**. 1. Enter the email you used to create your AWS Builder ID and choose **Sign in**. 1. On the **Sign in with your AWS Builder ID** page, enter your **Password**. 1. (Optional) If you want future sign-ins from this device to not prompt for additional verification, check the box next to **This is a trusted device**. 1. Choose Continue. 1. If prompted with an **Additional verification required** page, follow the instructions from your browser to provide the required code or security key. **Note** For your security, we analyze your sign-in browser, location, and device. If you tell us to trust this device, you won't have to provide a multi-factor authentication (MFA) code every time you sign in. For more information, see [Trusted devices](create-builder-id.md#trusted-devices-aws_builder_id). ### I have a Google Account If your Google Account is already associated with an AWS Builder ID, you must use a different email address to sign in to an application. For more information, see [I can’t sign in with Google](troubleshooting-builder-id-issues.md#sign-in-google-builder_id). 1. To use your Google Account to sign in to AWS Builder ID, choose **Continue with Google**. 1. On the **Sign in with Google** page, enter the information for your Google Account to sign in. 1. Choose **Continue** to load the AWS application homepage. ### I have an Apple Account If your Apple Account is already associated with an AWS Builder ID, you must use a different email address to sign in to an application. For more information, see [I can’t sign in with Apple](troubleshooting-builder-id-issues.md#sign-in-apple-builder_id). 1. To use your Apple Account to sign in to AWS Builder ID, choose **Continue with Apple**. 1. On the **Sign in with Apple** page, enter the information for your Apple account to sign in. 1. Choose **Continue** to load the AWS application homepage. ### I have a GitHub Account If your GitHub Account is already associated with an AWS Builder ID, you must use a different email address to sign in to an application. For more information, see [I can’t sign in with GitHub](troubleshooting-builder-id-issues.md#sign-in-github-builder_id). 1. To use your GitHub Account to sign in to AWS Builder ID, choose **Continue with GitHub**. 1. On the **Sign in with GitHub** page, enter the information for your GitHub Account to sign in. 1. Choose **Continue** to load the AWS application homepage. ### I have an Amazon Account If your Amazon Account is already associated with an AWS Builder ID, you must use a different email address to sign in to an application. For more information, see [I can’t sign in with Amazon](troubleshooting-builder-id-issues.md#sign-in-amazon-builder_id). 1. To use your Amazon Account to sign in to AWS Builder ID, choose **Continue with Amazon**. 1. On the **Sign in with Amazon** page, enter the information for your Amazon Account to sign in. 1. Choose **Continue** to load the AWS application homepage. ## Region availability for AWS Builder ID Region availability AWS Builder ID is available in the following AWS Regions. Applications that use AWS Builder ID may operate in other Regions. | Name | Code | | --- | --- | | US East (N. Virginia) | us-east-1 | # Create your AWS Builder ID You create your AWS Builder ID when you sign up for one of the AWS tools and services that use it. Sign up with your email address, name, and password as part of the sign-up process for an AWS tool or service. Your password must adhere to the following requirements: + Passwords are case-sensitive. + Passwords must be between 8 and 64 characters in length. + Passwords must contain at least one character from each of the following four categories: + Lowercase letters (a-z) + Uppercase letters (A-Z) + Numbers (0-9) + Non-alphanumeric characters (\$1\$1@\$1\$1%^&\$1\$1-\$1=`\$1\$1()\$1\$1[]:;"'<>,.?/) + The last three passwords cannot be reused. + Passwords that are publicly known through a data set leaked from a third party cannot be used. **Note** Tools and services that use AWS Builder ID direct you to create and use your AWS Builder ID when needed. **To create your AWS Builder ID** 1. Navigate to the [AWS Builder ID profile](https://profile.aws.amazon.com/) or the sign-up page of the AWS tool or service that you want to access. For example, to access Amazon CodeCatalyst, go to [https://codecatalyst.aws](https://codecatalyst.aws). 1. Choose how to create your AWS Builder ID + To use your Google Account, choose **Continue with Google** and follow the prompts to complete the sign-up process. This skips steps 3-8 below. Go to step 9. + To use your Apple Account, choose **Continue with Apple** and follow the prompts to complete the sign-up process. This skips steps 3-8 below. Go to step 9. **Note** If you choose to enable the iCloud\$1 "Hide My Email" feature for Sign in with Apple, your AWS Builder ID will be created with the designated Hide My Email address in your Apple Account instead of your real email address. You will not be able to change this email address, but your first and last name will still be editable. If you need to sign in to AWS Builder ID, you should use your Hide My Email address. AWS Builder ID will use your Hide My Email address to send email communications to you. For more details, see [ How to use Hide My Email with Sign in with Apple](https://support.apple.com/en-us/105078). + To use your GitHub Account, choose **Continue with GitHub** and follow the prompts to complete the sign-up process. This skips steps 3-8 below. Go to step 9. + To use your Amazon Account, choose **Continue with Amazon** and follow the prompts to complete the sign-up process. This skips steps 3-8 below. Go to step 9. + To create an account with email and password, continue with the following steps. 1. On the **Create AWS Builder ID** page, enter **Your email address**. We recommend that you use a personal email. 1. Choose **Next**. 1. Enter **Your name**, and then choose **Next**. 1. 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**. 1. After we verify your email, on the **Choose a password page**, enter a **Password** and **Confirm password**. 1. If a Captcha appears as additional security, enter the characters that you see. 1. Choose **Create AWS Builder ID**. ## Trusted devices After you select the **This is a trusted device** option from the sign-in page, we consider all future sign-ins from that web browser on that device authorized. This means that you don’t have to provide an MFA code on that trusted device. However, if your browser, cookies, or IP address change, you might have to use your MFA code for additional verification. # AWS tools and services that use AWS Builder ID AWS tools and services You can sign in with your AWS Builder ID to access the following AWS tools and services. Access to capabilities or benefits that are offered for a charge require an AWS account. By default, when you sign in to an AWS tool or service using your AWS Builder ID, the session duration lasts for 30 days except for Amazon Q Developer, which has a 90 day session duration. After your session ends, you will need to sign in again. **AWS Cloud Community** [Community.aws](https://community.aws/) is a platform by and for the community of AWS builders that you can access with your AWS Builder ID. It’s a place to discover educational content, share your personal thoughts and projects, comment on others’ posts, and follow your favorite builders. **Amazon CodeCatalyst** You will create an AWS Builder ID when you start using [Amazon CodeCatalyst](https://docs.aws.amazon.com/codecatalyst/latest/userguide/welcome.html) and choose an alias that will be associated with activities such as issues, code commits, and pull requests. Invite others to your Amazon CodeCatalyst space, which is complete with the tools, infrastructure, and environments your team needs to build your next successful project. You'll need an AWS account to deploy a new project to the cloud. **AWS Migration Hub** Access [AWS Migration Hub](https://aws.amazon.com/migration-hub/) (Migration Hub) with your AWS Builder ID. Migration Hub provides a single place to discover your existing servers, plan migrations, and track the status of each application migration. **Amazon Q Developer** Amazon Q Developer is a generative AI-powered conversational assistant that can help you to understand, build, extend, and operate AWS applications. For more information, see [What is Amazon Q Developer?](https://docs.aws.amazon.com/amazonq/latest/aws-builder-use-ug/what-is.html) in the *Amazon Q Developer User Guide*. **AWS re:Post** [AWS re:Post](https://repost.aws/) provides you with expert technical guidance so you can innovate faster and improve operational efficiency using AWS services. You can sign in with your AWS Builder ID and join the community on re:Post without an AWS account or credit card. **AWS Startups** Use your AWS Builder ID to join [AWS Startups](https://aws.amazon.com/startups) where you can use learning content, tools, resources, and support to grow your startup with AWS. **AWS Training and Certification** You can use your AWS Builder ID to access [AWS Training and Certification](https://www.aws.training/) where you can build your AWS Cloud skills with [AWS Skill Builder](https://skillbuilder.aws/), learn from AWS experts, and validate your cloud expertise with an industry-recognized credential. **Kiro** [Kiro](https://kiro.dev/) is an agentic IDE that helps you go from prototype to production with spec-driven development. From simple to complex tasks, Kiro works alongside you to turn prompts into detailed specs, then into working code, docs, and tests. With Kiro, what you build is exactly what you want and is ready to share with your team. Kiro’s agents help you solve challenging problems and automate tasks like generating documentation and unit tests. With Kiro, you can build beyond prototypes while being in the driver’s seat every step of the way. **Website Registration Portal (WRP)** You can use your AWS Builder ID as a persistent customer identity and registration profile for the [AWS Marketing Website](https://aws.amazon.com/). To register for new webinars and to view all webinars that you have registered for or attended, see [My webinars](https://aws.amazon.com/events/my-webinars/). # Edit your AWS Builder ID profile Edit your profile You can change your profile information at any time. You can edit the **Email address** and **Name** that you used to create an AWS Builder ID, as well as your **Nickname**. When using social logins like Google or Apple, only **Name** and **Nickname** are editable. Your **Name** is how you’re referred to in tools and services while interacting with others. Your **Nickname** indicates how you want to be known by AWS, friends, and other people you collaborate with closely. **Note** Tools and services that use AWS Builder ID direct you to create and use your AWS Builder ID when needed. **To edit your profile information** 1. Sign in to your AWS Builder ID profile at [https://profile.aws.amazon.com](https://profile.aws.amazon.com). 1. Choose **My details**. 1. On the **My details** page, choose the **Edit** button next to **Profile**. 1. On the **Edit profile** page, make any desired changes to your **Name** and **Nickname**. 1. Choose **Save changes**. A green confirmation message appears at the top of the page to let you know that you updated your profile. **Note** Changing your name and nickname with one of our other sign in partners does not update the same settings for your AWS Builder ID. **To edit your contact information** 1. Sign in to your AWS Builder ID profile at [https://profile.aws.amazon.com](https://profile.aws.amazon.com). 1. Choose **My details**. 1. On the **My details** page, choose the **Edit** button next to **Contact information**. 1. On the **Edit contact information** page, change your **Email address**. 1. Choose **Verify email**. A dialog box appears. 1. In the **Verify email** dialog box, after you receive the code in your email, enter the code in **Verification code**. Choose **Verify**. # Change your AWS Builder ID password Change your password Your password must adhere to the following requirements: + Passwords are case-sensitive. + Passwords must be between 8 and 64 characters in length. + Passwords must contain at least one character from each of the following four categories: + Lowercase letters (a-z) + Uppercase letters (A-Z) + Numbers (0-9) + Non-alphanumeric characters (\$1\$1@\$1\$1%^&\$1\$1-\$1=`\$1\$1()\$1\$1[]:;"'<>,.?/) + The last three passwords cannot be reused. **Note** Password changes are not available for AWS Builder ID accounts that use social logins such as Google or Apple. If you signed in using a social login, you manage your password through your social login account. To change your password for a social login: For a Google Account, see [Change or reset your (Google) password](https://support.google.com/accounts/answer/41078). For an Apple Account, see [Change your Apple Account password](https://support.apple.com/en-us/101567). For a GitHub Account, see [Updating your GitHub access credentials](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials). For an Amazon Account, see [How to change Amazon password](https://www.amazon.com/gp/help/customer/display.html?nodeId=GSMEQJRPX6P5JZLS). **To change your AWS Builder ID password** 1. Sign in to your AWS Builder ID profile at [https://profile.aws.amazon.com](https://profile.aws.amazon.com). 1. Choose **Security**. 1. On the **Security** page, choose **Change password**. This takes you to a new page. 1. On the **Re-enter your password** page, under **Password**, enter your current password. Then choose **Sign in**. 1. 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. 1. Choose **Change password**. You're redirected to your AWS Builder ID profile. # Delete all active sessions for your AWS Builder ID Delete all active sessions Under **Signed in devices**, you can view all the devices that you're currently signed in to. If you don't recognize a device, as a security best practice, first [change your password](https://docs.aws.amazon.com/signin/latest/userguide/change-password-aws_builder_id.html) and then sign out everywhere. You can sign out from all devices by deleting all your active sessions on the **Security** page for your AWS Builder ID. **Note** AWS Builder ID supports 90 day extended sessions for Amazon Q Developer in an IDE. For each new IDE sign in, you can see two session entries. When you sign out of your IDE, you may continue to see IDE sessions listed under **Signed in devices** even though they are no longer valid. These sessions disappear once the 90 days expire. **To delete all active sessions** 1. Sign in to your AWS Builder ID profile at [https://profile.aws.amazon.com](https://profile.aws.amazon.com). 1. Choose **Security**. 1. On the **Security** page, choose **Delete all active sessions**. 1. In the **Delete all sessions** dialog box, enter *delete all*. By deleting all your sessions, you sign out of all devices that you may have signed into using your AWS Builder ID, including different browsers. Then choose **Delete all sessions**. **Note** When using a social login account like Google or Apple, deleting active AWS Builder ID sessions will not log you out of your social login account. # Delete your AWS Builder ID The following procedure describes how to delete your AWS Builder ID account. **Warning** Deleting your AWS Builder ID will result in the following: **Loss of access** – You can no longer access any AWS tools and services that you previously accessed through AWS Builder ID. Your AWS Builder ID is separate from any AWS account you may have, and deletion of your AWS Builder ID will not close your AWS account. **Content deletion** – Any remaining content associated solely with your AWS Builder ID will be deleted and you will no longer be able to access or recover your content from applications using your AWS Builder ID. **Personal information deletion** – Any personal information you provided in connection with the creation and administration of your AWS Builder ID will be deleted, except that AWS may retain personal information as required or permitted by law, such as records of your deletion request or data in a form that does not identify you. You can find out more about how we handle your information in the [AWS Privacy Notice](https://aws.amazon.com/privacy/). You can update your AWS communication preferences or unsubscribe by visiting the [AWS Communications Preferences Center](https://pages.awscloud.com/communication-preferences.html). **Social login accounts remain unchanged** – If you are using a social login such as Google or Apple, deleting your AWS Builder ID does not delete anything related to your social login account. Refer to the documentation from your social login provider to learn how to delete those accounts. Deleting the AWS Builder ID connection from your social login account does not delete your AWS Builder ID account, but you will no longer be able to access your AWS Builder ID profile. **To delete your AWS Builder ID** 1. Sign in to your AWS Builder ID profile at [https://profile.aws.amazon.com](https://profile.aws.amazon.com). 1. Choose **Privacy & data**. 1. On the **Privacy & data** page, under **Deleting AWS Builder ID**, choose **Delete AWS Builder ID**. 1. Select the check box beside each disclaimer to confirm that you are ready to proceed. 1. Choose **Delete AWS Builder ID**. # Manage AWS Builder ID multi-factor authentication (MFA) Manage multi-factor authentication (MFA) Multi-factor authentication (MFA) is a simple and effective mechanism to enhance your security. The first factor — your password — is a secret that you memorize, also known as a knowledge factor. Other factors can be possession factors (something you have, such as a security key) or inherence factors (something you are, such as a biometric scan). We strongly recommend that you configure MFA to add an additional layer for your AWS Builder ID. You can register a built-in authenticator and also register a security key that you keep in a physically secure location. If you're unable to use your built-in authenticator, then you can use your registered security key. For authenticator applications, you can also enable the cloud backup or sync feature in those apps. This helps you avoid losing access to your profile if you lose or break your MFA device. ## Key points + We recommend that you register multiple MFA devices. If you lose access to all registered MFA devices, you will be unable to recover your AWS Builder ID. + We recommend that you periodically review your registered MFA devices to ensure they are up to date and functional. Additionally, you should store those devices in a place that is physically secure when not in use. + If you created your account using **Continue with Google**, you can enable multi-factor authentication through your Google account. For details, see [Turn on 2-Step Verification](https://support.google.com/accounts/answer/185839). + If you created your account using **Continue with Apple**, multi-factor authentication is likely already enabled in your Apple Account. If not, for details on how to enable it, see [Two-factor authentication for Apple Account](https://support.apple.com/en-us/102660). + If you created your account using **Continue with GitHub**, you can enable multi-factor authentication through your GitHub Account. For details, see [Configuring (GitHub) two-factor authentication](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication). + If you created your account using **Continue with Amazon**, you can enable multi-factor authentication through your Amazon Account. For details, see [What is Two-Step Verification?](https://www.amazon.com/gp/help/customer/display.html?nodeId=G3PWZPU52FKN7PW4). ## Available MFA types for AWS Builder ID Available MFA types AWS Builder ID supports the following multi-factor authentication (MFA) device types. ### FIDO2 authenticators [FIDO2](https://fidoalliance.org/fido2/) is a standard that includes CTAP2 and [WebAuthn](https://www.w3.org/TR/webauthn-2/) and is based on public key cryptography. FIDO credentials are phishing-resistant because they are unique to the website that the credentials were created such as AWS. AWS supports the two most common form factors for FIDO authenticators: built-in authenticators and security keys. See below for more information about the most common types of FIDO authenticators. **Topics** + [ #### Built-in authenticators ](#built-in-auth-aws_builder_id) + [ #### Security keys ](#security-keys-aws_builder_id) + [ #### Password managers, passkey providers, and other FIDO authenticators ](#other-mfa-aws_builder_id) #### Built-in authenticators Some devices have built-in authenticators, such as TouchID on MacBook or a Windows Hello-compatible camera. If your device is compatible with FIDO protocols, including WebAuthn, you can use your fingerprint or face as second factor. For more information, see [FIDO Authentication](https://fidoalliance.org/fido2/). #### Security keys You can purchase a FIDO2-compatible external USB, BLE, or NFC-connected security key. When you’re prompted for an MFA device, tap the key’s sensor. YubiKey or Feitian make compatible devices. For a list of all compatible security keys, see [ FIDO Certified Products](https://fidoalliance.org/certification/fido-certified-products/ ). #### Password managers, passkey providers, and other FIDO authenticators Multiple third party providers support FIDO authentication in mobile applications, as features in password managers, smart cards with a FIDO mode, and other form factors. These FIDO-compatible devices can work with IAM Identity Center, but we recommend that you test a FIDO authenticator yourself before enabling this option for MFA. **Note** Some FIDO authenticators can create discoverable FIDO credentials known as passkeys. Passkeys may be bound to the device that creates them, or they may be syncable and backed up to a cloud. For example, you can register a passkey using Apple Touch ID on a supported Macbook, and then log in to a site from a Windows laptop using Google Chrome with your passkey in iCloud by following the on-screen prompts at sign-in. For more information about which devices support syncable passkeys and current passkey interoperability between operating systems and browsers, see [Device Support](https://passkeys.dev/device-support/) at [passkeys.dev](https://passkeys.dev/), a resource maintained by the FIDO Alliance And World Wide Web Consortium (W3C). ### Authenticator applications Authenticator apps are one-time password (OTP)-based third party-authenticators. You can use an authenticator application installed on your mobile device or tablet as an authorized MFA device. The third-party authenticator application must be compliant with RFC 6238, which is a standards-based time-based one-time password (TOTP) algorithm capable of generating six-digit authentication codes. When prompted for MFA, you must enter a valid code from your authenticator app within the input box presented. Each MFA device assigned to a user must be unique. Two authenticator apps can be registered for any given user. You can choose from the following well-known third-party authenticator apps. However, any TOTP-compliant application works with AWS Builder ID MFA. | Operating system | Tested authenticator app | | --- | --- | | Android | [1Password](https://play.google.com/store/apps/details?id=com.onepassword.android), [Authy](https://play.google.com/store/apps/details?id=com.authy.authy), [Duo Mobile](https://play.google.com/store/apps/details?id=com.duosecurity.duomobile), [Microsoft Authenticator](https://play.google.com/store/apps/details?id=com.azure.authenticator), [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2) | | iOS | [1Password](https://apps.apple.com/us/app/1password-password-manager/id1511601750), [Authy](https://apps.apple.com/us/app/authy/id494168017), [Duo Mobile](https://apps.apple.com/us/app/duo-mobile/id422663827), [Microsoft Authenticator](https://apps.apple.com/us/app/microsoft-authenticator/id983156458), [Google Authenticator](https://apps.apple.com/us/app/google-authenticator/id388497605) | ## Register your AWS Builder ID MFA device **Note** After you sign up for MFA, sign out, and then sign in on the same device, you might not be prompted for MFA on trusted devices. **To register your MFA device using an authenticator app** 1. Sign in to your AWS Builder ID profile at [https://profile.aws.amazon.com](https://profile.aws.amazon.com). 1. Choose **Security**. 1. On the **Security** page, choose **Register device**. 1. On the **Register MFA device** page, choose **Authenticator app**. 1. AWS Builder ID operates and displays configuration information, including a QR code graphic. The graphic is a representation of the "secret configuration key" that is available for manual entry in authenticator apps that do not support QR codes. 1. Open your authenticator app. For a list of apps, see [Authenticator applications](#auth-apps-aws_builder_id). If the authenticator app supports multiple MFA devices or accounts, choose the option to create a new MFA device or account. 1. Determine whether the MFA app supports QR codes, and then do one of the following on the **Set up your authenticator app** page: 1. Choose **Show QR code**, and then use the app to scan the QR code. For example, you might choose the camera icon or choose an option similar to **Scan code**. Then use the device's camera to scan the code. 1. Choose **Show secret key**, and then enter that secret key into your MFA app. When you finish, your authenticator app will generate and display a one-time password. 1. In the **Authenticator code** box, enter the one-time password that currently appears in your authenticator app. Choose **Assign MFA**. **Important** Submit your request immediately after generating the code. If you generate the code and then wait too long to submit the request, the MFA device is successfully associated with your AWS Builder ID, but the MFA device is out of sync. This happens because time-based one-time passwords (TOTP) expire after a short period of time. If this happens, you can resync the device. For more information, see [I get the message 'An unexpected error has occurred' when I try to register or sign in with an authenticator app](troubleshooting-builder-id-issues.md#syncing-mfa-aws_builder_id). 1. To give your device a friendly name in AWS Builder ID, choose **Rename**. This name helps you distinguish this device from others that you register. The MFA device is now ready for use with AWS Builder ID. ## Register a security key as your AWS Builder ID MFA device **To register your MFA device using a security key** 1. Sign in to your AWS Builder ID profile at [https://profile.aws.amazon.com](https://profile.aws.amazon.com). 1. Choose **Security**. 1. On the **Security** page, choose **Register device**. 1. On the **Register MFA device** page, choose **Security key**. 1. Ensure that your security key is enabled. If you use a separate physical security key, connect it to your computer. 1. Follow the instructions on your screen. Your experience varies based on your operating system and browser. 1. To give your device a friendly name in AWS Builder ID, choose **Rename**. This name helps you distinguish this device from others that you register. The MFA device is now ready for use with AWS Builder ID. ## Rename your AWS Builder ID MFA device **To rename your MFA device** 1. Sign in to your AWS Builder ID profile at [https://profile.aws.amazon.com](https://profile.aws.amazon.com). 1. Choose **Security**. When you arrive at the page, you see that **Rename** is grayed out. 1. Select the MFA device that you want to change. This allows you to choose **Rename**. Then a dialog box appears. 1. In the prompt that opens, enter the new name in **MFA device name**, and choose **Rename**. The renamed device appears under **Multi-factor authentication (MFA) devices**. ## Delete your MFA device We recommend that you keep two or more active MFA devices. Before you remove a device, see [Register your AWS Builder ID MFA device](#register-mfa-aws_builder_id) to register a replacement MFA device. To disable multi-factor authentication for your AWS Builder ID, remove all registered MFA devices from your profile. **To delete an MFA device** 1. Sign in to your AWS Builder ID profile at [https://profile.aws.amazon.com](https://profile.aws.amazon.com). 1. Choose **Security**. 1. Select the MFA device that you want to change and choose **Delete**. 1. In the **Delete MFA device?** modal, follow the instructions to delete your device. 1. Choose **Delete**. The deleted device no longer appears under **Multi-factor authentication (MFA) devices**. # Privacy and data in AWS Builder ID Privacy and data The [AWS Privacy Notice](https://aws.amazon.com/privacy/) outlines how we handle your personal data. For information on how to delete your AWS Builder ID profile, see [Delete your AWS Builder ID](delete-builder-id.md). ## Request your AWS Builder ID data You can request and view the personal information associated with your AWS Builder ID and the AWS applications and services you accessed with your AWS Builder ID. For more information about exercising your data subject rights, including for personal information provided in relation to other AWS websites, applications, products, services, events, and experiences, see [https://aws.amazon.com/privacy](https://aws.amazon.com/privacy). **To request your data** 1. Sign in to your AWS Builder ID profile at [https://profile.aws.amazon.com](https://profile.aws.amazon.com). 1. Choose **My AWS Builder ID data**. 1. On the **My AWS Builder ID data** page, under **Deleting AWS Builder ID**, choose **Request your data**. 1. A green confirmation message appears at the top of the page that we received your request and will complete it within 30 days. 1. 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**. While your data request is pending, you will not be able to delete your AWS Builder ID. # AWS Builder ID and other AWS credentials Your AWS Builder ID is separate from any AWS account or sign in credential. You can use the same email for your AWS Builder ID and for the root user email of an AWS account. An AWS Builder ID: + Allows you to access tools and services that use AWS Builder ID. + Doesn't impact existing security controls, such as policies and configurations that you've specified on your AWS accounts or applications. + Doesn't replace any existing root, IAM Identity Center, or IAM users, credentials, or accounts. + Can't obtain AWS IAM credentials to access the AWS Management Console, AWS CLI, AWS SDKs, or AWS Toolkit. An AWS account is a resource container with contact and payment information. It establishes a security boundary in which to operate billed and metered AWS services, like S3, EC2, or Lambda. Account owners can sign in to an AWS account in the AWS Management Console. For more information see [Signing in to the AWS Management Console](https://docs.aws.amazon.com/signin/latest/userguide/console-sign-in-tutorials.html). ## How AWS Builder ID relates to your existing IAM Identity Center identity As the individual who owns the identity you manage the AWS Builder ID. It's not connected to any other identity you may have for another organization, such as school or work. You might use a workforce identity in IAM Identity Center to represent your work-self and an AWS Builder ID to represent your private-self. These identities operate independently. Users in AWS IAM Identity Center (successor to AWS Single Sign-On) are managed by a corporate IT or cloud administrator, or by the administrator of the organization’s identity provider, such as Okta, Ping, or Azure. Users in IAM Identity Center can access resources across multiple accounts in AWS Organizations. ## Multiple AWS Builder ID profiles You can create more than one AWS Builder ID as long as each ID uses a unique email address. However, using more than one AWS Builder ID can make it difficult to recall which AWS Builder ID you used for which purpose. When possible, we recommend using a single AWS Builder ID for all your activities in AWS tools and services.