In the previous lesson, you learned about Aura and how it differs from self-managed databases.
In this lesson, you will learn about the different responsibilities of Aura and its users.
Aura operates on a shared responsibility model, where Neo4j handles the operational aspects of the database while users focus on their applications and data. This model allows you to benefit from the power of Neo4j without worrying about the underlying infrastructure.
Aura’s Responsibilities
Aura is responsible for the following:
-
Infrastructure Management: Aura manages the underlying infrastructure, including servers, storage, and networking.
-
Database Maintenance: Aura handles database maintenance tasks such as backups, updates, and scaling.
-
Security: Aura provides security features such as encryption, access control, and compliance with industry standards.
User Responsibilities
Users are responsible for the following:
-
Data Modeling: Users must design and implement their data models using Neo4j’s graph data model.
-
Application Development: Users are responsible for developing applications that interact with the Neo4j database.
-
Monitoring and Optimization: Users should monitor their database performance and optimize queries as needed.
By understanding these shared responsibilities, you can effectively manage your Neo4j Aura instances and build successful applications.
User roles
In addition to the shared responsibilities, it’s important to understand the different user roles within an Aura organization:
-
Organisation Admin: Has full access to all projects and instances within the organization. Can manage users, billing, and organization settings. You will get this role when you create a new Aura account.
-
Project Admin: Has full access to all instances within a specific project. Can manage users and project settings.
-
Project Member: Has read and write access to instances within a specific project but cannot manage users or settings.
-
Project Viewer: Has read-only access to instances within a specific project. Cannot make any changes to the database or settings.
-
Metrics Reader: Has access to view performance metrics and monitoring data for instances within a specific project. Cannot make any changes to the database or settings.
If you would like to learn more about the shared responsibility model, you can refer to the [Neo4j Aura Security Whitepaper](https://neo4j.com/books/neo4j-aura-security/) for a detailed overview of the security measures and responsibilities in Aura.
Invite users to your project
To invite users to your project, follow these steps:
-
Go to the Project Settings page in the Aura console.
-
Click on the Users menu.
-
Click on the Invite Users button.
-
Enter the email addresses of the users you want to invite.
-
Select the appropriate roles for the invited users.
Click Send Invites to send the invitations.
To review the full list of your project users, go to the Users menu in the Project Settings page, where you can see their roles and statuses.
Delete users from your project
To delete users from your project, follow these steps:
-
Go to the Project Settings page in the Aura console.
-
Click on the Users menu.
-
Find the user you want to delete and click on the Delete button next to their name.
-
Confirm the deletion when prompted.
Check your understanding
Making the Right Choice
You are planning to have a new team of data analysts working on a Neo4j Aura instance for a critical project.
Their role will involve analysing metrics, but they won’t be making any changes to the database itself.
Which one of the following roles is the right choice for you?
-
❏ Project Admin
-
❏ Project Member
-
✓ Metrics Reader
-
❏ Project Viewer
Hint
Think about the permissions each role provides and what your team needs to accomplish their tasks.
Solution
The correct answer is Metrics Reader. This role allows users to view performance metrics and monitoring data for instances within a specific project without making any changes to the database or settings.
This is ideal for your data analysts who need to analyze metrics but do not require write access or the ability to manage users or settings.
Summary
In this lesson, you learned about the different responsibilities of Neo4j Aura and its users, and how Aura simplifies the management of graph databases in the cloud.
In the next lesson, you will learn how to take your learning journey further with additional resources and learning paths on GraphAcademy.