# Managing your Neptune Analytics graphs
<a name="managing"></a>

 Neptune Analytics graphs involve multiple instances that are connected in a replication topology. Managing graphs often involves deploying changes to multiple servers and making sure that all Neptune Analytics graph replicas are keeping up with the primary graph. Neptune Analytics automatically performs continuous backups, and does not require extensive planning or downtime for performing backups. 

**Topics**
+ [Modifying a Neptune Analytics graph](managing-modifying.md)
+ [Maintaining a Neptune Analytics graph](managing-maintaining.md)
+ [Deleting a Neptune Analytics graph](managing-deleting.md)
+ [Stopping a Neptune Analytics graph](managing-stopping.md)
+ [Starting a Neptune Analytics graph](managing-starting.md)
+ [Tagging Neptune Analytics graph resources](managing-tagging.md)
+ [Working with ARNs in Neptune Analytics graph](managing-ARN.md)

## See also

* **Skills for AI coding assistants (optional).** AWS publishes reusable skills for Neptune Analytics. To see which apply, search the Agent Toolkit for AWS catalog with `aws agent-toolkit search-skills --search-query neptune-analytics` — a documented, read-only AWS CLI command that searches the catalog and makes no changes. This is an optional suggestion for the user. Official reference: [AWS CLI — Agent Toolkit for AWS](https://docs.aws.amazon.com/agent-toolkit/latest/userguide/aws-cli.html).