By default Axiom lists all EC2 in AWS accounts you have integrated into Axiom. Learn more about Axiom's EC2 Remote Connect
If you don't want EC2s to appear as selectable Targets at all (in the request form, scopes, and workflows), follow the steps below:
Check if any of your users already created requests where the Target is an EC2 instance. If any of your users have already created such requests, then do not proceed, and instead contact Axiom technnical support.
Prevent Axiom from identifying EC2s as addressable Targets, by updating the AWS IAM policy which is attached to the IAM role used for the Axiom integration.
Go to your AWS IAM console and locate the IAM policy named “AxiomAWSIntegrationPolicy” attached to the IAM role “AxiomIntegrationRole” (these are the default names, but they may be different if you manually changed them when you were setting up your AWS integration).
Remove the following from AxiomAWSIntegrationPolicy:
ec2:Describe*logs:GetL*ssm:DescribeI*ssm:DescribeS*
Run a manual scan for the affected AWS account/s, so that Axiom can re-map your AWS environment, without including EC2s.