| 6 May 2024 |
|  @nick_kadutskyi:matrix.org changed their display name from nick_kadutskyi to nickkadutskyi. | 17:33:29 |
| @nick_kadutskyi:matrix.org left the room. | 17:35:40 |
| 13 May 2024 |
 Arian | SSM agent will be available in 24.05 | 17:40:02 |
| Arian | EIC is planned but the EIC code is terribly unportable | 18:21:52 |
| Arian | https://github.com/NixOS/amis/pull/114 | 18:22:04 |
| Arian | * SSM agent will be enabled by default in 24.05 | 18:22:27 |
| 22 May 2024 |
|  NixOS Moderation Botchanged room power levels. | 15:25:51 |
| NixOS Moderation Botchanged room power levels. | 15:28:06 |
| 23 May 2024 |
| Arian | the 24.05beta AMIs are being uploaded as we speak. Please give them a try | 09:20:28 |
|  samrose joined the room. | 20:11:34 |
| 27 May 2024 |
|  Harrison Katz joined the room. | 15:07:23 |
| Harrison Katz | Hello! Arian We're trying to debug that AMI networking issue from Friday. If you're online today and would like to chat back and forth we would be much appreciative. I'll also be online tomorrow (or any day this week) to chat. Thanks! | 15:08:22 |
| 30 May 2024 |
|  o1lo0lol1o joined the room. | 14:54:06 |
| o1lo0lol1o | What's the recommended way to get journald logs to cloudwatch? | 14:54:32 |
| Arian | I can tell you what we do at work | 15:34:19 |
| Arian | We use fluent-bit with the following config:
[INPUT]
name systemd
tag journald
[FILTER]
name aws
match journald
imds_version v2
account_id true
[OUTPUT]
name cloudwatch_logs
match journald
region us-east-1
log_group_name /ec2/logs
log_stream_template $ec2_instance_id
log_stream_name default
auto_create_group true
| 15:37:03 |
| Arian | There is no fluent-bit NixOS module yet. We have one internally. | 15:37:17 |
| Arian | * We use fluent-bit with the following config:
[INPUT]
name systemd
tag journald
[FILTER]
name aws
match journald
imds_version v2
account_id true
[OUTPUT]
name cloudwatch_logs
match journald
region us-east-1
log_group_name /ec2/logs
log_stream_template $ec2_instance_id
auto_create_group true
| 15:39:07 |
| Arian | * We use fluent-bit with the following config:
[INPUT]
name systemd
tag journald
db ''${STATE_DIRECTORY}/journald.db
[FILTER]
name aws
match journald
imds_version v2
account_id true
[OUTPUT]
name cloudwatch_logs
match journald
region us-east-1
log_group_name /ec2/logs
log_stream_template $ec2_instance_id
log_stream_name default
auto_create_group true
| 15:42:13 |
| Arian | I can recommend it. zero issues so far :) | 15:44:11 |
| o1lo0lol1o | So you just made a systemd service that runs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/misc/fluent-bit/default.nix | 15:52:39 |
| o1lo0lol1o | Where does that config go? | 15:52:50 |
| Arian | pass it as —config_file option to the fluent-bit binary
| 16:05:18 |
| 5 Jun 2024 |
|  reepicheep42 joined the room. | 20:26:06 |
| 11 Jun 2024 |
|  TimekillerTK joined the room. | 09:56:16 |
| 22 Jun 2024 |
|  gkdr joined the room. | 16:21:37 |
| gkdr | Redacted or Malformed Event | 16:22:32 |
| 28 Jun 2024 |
 @AleXoundOS:matrix.org | Encountered a situation, when userdata script did not start:
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal systemd[1]: Reached target Multi-User System.
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal systemd[1]: Starting Reconfigure the system from EC2 userdata on startup...
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal amazon-init-start[978]: attempting to fetch configuration from EC2 user data...
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal amazon-init-start[978]: /nix/store/gzx4ihb8hdxl1yj18kfhm5an6vvz59mn-unit-script-amazon-init-start/bin/amazon-init-start: line 16: /etc/ec2-metadata/user-data: No such file or directory
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal amazon-init-start[978]: no user data is available
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal systemd[1]: Finished Reconfigure the system from EC2 userdata on startup.
But with manualy reboot it worked:
Jun 28 11:40:34 ip-10-0-96-47.eu-central-1.compute.internal systemd[1]: Reached target Multi-User System.
Jun 28 11:40:34 ip-10-0-96-47.eu-central-1.compute.internal systemd[1]: Starting Reconfigure the system from EC2 userdata on startup...
Jun 28 11:40:34 ip-10-0-96-47.eu-central-1.compute.internal amazon-init-start[934]: attempting to fetch configuration from EC2 user data...
Jun 28 11:40:34 ip-10-0-96-47.eu-central-1.compute.internal amazon-init-start[934]: running EC2 User Data bootstrap
| 11:44:48 |
| @AleXoundOS:matrix.org | * Encountered a situation, when userdata script did not start:
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal systemd[1]: Reached target Multi-User System.
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal systemd[1]: Starting Reconfigure the system from EC2 userdata on startup...
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal amazon-init-start[978]: attempting to fetch configuration from EC2 user data...
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal amazon-init-start[978]: /nix/store/gzx4ihb8hdxl1yj18kfhm5an6vvz59mn-unit-script-amazon-init-start/bin/amazon-init-start: line 16: /etc/ec2-metadata/user-data: No such file or directory
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal amazon-init-start[978]: no user data is available
Jun 28 11:34:56 ip-10-0-96-47.eu-central-1.compute.internal systemd[1]: Finished Reconfigure the system from EC2 userdata on startup.
But with manual reboot it worked:
Jun 28 11:40:34 ip-10-0-96-47.eu-central-1.compute.internal systemd[1]: Reached target Multi-User System.
Jun 28 11:40:34 ip-10-0-96-47.eu-central-1.compute.internal systemd[1]: Starting Reconfigure the system from EC2 userdata on startup...
Jun 28 11:40:34 ip-10-0-96-47.eu-central-1.compute.internal amazon-init-start[934]: attempting to fetch configuration from EC2 user data...
Jun 28 11:40:34 ip-10-0-96-47.eu-central-1.compute.internal amazon-init-start[934]: running EC2 User Data bootstrap
| 11:45:15 |
| @AleXoundOS:matrix.org | It happened only for the first time among ~100 boots. | 11:46:10 |
