18:28:28 containerd: starting signal loop
18:28:28 control-01 systemd-logind[18691]: New session 677 of user martin.
18:28:28 kubelet: Back-off restarting failed container api in pod prod/auth-service-58d6c4cd6f
18:28:28 ip-10-0-2-44 CRON[6621]: pam_unix(cron:session): session opened for user martin(uid=1000)
18:28:28 bastion-01 dhclient: bound to 10.0.3.145 -- renewal in 3211 seconds.
18:28:28 dockerd: container a1c5c817f6aa health_status: healthy (name=api-gateway-7c4f6b9d8b)
18:28:28 github-actions: ✓ deploy:staging completed in 453s
18:28:28 HPA: New size: 8; reason: cpu resource utilization (percentage of request) above target
18:28:28 ip-10-0-4-21 CRON[24956]: pam_unix(cron:session): session opened for user martin(uid=1000)
{"t":"2026-05-14 18:28:28.868","level":"error","svc":"billing","msg":"upstream timeout","upstream":"payments","dur_ms":5632,"trace_id":"a4c31dc87dd04910"}
18:28:28 cloud-init: finished at 2026-05-14 18:28:28.868. Up 30.14 seconds
18:28:28 kubelet: pod staging/metrics-relay-7fdb59c879 ready in 9.6s
18:28:28 HPA: New size: 11; reason: cpu resource utilization (percentage of request) above target
18:28:28 worker-03 kernel: [215689.034598] TCP: request_sock_TCP: Possible SYN flooding on port 443. Sending cookies.
18:28:28 control-01 systemd[1]: Started Session 5984 of user martin.
18:28:28 amazon-ssm-agent: ssm-document-worker - executing command on instance i-02ff428b7ae50903
18:28:28 argocd: app "ades/api" synced (revision 9531f65)
18:28:28 kubelet: Liveness probe failed: HTTP probe failed with statuscode: 503
18:28:28 amazon-ssm-agent: ssm-document-worker - executing command on instance i-0197a2fb6285d448
18:28:28 containerd: starting signal loop
18:28:28 kubelet: Back-off restarting failed container sidecar in pod kube-system/payments-6c8d97f5b6
18:28:28 cloud-init: finished at 2026-05-14 18:28:28.868. Up 28.49 seconds
18:28:28 ip-10-0-6-118 cron[20918]: (martin) CMD (/usr/local/bin/backup.sh --incremental)
18:28:28 containerd: PullImage "docker.io/library/postgres:16.1" returns image reference "sha256:c211f0592761..."
18:28:28 kube-proxy: Adding new service port "ingress/svc:http" at 10.0.7.91:8865/TCP
18:28:28 control-01 systemd[1]: Reached target network-online.target.
18:28:28 github-actions: ✓ test completed in 402s
18:28:28 bastion-01 cron[21127]: (martin) CMD (/usr/local/bin/backup.sh --incremental)
18:28:28 wazuh: rule 5710 fired - sshd: Attempt to login using a non-existent user from 218.194.79.111
18:28:28 kube-proxy: Adding new service port "ingress/svc:http" at 10.0.0.250:8789/TCP
18:28:28 sentinelone: agent heartbeat ok (184 threats blocked this week)
18:28:28 wazuh: rule 5710 fired - sshd: Attempt to login using a non-existent user from 82.53.98.247
18:28:28 ip-10-0-4-21 systemd[1]: Reached target timers.target.
18:28:28 kube-scheduler: Successfully bound ingress/metrics-relay-7fdb59c879 to worker-2
18:28:28 worker-03 kernel: [624471.363658] TCP: request_sock_TCP: Possible SYN flooding on port 443. Sending cookies.
{"t":"2026-05-14 18:28:28.869","level":"info","svc":"api-gateway","msg":"request","method":"GET","path":"/v1/users","status":200,"dur_ms":23,"req_id":"51f439d785ff"}
18:28:28 bastion-01 systemd[1]: Reached target multi-user.target.
18:28:28 containerd: starting signal loop
18:28:28 github-actions: ✓ build completed in 45s
18:28:28 ip-10-0-4-21 CRON[29181]: pam_unix(cron:session): session opened for user martin(uid=1000)
18:28:28 kubelet: pod monitoring/notif-dispatcher-66cbf9d6f8 ready in 5.3s
18:28:28 ip-10-0-4-21 kernel: [321973.542461] eth0: link up, 10000Mbps, full-duplex, lpa 0x7800
18:28:28 control-01 audit: type=1400 audit(1778783308.869:8891): apparmor="ALLOWED" operation="exec" profile="docker-default"
{"t":"2026-05-14 18:28:28.869","level":"warn","svc":"auth","msg":"token near expiry","sub":"u_cfdf267b","ttl_s":59}
{"t":"2026-05-14 18:28:28.869","level":"info","svc":"api-gateway","msg":"request","method":"GET","path":"/v1/health","status":200,"dur_ms":26,"req_id":"c547132a8e38"}
18:28:28 kube-scheduler: Successfully bound monitoring/auth-service-58d6c4cd6f to worker-7
18:28:28 github-actions: ✓ test completed in 236s
18:28:28 bastion-01 cron[9614]: (martin) CMD (/usr/local/bin/backup.sh --incremental)
18:28:28 fluent-bit: [output:s3] flushed 243 records to s3://ades-logs/prod/2026-05-14/
18:28:28 bastion-01 kernel: [789764.091267] TCP: request_sock_TCP: Possible SYN flooding on port 443. Sending cookies.
18:28:28 control-01 audit: type=1400 audit(1778783308.87:7387): apparmor="ALLOWED" operation="exec" profile="docker-default"
18:28:28 bastion-01 audit: type=1400 audit(1778783308.87:2815): apparmor="ALLOWED" operation="exec" profile="docker-default"
18:28:28 amazon-ssm-agent: ssm-document-worker - executing command on instance i-0c8dc8407242ea7e
18:28:28 kubelet: pod ingress/notif-dispatcher-66cbf9d6f8 ready in 10.2s
18:28:28 ip-10-0-2-44 kernel: [894686.599556] eth0: link up, 10000Mbps, full-duplex, lpa 0x7800
18:28:28 ip-10-0-4-21 NetworkManager: <info> [1778783308.87] device (eth0): state change: activated -> deactivating (reason 'connection-removed')
18:28:28 sentinelone: agent heartbeat ok (89 threats blocked this week)
18:28:28 ip-10-0-4-21 CRON[18147]: pam_unix(cron:session): session opened for user martin(uid=1000)
18:28:28 containerd: starting signal loop
18:28:28 ip-10-0-6-118 kernel: [381900.734371] TCP: request_sock_TCP: Possible SYN flooding on port 443. Sending cookies.