netplan VS amazon-ssm-agent

For Netplan-based stuff, this looks similar:

* https://github.com/canonical/netplan/blob/main/examples/dire...

I recently had to switch ISPs to one that doesn't do IPv6 for FTTH (but their smart offerings are (AFAICT) IPv6-only), but my previous IPv6 did, and activating it for my home network was a couple clicks on my Asus router.

I'm not sure how far back you want to go, but you can install the ifupdown package and remove netplan.io. But, even in Ubuntu 16, they were starting to phase it out. So, you're going to hit some bugs here.

I was working with my Ubuntu 22.04 server and configuring my network with Netplan. After executing the Netplan apply command, I got an error message like the following:

Doesn't Ubuntu server use netplan.io by default?

The interfaces on omv are managed by netplan. https://netplan.io/

This is because Ubuntu Desktop uses NetworkManager to manage all the network interfaces by default. It is the application responsible for network management via UI. This is not the case in Ubuntu Server which I will be using. The documentation can be found here NetworkManager It can be completely turned off by choosing a different renderer or a specific networking interface can be excluded from under management of NetworkManager. The configuration is in the file /etc/NetworkManager/NetworkManager.conf. On UI less versions like Ubuntu Server there is no NetworkManager installed. The default network renderer is systemd-networkd. In both flavours of Ubuntu the networking configuration is done via Netplan and the configuration for Netplan is stored in yaml file in the location /etc/netplan/*.yaml. There could be more than one configuration file. More information on this are to be found in the provided link.

nautilus-extension-gnome-terminal nautilus-gtkhash nautilus-sendto nemo-fileroller neofetch net-tools netcat-openbsd netplan.io network-manager network-manager-config-connectivity-ubuntu network-manager-gnome

https://netplan.io/, yes?

Don't overlook SSM <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/session-...> which doesn't require sshd nor public access to get onto a machine and one can opt in to a bunch of audit logging if that's your jam. It's just a small bonus that one can also hop onto an instance from the AWS Console when using SSM, since it is websocket based and not "ssh from the browser"

The agent is Apache 2 if one wanted to build, enhance, or audit what it does: https://github.com/aws/amazon-ssm-agent#readme as is the local binary that awscli uses for the websocket handshaking: https://github.com/aws/session-manager-plugin#readme

There’s no toggle for it as RunShellScript is hard coded to use the sh shell in the agent source code. However you can modify your script to check if it’s running bash and if it’s not then re-execute with bash. See this feature request for a shell toggle, with example code. https://github.com/aws/amazon-ssm-agent/issues/46

Java tends to be the default language outside of specific use cases where other languages fit better, e.g. on-host agents like the SSM agent will be written in something like Go because it's compiled and hence easier to distribute. But server code typically is Java.

... ... Ping ECS Agent registered successfully! Container instance arn: "arn:aws:ecs:eu-west-1:704533066374:container-instance/ecs-anywhere-ec2-mydcecsclusterBB109425-r7l2mKClssuV/8dfb8700d9a1460dad403a321db6b5b9" You can check your ECS cluster here https://console.aws.amazon.com/ecs/home?region=eu-west-1#/clusters/ecs-anywhere-ec2-mydcecsclusterBB109425-r7l2mKClssuV # ok ########################## ########################## This script installed three open source packages that all use Apache License 2.0. You can view their license information here: - ECS Agent https://github.com/aws/amazon-ecs-agent/blob/master/LICENSE - SSM Agent https://github.com/aws/amazon-ssm-agent/blob/master/LICENSE - Docker engine https://github.com/moby/moby/blob/master/LICENSE ##########################