Guide / What's new

What's new

What changed in each release since v0.1.0, newest first. The full notes and binaries are on the releases page. The installer always fetches the latest release, so re-running it upgrades you.

v0.1.5

C copies operational commands, not just the read one

C used to copy one thing: the read-only describe command for the selected resource. Where there is more than one useful command, it now opens a picker in three tiers:

These are available on EC2 instances, ECS services and tasks, Auto Scaling groups and EKS clusters. The picker shows the exact command before you copy it, with --region, --profile and --endpoint-url (when you’re pointed at an emulator) filled in. A resource with only one command still copies it straight away.

neboto still only copies these commands and never runs them. It makes no new API calls and needs no new permissions, so the read-only guarantee is unchanged. A few rules keep a careless paste safe:

• Nothing destructive. No terminate, delete, purge or deregister commands.
• Value-taking commands are prefilled with the current value. Pasting update-service --desired-count or set-desired-capacity without editing it changes nothing.
• Change rows are disabled while you’re assumed into a member account. A --profile flag can’t reproduce that session, so a pasted change would run as the wrong identity.
• Visual selection batches. Select several instances with V in the list and C offers the commands they share, with every id merged into one --instance-ids a b c list.

C also works from the detail pane now. Before this release, pressing it there did nothing.

EC2: which load balancers hold this instance

An instance’s detail pane has a new Load Balancing section (key 4). It answers “is this instance behind a load balancer, and is it healthy there?” AWS has no API that answers this directly, so neboto checks the target groups in the same VPC with DescribeTargetHealth. For an instance in an Auto Scaling group, it checks the group’s own target groups first. Each row shows the health state and reason, port, and zone. The target group and load balancer ARNs are links you can follow with Enter.

The network access lens (N) now labels rules whose source is a load balancer’s security group (sg-… ⇠ ALB web-alb). That tells ports forwarded by the load balancer apart from ports opened to the instance directly.

The instance’s later section keys moved up one: Storage 5, User Data 6, Console 7, Tags 8, Optimizer 9. Bookmarks restore by section name, so existing ones still land in the right place.

v0.1.4

Route 53: hosted zone tags

Every hosted zone’s Tags section read “No tags”, whatever the zone was actually tagged with. Zone tags are now loaded with the list, so they also feed the ownership line, tag: search filters, U and exports. If the tag call is refused, the error shows in the Tags section instead of looking like an untagged zone.

Route 53: readable record sets

A zone’s Records section now shows names relative to the zone (@ for the apex, www, *.dev) and puts the record type first:

A      @      192.0.2.10 · 300
CNAME  www    example.com · 300
TXT    @      "v=spf1 -all" · 3600

Before, the type and TTL were cut off every row. Enter on a record opens its own pane, where every value is on its own untruncated line, and alias targets and health checks can be followed.

v0.1.3

EC2: the instance console log

A new Console section on the instance pane shows the system log (the console’s Get system log). Check it first when an instance fails its status checks or never registers with SSM. e opens the whole buffer in $EDITOR as a plain .log file, easy to grep for a kernel error. e on User Data likewise opens the script itself, with a .sh or .yaml extension to match its first line.

AWS posts the log a few minutes after the instance starts or stops, so an empty section right after launch is expected, not an error. The call is ec2:GetConsoleOutput, which ReadOnlyAccess already includes.

v0.1.2

Route 53 Resolver: DNS delegation and endpoint detail

Resolver endpoints and rules now show the newer features: the inbound-delegation endpoint type and DELEGATE rules, IPv6 targets and DNS-over-HTTPS protocols. Endpoint panes gain type, protocols and feature flags. They also get a Rules section listing the loaded rules routed through the endpoint. Three display bugs are fixed: DELEGATE rules showed as system rules, IPv6-only targets showed as a bare :53, and O on an outbound endpoint opened the inbound page in the Console.

v0.1.1

Profile switch with access keys exported

With AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY in the environment, P, -p and default_profile showed the new profile’s name but kept signing every call with the exported keys. A profile you choose explicitly now wins, the same way it does with aws --profile.

Coming soon: nebaz, for Azure

nebaz is neboto’s Azure sibling and is in active development. It uses the same keyboard-driven, read-only design on the same core: fuzzy search, detail panes with links you can follow, visual selection, macros, bookmarks, export and themes. It authenticates through the Azure CLI (az login).

It already covers subscriptions and resource groups, Virtual Machines, Storage, Networking, Key Vault (names and metadata, never secret values), AKS, managed identities, App Service, SQL, Container Registry, Cosmos DB and Foundry. There is no release yet. Follow or star the repository to hear when there is. Its guide will live here at neboto.dev/azure.