.png?sv=2022-11-02&ss=b&srt=o&spr=https&st=2024-04-25T08%3A15%3A26Z&se=2024-04-25T08%3A25%3A26Z&sp=r&sig=zvac%2F1A3YTZry%2Ba%2B%2FIuJVOjKuaWiIntnFQKiZkRBgRI%3D){kind=logo}
AWS - Start/Stop EC2 Instances
- 21 May 2023
- 2 Minutes to read
- Print
- DarkLight
- PDF
AWS - Start/Stop EC2 Instances
- Updated on 21 May 2023
- 2 Minutes to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
AWS - Starts EC2 Instances starts an EC2 Instance for:
- Assets that match the results of the selected saved query, and match the Enforcement Action Conditions, if defined or assets selected on the relevant asset page.
AWS - Stops EC2 Instances stops an EC2 Instance for:
- Assets that match the results of the selected saved query, and match the Enforcement Action Conditions, if defined or assets selected on the relevant asset page.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
- Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
- Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
Required Fields
These fields must be configured to run the Enforcement Set.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
- Use attached IAM role
- If enabled, Axonius will use the attached IAM role / instance profile.
- If disabled, Axonius will use the supplied account details in the AWS Access Key ID and AWS Access Key Secret.
- AWS Access Key ID and AWS Access Key Secret - The credentials for an account that has the Required Permissions to start or to stop EC2 instances.
- If supplied, Axonius will use the supplied account details to start or to stop EC2 instances.
- If not supplied, Axonius will use the EC2 instance (Axonius installed on) attached IAM role / instance profile to start or to stop EC2 instances.
- Proxy - An optional https proxy.
Required Permissions
The values supplied in AWS Access Key ID and AWS Access Key Secret or the EC2 instance (Axonius installed on) attached IAM role account must have permissions to start or to stop EC2 instances:
- Start Amazon EC2 Instance - Requires ec2:StartInstances permission.
- Stop Amazon EC2 Instance - Requires ec2:StopInstances permission.
Those permissions must be added to a policy attached to relevant IAM user account.
For details on creating an IAM user and attaching policies, see Connecting the Amazon Web Services (AWS) Adapter.
NOTE
Devices (EC2 instances) fetched from an Amazon Web Services (AWS) adapter connection using an assumed role can be started/stopped only if the used account has sts:AssumeRole permission and a trust relationship for has been established for that role.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?