CloudAMQP 2FA: how to set up an authenticator app

CloudAMQP hosts RabbitMQ and LavinMQ message brokers, and your CloudAMQP account is where you create instances, manage billing and invite teammates. Two-factor authentication (2FA) on that account works with an authenticator app. CloudAMQP builds it on the standard time-based codes (TOTP), so it isn't tied to one app (CloudAMQP).

Two things set CloudAMQP apart. Its documentation describes no backup codes, only an optional backup phone number for text messages. And while 2FA is optional for you, a team admin can make it mandatory for the whole team.

The steps below use Authenticator App - Novaz on iPhone. Any authenticator app works the same way.

How we checked this guide: the CloudAMQP steps come from CloudAMQP's own documentation and blog, linked below, including the screenshots in its documentation, which we read on October 21, 2026. We haven't tested them on a CloudAMQP account, so a label may differ slightly. The Novaz steps are checked against the app, version 1.0.5.

Turn on 2FA with an authenticator app

CloudAMQP's documentation describes these steps (CloudAMQP):

1. In the CloudAMQP console, open Account Settings from the user menu.
2. On the Two-Factor Authentication row, click Enable Two-Factor.
3. Re-enter your password if asked. Account settings are locked by default and stay unlocked for about 15 minutes once you confirm.
4. The Authenticator app page shows a QR code. In Novaz, tap +, then Scan QR code, and point the camera at it. On the same iPhone, take a screenshot and use Choose a photo. See scanning a QR code on the same iPhone.
5. If you can't scan it, use the line under the QR code that reads Or use the security code. Click the eye icon to show the hidden key, or the copy icon. In Novaz, tap +, then Enter key manually, and enter it as the Setup key. See What is a 2FA setup key?
6. Type the six-digit code from Novaz into the Token field and click Verify token and enable two-factor authentication.

The page then shows two-factor authentication as Enabled. The setup screen names Google's app, but CloudAMQP's blog says any authenticator app works (CloudAMQP).

CloudAMQP mentions six-digit codes but doesn't say how often they change. Scanning the QR code is the safer route, because the QR code carries those settings to your app.

Add a backup phone number

Once the authenticator app is on, CloudAMQP lets you add a backup phone number that can receive a code by text message if you lose the app. It's the only backup method the documentation names, and CloudAMQP is clear that the app stays the main method: a phone number "on its own is not considered sufficient" (CloudAMQP).

If you lose your iPhone without a Novaz backup (iCloud backup or a backup file), that number is your safety net. Pick one you'll keep for years. For the trade-offs of text-message codes, see Authenticator app vs SMS.

Signing in

With 2FA on, CloudAMQP asks for a code every time you sign in, right after your password. The sign-in screen is titled Two-factor authentication: type the current code from Novaz and click Verify. If you tick Remember this device, that browser skips the code for a while. CloudAMQP doesn't say for how long. With a backup number registered, Get code by SMS on the same screen sends a code by text instead (CloudAMQP).

The documentation describes this for password sign-in. It doesn't say how 2FA applies if you sign in with Google or through your company's SAML single sign-on.

When your team requires it

A team admin can turn on Enforced Two-factor authentication under Team > Settings. While it's on, any member who hasn't set up 2FA loses access to that team until they do (CloudAMQP). Admins should warn the team first.

If CloudAMQP rejects your code

CloudAMQP's documentation doesn't cover rejected codes. The most common cause is the iPhone's clock: open Settings > General > Date & Time and turn on Set Automatically. Novaz also warns you when the clock is 15 seconds or more off. Other causes are in Authenticator code not working?

Changing phones

CloudAMQP doesn't document a way to move 2FA to a new phone. What it does document is turning 2FA off with a current code and turning it on again, so do this while you still have the old phone. Then add CloudAMQP to the new phone from the fresh QR code. If you have a Novaz iCloud backup or backup file, you can skip all this and restore your accounts on the new iPhone instead. Turning 2FA off also removes your backup phone number, so add it again afterwards. See How to transfer your authenticator app to a new iPhone.

If you lose your authenticator

If you added a backup phone number, use Get code by SMS on the sign-in screen. Then set up the authenticator again.

Without a backup number, CloudAMQP's documentation says to email support@cloudamqp.com, and its support team will help you get back into the account (CloudAMQP). It doesn't say what proof support asks for or how long it takes. More in Lost the phone with your authenticator app?

Turning 2FA off

Open Account Settings > Two-Factor, and in the Disable two-factor authentication section type a current code into Token and click Disable two-factor authentication. Any backup phone number is removed at the same time (CloudAMQP). Then you can open the entry in Novaz and tap Remove account.

Official CloudAMQP help

• Two-Factor Authentication (CloudAMQP documentation)
• Two-Factor Authentication (CloudAMQP blog, last updated August 7, 2026)