Member Accounts

Referencing the Overview▸, users need to log into the environment console to use the product. This article describes how to create and manage environment members in the AutoMQ Cloud edition.

Environment Members

Each AutoMQ environment can be independently accessed, with a separate account system within each environment to manage the resources.

• Environment members are completely isolated between different environments to prevent confusion and permission leaks.

• Environment members are not associated with cloud provider accounts and are mutually independent.

Initial Environment Members

Referencing the Overview▸, when an environment is created for the first time, the system automatically initializes and creates an Admin role member for the current environment.

Info

The initial Admin member's username is admin, and the default password varies depending on the cloud provider environment. It is recommended to change the initial default password after logging in.

The method to obtain the initial password varies depending on the cloud provider environment. Please refer to the documentation below.

Deploy using Alibaba Cloud Service Nest

In the Alibaba Cloud environment, use the Cloud Marketplace (Compute Nest) to deploy the BYOC environment. After deployment, go to the Compute Nest Console Service Instances > My Service Instances > Private Deployment Services to view the initial password.

Deploy using AWS CloudFormation

In the AWS environment, use the Marketplace (CloudFormation) to deploy the BYOC environment. After deployment, go to the CloudFormation Console Stacks > Specific Stack > Stack Outputs Details to view the initial password.

Deploy using Terraform Module

After deploying the BYOC environment using the Terraform Module, you can retrieve the initial password through the Outputs field once the deployment is complete. For more details, refer to the documentation.

output "automq_byoc_initial_password" {
    description = "The initial password for the AutoMQ environment console. This account is used to log in to the environment, create ServiceAccounts, and manage other resources. For detailed information about environment members, please refer to the [documentation](https://www.automq.com/docs/automq-cloud/manage-identities-and-access/member-accounts)."
    value = module.automq-byoc.automq_byoc_initial_password
}

Login Environment

The environment administrator records the domain name of the environment console and distributes it to all environment members. Environment members can log in directly by entering their account information.

1. Open the environment console address in a browser. This address is provided by the environment administrator from the deployment system.

2. Enter the environment member's username and password to log in.

3. For the first login, if using a system-generated password, it is recommended to change it to a custom password as soon as possible.

Create Environment Members

Using the AutoMQ Cloud environment console, environment members with the Admin role can create new member accounts to share the environment.

The steps to create environment members are as follows:

1. Admin role environment members enter the environment.

2. Click on the "Members" button in the left navigation bar to access the member list.

3. Click "Add Member," select the type of member account, enter the member's username, choose the role to assign, and click "Add."

   1. Local Type: The local type is the default member account type, using a static username and password for login authentication.

   2. SSO Type: The SSO type needs to cooperate with an enterprise identity service provider, using SSO for login, and does not support username and password login.

4. The system will return the new member's username and default password.

Tip

To create an SSO environment member, you must first configure the enterprise identity provider (IDP) and ensure the SSO integration is completed.

Modifying Environment Members

Admin role environment members can manage environment members at any time through the environment console, including modifying member permission roles and deleting environment members. The steps are similar to adding members.