Amazon EC2 managed instances

An Amazon EC2 managed instance is an EC2 instance that is provisioned and managed by a designated service provider, such as Amazon EKS through EKS Auto Mode. Managed instances provide a simplified way for running compute workloads on Amazon EC2 by allowing you to delegate operational control of the instance to a service provider.

Delegated control is the only change introduced for managed instances. The technical specifications and billing remain the same as non-managed EC2 instances. Because managed instances allow you to delegate control to the service provider, you can benefit from the service provider’s operational expertise and best practices. When an instance is managed, the service provider is responsible for tasks such as provisioning the instance, configuring software, scaling capacity, handling instance failures and replacements, and terminating the instance.

You can’t directly modify the settings of a managed instance or terminate it. The service and specific operations are determined by the agreement between you and the service provider. However, you can add, modify, or remove tags from your managed instances, allowing you to categorize them within your AWS environment.

Billing for managed instances

An Amazon EC2 managed instance incurs the same base charge as a non-managed Amazon EC2 instance, plus a separate fee for the service provider. This additional fee is charged by the service provider managing your instance and is billed separately. It covers the cost of services provided for operating and maintaining your managed instance.

All Amazon EC2 purchasing options are available for managed instances, including On-Demand Instances, Reserved Instances, Spot Instances, and Savings Plans. By sourcing your compute directly from EC2 and then providing it to your service provider, you benefit from any existing Reserved Instances or Savings Plans applied to your account, ensuring that you're using the most cost-effective compute capacity available.

For example, when using Amazon EKS Auto Mode, you pay the standard EC2 instance rate for the underlying instances, plus an additional charge from Amazon EKS for managing the instances on your behalf. If you then decide to sign up for a Savings Plans, the EC2 instance rate is reduced by the Savings Plans, while the additional charge from Amazon EKS remains unchanged.

Identify managed instances

Managed instances are identified by a true value in the Managed field. The service provider is identified in the Operator field (in the console) or Principal field (in the CLI).

Use the following procedures to identify managed instances.

Console

To identify a managed instance

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Instances.

3. Select the instance you want to check.

4. On the Details tab (if you selected the checkbox) or in the summary area (if you selected the instance ID), find the Managed field.

   • A value of true indicates a managed instance.

   • A value of false indicates a non-managed instance.

5. If Managed is set to true, the Operator field displays a value identifying the service provider responsible for managing the instance. For example, a value of eks.amazonaws.com identifies Amazon EKS as the service provider.

AWS CLI

To identify a managed instance

Use the describe-instances command and specify the instance ID.

aws ec2 describe-instances \
    --instance-ids i-1234567890abcdef0 \
    --query Reservations[].Instances[].Operator

The following is example output. If Managed is true, the instance is a managed instance and a Principal is included. The principal is the service provider that manages the instance. For example, a value of eks.amazonaws.com identifies Amazon EKS as the service provider.

[
    {
        "Managed": true,
        "Principal": "eks.amazonaws.com"
    }
]

To find your managed instances

Use the describe-instances command and specify the operator.managed filter with a value of true. The --query option displays only the IDs of the managed instances.

aws ec2 describe-instances \
    --filters "Name=operator.managed,Values=true" \
    --query Reservations[*].Instances[].InstanceId

PowerShell

To identify a managed instance

Use the Get-EC2Instance cmdlet.

(Get-EC2Instance -InstanceId i-1234567890abcdef0).Instances.Operator

The following is example output.

Managed Principal
------- ---------
True    eks.amazonaws.com

To find your managed instances

Use the Get-EC2Instance cmdlet. This example displays only the IDs of the managed instances.

(Get-EC2Instance -Filter @{Name="operator.managed"; Values="true"}).Instances.InstanceId

Managed resource visibility settings

You can control whether resources that AWS services provision on your behalf appear in your Amazon EC2 console views and API list operations.

What is managed resource visibility?

AWS services such as Amazon EKS, Amazon ECS, Workspaces, and AWS Lambda provision and operate Amazon EC2 instances directly within your account. These services assume responsibility for scaling, OS patches, security updates, and lifecycle management. The resulting Amazon EC2 instances, Amazon EBS volumes, Amazon EBS snapshots, and network interfaces (ENIs) appear alongside your customer-managed resources in the Amazon EC2 console and APIs. Managed resource visibility settings give you control over whether these managed resources surface in your resource views.

Affected resource types

Why configure visibility settings

Configuring visibility settings lets you tailor how managed resources appear across your operational tooling. Common use cases include:

Configure managed resource visibility

You can configure managed resource visibility by using the Amazon EC2 console or the AWS CLI.

Console

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Dashboard.

3. On the Account attributes card, under Settings, choose Managed resource visibility.

4. Choose Manage.

5. Toggle visibility on or off for managed instances.

6. Choose Save changes.

AWS CLI

Get current visibility settings

Use the get-managed-resource-visibility command to retrieve the current visibility configuration:

aws ec2 get-managed-resource-visibility

Example response:

{
    "visibility": {
        "defaultVisibility": "hidden"
    }
}

Hide all managed resources

Use the modify-managed-resource-visibility command to hide all managed resources regardless of operator:

aws ec2 modify-managed-resource-visibility \
    --default-visibility "hidden"

Discover hidden managed resources

When you turn off visibility, you can still access managed resources. The following methods surface them on demand:

Billing considerations

Managed resource visibility settings have no effect on billing. Hidden managed instances continue to appear in billing data because they are resources running within your account, provisioned on your behalf, and remain fully billable regardless of visibility configuration.

Hidden resources remain visible in:

Limitations

Get started with managed instances

For guidance on using managed instances, see Automate cluster infrastructure with EKS Auto Mode in the Amazon EKS User Guide.