Home/Templates/An analysis machine that cannot reach production
An analysis machine that cannot reach production
A clean-room virtual machine for looking at suspicious files, with no route to anything live, on four clouds.
Terraform
Why bother
Opening malware or reviewing a disk image on a machine that can reach production turns one incident into two. This builds a workstation with no way out and a snapshot taken when it shuts down.
From the workstation, try to reach a production subnet. It should fail.
How it works
Set it up
Pick your platform, then open the level you want. Each level is complete on its own. Read the comments in the files as you go. Anything with a real consequence is explained on the line where it happens.
Terraform. An isolated VPC with no internet gateway, reached through Session Manager only
What you need first
- An account for forensics, kept separate from production if you can.
- The evidence bucket, such as the evidence capture template's.
- For Standard, the analysts' roles and an SNS topic for the alerts.
What it creates
- A VPC with no internet gateway, NAT, or peering, and private endpoints for Session Manager
- An S3 endpoint whose policy allows reads from the evidence bucket and the Amazon Linux package repository only
- A workstation with no inbound rules, an encrypted disk, and read access to the evidence
- DNS limited to AWS's own names, flow and query logs, and alarms when anything on it tries to reach out (Standard)
- A policy letting analysts open sessions on it and attach evidence volumes to it (Standard)
See the two alerts this creates
The code
Quick startReady
evidence_bucket = "your-evidence-bucket"main.tf, line 19
aws sts get-caller-identity
Shows the account and role you are signed in as. Check it before every apply.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform destroy
When you have finished. If it refuses, How to undo it below explains why.
Formatting passedValid passedLint passed
Security scan: 64 checks passed, and two rules flagged, each with a written reason:
Last run 2026-10-02 with OpenTofu v1.12.6 against hashicorp/aws 6.66.0.
Open main.tf as plain text
StandardReady
evidence_bucket. The bucket evidence is read from, such as the evidence capture template's.analyst_role_arns. Roles allowed to open sessions on the workstation and attach evidence volumes to it.alert_topic_arn. SNS topic told when something on the workstation tries to connect out, or looks up a name outside AWS.
aws sts get-caller-identity
Shows the account and role you are signed in as. Check it before every apply.# terraform.tfvars evidence_bucket = "" analyst_role_arns = "" alert_topic_arn = ""
Create this file beside the others and fill in your values. Terraform reads it on its own.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform output verify
Prints the commands that prove it worked.
Formatting passedValid passedLint passed
Security scan: 120 checks passed, and four rules flagged, each with a written reason:
- IAM permissions management without constraints
- IAM write access without constraints
- Log group encrypted with KMS
- IAM resource of *
Last run 2026-10-02 with OpenTofu v1.12.6 against hashicorp/aws 6.66.0.
Open network.tf as plain text
Open outputs.tf as plain text
Open variables.tf as plain text
Open versions.tf as plain text
Open workstation.tf as plain text
HardenedReady
evidence_bucket. The bucket evidence is read from, such as the evidence capture template's.analyst_role_arns. Roles allowed to open sessions on the workstation and attach evidence volumes to it.alert_topic_arn. SNS topic told when something on the workstation tries to connect out, or looks up a name outside AWS.
aws sts get-caller-identity
Shows the account and role you are signed in as. Check it before every apply.# terraform.tfvars evidence_bucket = "" analyst_role_arns = "" alert_topic_arn = ""
Create this file beside the others and fill in your values. Terraform reads it on its own.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform output verify
Prints the commands that prove it worked.
Formatting passedValid passedLint passed
Security scan: 110 checks passed, and none flagged.
Last run 2026-10-02 with OpenTofu v1.12.6 against hashicorp/aws 6.66.0.
Open .checkov.yml as plain text
Open guard.yml as plain text
Open main.tf as plain text
Open outputs.tf as plain text
Open variables.tf as plain text
Open versions.tf as plain text
How to check it worked
In a session on the workstation, try to reach the internet and a production address. Both fail. Listing the evidence bucket works, and writing to it is refused.
Without Standard's DNS Firewall, the workstation can still look up any name through the VPC resolver, which security groups do not filter and flow logs do not record. A sample under examination could leak data that way.
Volumes made from snapshots encrypted with a key the workstation cannot use will not attach. Grant the workstation's role that key, or copy the snapshot under one it can use.
The Amazon Linux package bucket is allowed by name in the endpoint policy. If dnf stops working, check the bucket name AWS documents for your region.
Mount evidence read-only, with -o ro,noload for ext4, or even mounting can change it.
How to undo it
terraform destroy removes the workstation, its network, and its logs. Detach and delete any evidence volumes first.
What it costs
The workstation's hourly rate while it runs, about 20 dollars a month per interface endpoint, and DNS Firewall charges per million queries.
Terraform. An isolated virtual network with a workstation reached only through Azure Bastion
What you need first
- A subscription for forensics, kept separate from production if you can, in a region that offers Bastion Developer, such as East US 2.
- The evidence storage account, such as the evidence capture template's, and User Access Administrator on it.
- An SSH public key for the analyst account.
- For Standard, an Entra group for the analysts, and EncryptionAtHost registered on the subscription.
What it creates
- A virtual network with no peering, a subnet with no default internet access, and outbound allowed to Azure Storage in the region only, through a service endpoint
- Bastion Developer, and an Ubuntu workstation with no public IP and read access to the evidence account
- A private endpoint as the only way to the evidence account, and every other connection refused in both directions (Standard)
- Bastion Standard with copy and file transfer off, encryption at host, and an analyst group that can connect (Standard)
- Flow logs with traffic analytics, and an email when the workstation tries to connect somewhere it may not (Standard)
- Six native activity log alerts, which Azure evaluates without the workspace: a flow log or diagnostic setting deleted or written, a log search rule disabled by Azure, and a lock deleted (Standard)
- A cannot-delete lock on the workspace, the flow log storage, the action group, and each alert, with the workstation left free to rebuild (Standard)
See the seven alerts this creates
The code
Quick startReady
evidence_storage_account_id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-evidence/providers/Microsoft.Storage/storageAccounts/evidence"main.tf, line 22analyst_ssh_public_key = "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAVLSNVHxwTkfF6QlOHKLaAYXoPNlChUBMMleVjJvDyi replace-me"main.tf, line 23
az login
Signs the command line tool in. Terraform uses the same sign-in.export ARM_SUBSCRIPTION_ID=$(az account show --query id -o tsv)
Tells the provider which subscription. It stopped guessing in version 4.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform destroy
When you have finished. If it refuses, How to undo it below explains why.
Formatting passedValid not runLint passed
Security scan: 24 checks passed, and none flagged.
Last run 2026-11-09 with OpenTofu v1.12.6.
Open main.tf as plain text
StandardReady
subscription_id. Subscription for the workstation and its network.evidence_storage_account_id. Resource ID of the storage account evidence is read from, such as the evidence capture template's.analyst_group_object_id. Entra group whose members may connect through Bastion. They get Reader on Bastion and on the workstation, which is what a Bastion connection needs.analyst_ssh_public_key. Public key for the analyst account on the workstation.alert_emails. Addresses told when the workstation tries to connect somewhere it may not, and when its record or alerts are changed.
az login
Signs the command line tool in. Terraform uses the same sign-in.export ARM_SUBSCRIPTION_ID=$(az account show --query id -o tsv)
Tells the provider which subscription. It stopped guessing in version 4.# terraform.tfvars subscription_id = "" evidence_storage_account_id = "" analyst_group_object_id = "" analyst_ssh_public_key = "" alert_emails = ""
Create this file beside the others and fill in your values. Terraform reads it on its own.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform output verify
Prints the commands that prove it worked.
Formatting passedValid not runLint passed
Security scan: 87 checks passed, and six rules flagged, each with a written reason:
- Storage encrypted with your own key
- Storage private endpoint
- Storage account shared key access off
- Storage replication
- Classic queue logging
- Storage public network access off
Last run 2026-11-09 with OpenTofu v1.12.6.
Open network.tf as plain text
Open outputs.tf as plain text
Open variables.tf as plain text
Open versions.tf as plain text
Open workstation.tf as plain text
HardenedReady
subscription_id. Subscription for the workstation and its network.evidence_storage_account_id. Resource ID of the storage account evidence is read from, such as the evidence capture template's.analyst_group_object_id. Entra group whose members may connect through Bastion. They get Reader on Bastion and on the workstation, which is what a Bastion connection needs.analyst_ssh_public_key. Public key for the analyst account on the workstation.alert_emails. Addresses told when the workstation tries to connect somewhere it may not, and when its record or alerts are changed.
az login
Signs the command line tool in. Terraform uses the same sign-in.export ARM_SUBSCRIPTION_ID=$(az account show --query id -o tsv)
Tells the provider which subscription. It stopped guessing in version 4.# terraform.tfvars subscription_id = "" evidence_storage_account_id = "" analyst_group_object_id = "" analyst_ssh_public_key = "" alert_emails = ""
Create this file beside the others and fill in your values. Terraform reads it on its own.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform output verify
Prints the commands that prove it worked.
Formatting passedValid not runLint passed
Security scan: 87 checks passed, and none flagged.
Last run 2026-11-09 with OpenTofu v1.12.6.
Open .checkov.yml as plain text
Open guard.yml as plain text
Open main.tf as plain text
Open outputs.tf as plain text
Open variables.tf as plain text
Open versions.tf as plain text
How to check it worked
On the workstation, a five-second request with curl to https://example.com fails, and listing the evidence with the machine's own identity succeeds. The file prints both commands; Standard prints more with terraform output verify.
Network security groups do not filter DNS to Azure's resolver, and flow logs do not record it, so a sample could leak data through lookups. Azure DNS security policy can block that; this template does not set it up.
The quick start allows the whole regional Storage service tag, which includes storage accounts you do not own. Standard narrows it to the evidence account's private endpoint.
With no internet access, apt cannot reach Ubuntu's mirrors. Build an image with your tools before an incident.
Mount evidence disks read-only, with -o ro,noload for ext4, or even mounting can change them.
The quick start's example SSH key belongs to nobody, and apply refuses to use it.
Every alert, the native ones included, emails through one action group. Locks stop the record, the action group, and the alerts being deleted, but whoever can edit the group can still disable it or change its addresses.
The locks block Terraform too. A change that replaces or removes a locked resource fails while its lock is on. Remove that lock with terraform destroy -target, then apply, and the lock returns. Its removal fires the lock alert.
Flows reach the workspace only once traffic analytics starts processing them, some time after the first apply. Run the refused-connection drill once NTANetAnalytics has rows. Azure disables a rule whose query fails for a week, and the rule-disabled alert reports it.
The diagnostic-setting-written and flow-log-written alerts fire on every such change in the subscription, other teams' changes included.
How to undo it
Remove the locks first with terraform destroy -target=azurerm_management_lock.record, or module.standard.azurerm_management_lock.record in Hardened. Then terraform destroy removes the workstation, its network, and its logs. Detach and delete any evidence disks first.
What it costs
The workstation's hourly rate while it runs. Bastion Developer is free; Standard bills by the hour. Flow logs and traffic analytics by GB.
Terraform. An isolated VPC network with no internet route, reached through Identity-Aware Proxy
What you need first
- A project where you can create networks, firewall rules, Cloud DNS zones, and VMs.
- The evidence bucket, such as the evidence capture template's.
- The analyst allowed in, as user: or group:.
What it creates
- A network created with no default internet route, a subnet with private Google access and full flow logs
- One route and a private DNS zone that send every Google API name to restricted.googleapis.com
- Firewall rules: HTTPS out to that range only, everything else refused and logged, and SSH in from IAP only
- A workstation with no external address, Shielded VM, OS Login, and read access to the evidence bucket
- IAP and admin login rights for the analyst on this workstation only, since mounting evidence needs root
- DNS that answers only Google API names, every query logged, and alerts on refused connections and outside lookups (Standard)
- Several analysts, your own tool image, and an optional disk key of your own (Standard)
See the two alerts this creates
The code
Quick startReady
project_id = "your-project-id"main.tf, line 19zone = "us-central1-a"main.tf, line 20evidence_bucket = "your-evidence-bucket"main.tf, line 21analyst = "user:you@example.com"main.tf, line 22
gcloud auth application-default login
The sign-in Terraform reads. A plain gcloud auth login is not enough.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform destroy
When you have finished. If it refuses, How to undo it below explains why.
Formatting passedValid passedLint passed
Security scan: 34 checks passed, and one rule flagged, each with a written reason:
Last run 2026-10-02 with OpenTofu v1.12.6 against hashicorp/google 8.4.0.
Open main.tf as plain text
StandardReady
project_id. A project kept for forensics. The DNS alert reads every DNS query log in it, so keep other workloads out.zone. Zone for the workstation.evidence_bucket. The bucket evidence is read from, such as the evidence capture template's.analysts. Who may open sessions and have root on the workstation, such as group:forensics@example.com.alert_emails. Addresses told when something on the workstation reaches out or looks up a name outside Google's APIs.
gcloud auth application-default login
The sign-in Terraform reads. A plain gcloud auth login is not enough.# terraform.tfvars project_id = "" zone = "" evidence_bucket = "" analysts = "" alert_emails = ""
Create this file beside the others and fill in your values. Terraform reads it on its own.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform output verify
Prints the commands that prove it worked.
Formatting passedValid passedLint passed
Security scan: 36 checks passed, and none flagged.
Last run 2026-10-02 with OpenTofu v1.12.6 against hashicorp/google 8.4.0.
Open network.tf as plain text
Open outputs.tf as plain text
Open variables.tf as plain text
Open versions.tf as plain text
Open workstation.tf as plain text
HardenedReady
project_id. A project kept for forensics. The DNS alert reads every DNS query log in it, so keep other workloads out.zone. Zone for the workstation.evidence_bucket. The bucket evidence is read from, such as the evidence capture template's.analysts. Who may open sessions and have root on the workstation, such as group:forensics@example.com.alert_emails. Addresses told when something on the workstation reaches out or looks up a name outside Google's APIs.
gcloud auth application-default login
The sign-in Terraform reads. A plain gcloud auth login is not enough.# terraform.tfvars project_id = "" zone = "" evidence_bucket = "" analysts = "" alert_emails = ""
Create this file beside the others and fill in your values. Terraform reads it on its own.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform output verify
Prints the commands that prove it worked.
Formatting passedValid passedLint passed
Security scan: 36 checks passed, and none flagged.
Last run 2026-10-02 with OpenTofu v1.12.6 against hashicorp/google 8.4.0.
Open .checkov.yml as plain text
Open guard.yml as plain text
Open main.tf as plain text
Open outputs.tf as plain text
Open variables.tf as plain text
Open versions.tf as plain text
How to check it worked
In an IAP session on the workstation, try to reach the internet. It fails. Listing the evidence bucket works.
DNS lookups go to the metadata server, which firewall rules do not cover, so in the quick start public names still resolve and a sample could leak data through lookups. Standard sends every name outside Google's APIs to a reserved address nothing answers on, and alerts on each lookup.
restricted.googleapis.com serves only the APIs VPC Service Controls supports. A tool needing another Google API will fail to reach it.
With no internet route, apt cannot reach Debian's mirrors. Bake your tools into a custom image before an incident.
Google Cloud can attach an evidence disk read-only with --mode ro, which AWS cannot. Use it, and mount with -o ro,noload as well.
With Standard DNS, internal names such as metadata.google.internal resolve only through /etc/hosts, as Google images set up. A custom image must keep that entry.
How to undo it
terraform destroy removes the workstation, its network, and its DNS zone. Detach and delete any evidence disks first.
What it costs
The workstation's hourly rate while it runs, and flow logs by volume. The network, route, and DNS zone cost little.
Terraform. An isolated VCN with no internet route, reached through a Bastion port-forwarding session
What you need first
- A compartment kept for forensics, and rights to create networks, instances, bastions, logs, and policies in it.
- Rights to create a dynamic group and policies in the tenancy.
- The evidence bucket, such as the evidence capture template's, and the analysts' SSH public keys.
What it creates
- A VCN with no internet gateway and no NAT gateway, and a private subnet that refuses public addresses
- A service gateway and one route to it, so Oracle's own services are the only thing reachable
- A security list allowing HTTPS to those services and SSH inside the subnet, and a security group letting only the bastion open a connection to the workstation
- A bastion for port-forwarding sessions from the addresses you name, and a workstation with no public address, Secure Boot, and every Oracle Cloud Agent plugin off
- A dynamic group and a policy letting the machine read one evidence bucket, and nothing else
- Flow logs on the subnet with a capture filter that keeps every flow, a metric counting the refused ones, and an alarm that emails on them (Standard)
See the one alert this creates
The code
Quick startReady
tenancy_ocid = "ocid1.tenancy.oc1..replace-me"main.tf, line 28compartment_ocid = "ocid1.compartment.oc1..replace-me"main.tf, line 29region = "us-ashburn-1"main.tf, line 30evidence_bucket = "your-evidence-bucket"main.tf, line 31analyst_ssh_key = "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAVLSNVHxwTkfF6QlOHKLaAYXoPNlChUBMMleVjJvDyi replace-me"main.tf, line 32analyst_cidr = "203.0.113.0/24"main.tf, line 33
oci os ns get
Prints your Object Storage namespace, which proves ~/.oci/config works.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform output verify
Prints the commands that prove it worked.terraform destroy
When you have finished. If it refuses, How to undo it below explains why.
Formatting passedValid passedLint passed
Security scan: five checks passed, and five rules flagged, each with a written reason:
- VCN has an inbound security list
- Security list restricts SSH from 0.0.0.0/0
- Network security group ingress rules are stateless
- Compute instance boot volume in-transit encryption
- Compute instance monitoring enabled
Last run 2026-11-09 with OpenTofu v1.12.6 against oracle/oci 9.8.0.
Open main.tf as plain text
StandardReady
tenancy_ocid. The tenancy. The dynamic group and its policies live here.compartment_ocid. A compartment kept for forensics. Keep other workloads out, because the alerts read every flow log and DNS query in it.region. Region identifier, such as us-ashburn-1.evidence_bucket. The bucket evidence is read from, such as the evidence capture template's.analyst_ssh_keys. Public keys of the analysts who may log in. The bastion injects nothing, so a key that is not here cannot get in.analyst_cidrs. Addresses analysts open sessions from, such as your VPN egress. Everything else is refused by the bastion.alert_emails. Addresses told when the workstation tries to reach something the rules refuse. Each must confirm the subscription once.
oci os ns get
Prints your Object Storage namespace, which proves ~/.oci/config works.# terraform.tfvars tenancy_ocid = "" compartment_ocid = "" region = "" evidence_bucket = "" analyst_ssh_keys = "" analyst_cidrs = "" alert_emails = ""
Create this file beside the others and fill in your values. Terraform reads it on its own.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform output verify
Prints the commands that prove it worked.
Formatting passedValid passedLint passed
Security scan: five checks passed, and five rules flagged, each with a written reason:
- VCN has an inbound security list
- Security list restricts SSH from 0.0.0.0/0
- Network security group ingress rules are stateless
- Compute instance boot volume in-transit encryption
- Compute instance monitoring enabled
Last run 2026-11-09 with OpenTofu v1.12.6 against oracle/oci 9.8.0.
Open network.tf as plain text
Open outputs.tf as plain text
Open variables.tf as plain text
Open versions.tf as plain text
Open workstation.tf as plain text
HardenedReady
tenancy_ocid. The tenancy. The dynamic group and its policies live here.compartment_ocid. A compartment kept for forensics. Keep other workloads out, because the alerts read every flow log and DNS query in it.region. Region identifier, such as us-ashburn-1.evidence_bucket. The bucket evidence is read from, such as the evidence capture template's.analyst_ssh_keys. Public keys of the analysts who may log in. The bastion injects nothing, so a key that is not here cannot get in.analyst_cidrs. Addresses analysts open sessions from, such as your VPN egress. Everything else is refused by the bastion.alert_emails. Addresses told when the workstation tries to reach something the rules refuse. Each must confirm the subscription once.
oci os ns get
Prints your Object Storage namespace, which proves ~/.oci/config works.# terraform.tfvars tenancy_ocid = "" compartment_ocid = "" region = "" evidence_bucket = "" analyst_ssh_keys = "" analyst_cidrs = "" alert_emails = ""
Create this file beside the others and fill in your values. Terraform reads it on its own.terraform init
Downloads the provider. Run it once per folder.terraform plan
Shows what will be created. Changes nothing. Read it.terraform apply
Shows the plan again and waits for you to type yes.terraform output verify
Prints the commands that prove it worked.
Formatting passedValid passedLint passed
Security scan: five checks passed, and none flagged.
Last run 2026-11-09 with OpenTofu v1.12.6 against oracle/oci 9.8.0.
Open .checkov.yml as plain text
Open guard.yml as plain text
Open main.tf as plain text
Open outputs.tf as plain text
Open variables.tf as plain text
Open versions.tf as plain text
How to check it worked
In a session on the workstation, try to reach the internet. It times out. Listing the evidence bucket works, and writing to it is refused. At Standard, confirm the subscription email first; the refused connection then emails within minutes. Oracle's own services stay reachable, which the template page explains.
Oracle's resolver answers public names for instances with no internet access, by design, so a sample under examination can carry data out in a name lookup. Turn on Query Response Logs for the VCN's private resolver in the Console and watch for queries answered from the internet. The service and category strings Terraform would need are not in Oracle's documentation; oci logging service list --all prints them for your tenancy. Pointing the subnet's DHCP options at a custom resolver closes the lookups, and closes the evidence bucket's own name with them.
A service gateway takes one service CIDR label. Object Storage alone would be narrower. An instance principal has to reach the identity service to turn its certificate into a token, and that address sits outside the Object Storage label. A bastion needs the gateway too. So the whole Oracle Services Network is reachable on 443, Object Storage in any tenancy included. A pre-authenticated request carries no credentials, so anything running here can put a file in a stranger's bucket. The rules allow that traffic, so no alert fires on it.
Security lists and network security groups only allow traffic; neither can deny it. What is refused here is refused because nothing allows it and no route exists. The alarm follows the same line: it fires on traffic the rules turned away, and says nothing about traffic they allow.
Deleting the notification topic or the connector's policy stops the alarm, and so does moving the connector to another compartment. Nothing reports it. The daily drift plan in Hardened is what notices.
The Oracle Cloud Agent is off, so managed SSH cannot work and neither can Run Command. Sessions are port forwarding, and the only keys that open the machine are the ones in analyst_ssh_keys.
Shielded instances do not support custom images, so the tools have to be installed another way. With no route to a package mirror, bring them in through the evidence bucket.
A volume attached read-only stays read-only until every attachment is gone. That is the point, and it also means you cannot flip one to read-write in place. Mount an ext4 image with noload, or the mount replays the journal, which is a write, and the attachment refuses it.
How to undo it
terraform destroy removes the workstation, its network, the bastion, and the policies. Detach and delete any evidence volumes first, because a volume still attached keeps the instance from being destroyed.
What it costs
The workstation's hourly rate while it runs, flow logs by volume, and the bastion, which bills nothing while idle.
Good to know
- Malware under examination may try to call home. On this workstation that attempt is refused, and at Standard it becomes an alert and a lead.
- Evidence comes in through snapshots and the evidence bucket, and nothing goes out. Findings leave through the analyst's own session, never through a copy tool on the machine.