Managing your elastic agents
Managing Elastic Bamboo
On this page
In this section
Related content
- How to Configure a Cluster Without Multicast Traffic
- Cluster Nodes Can Connect to the Database, but Fail to Make a Cluster
- 'Multicast address does not correspond with cluster name' during Cluster Configuration
- Cluster Panic due to Multicast Traffic Communication Problem
- Confluence Data Center won't start due to no matching network interface found
- Cluster panic is triggered in Confluence Data Center when a node rejoins the cluster
- Confluence Data Center fails to start with Hazelcast phone home error
- Interface IP is incorrect and not found while starting Hazelcast in a dockerized environment for Confluence Data Center
- Confluence Datacenter reports Hazelcast port already in use for separate nodes on different hosts
- Interface IP is incorrect and not found while starting Hazelcast in a dockerized environment for Confluence Data Center
An elastic agent is an agent that runs in the Amazon Elastic Compute Cloud (EC2). An elastic agent process runs in an elastic instance of an elastic image. An elastic agent inherits its capabilities from the elastic image that it was created from.
- To view your elastic agents, see Viewing your elastic agents.
- To view elastic agents that have terminated, see Viewing your elastic agent usage history.
- To configure your elastic agent's capabilities, see Configuring elastic agent capabilities.
- To disable an elastic agent, see Disabling an elastic agent.
Last modified on Sep 28, 2017
In this section
Related content
- How to Configure a Cluster Without Multicast Traffic
- Cluster Nodes Can Connect to the Database, but Fail to Make a Cluster
- 'Multicast address does not correspond with cluster name' during Cluster Configuration
- Cluster Panic due to Multicast Traffic Communication Problem
- Confluence Data Center won't start due to no matching network interface found
- Cluster panic is triggered in Confluence Data Center when a node rejoins the cluster
- Confluence Data Center fails to start with Hazelcast phone home error
- Interface IP is incorrect and not found while starting Hazelcast in a dockerized environment for Confluence Data Center
- Confluence Datacenter reports Hazelcast port already in use for separate nodes on different hosts
- Interface IP is incorrect and not found while starting Hazelcast in a dockerized environment for Confluence Data Center
Powered by Confluence and Scroll Viewport.