HEX
Server: Apache
System: Linux server1.panigaletech.com 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64
User: www-data (33)
PHP: 7.4.30
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
Upload Files
File: //usr/lib/python3/dist-packages/awscli/examples/logs/put-log-events.rst
The following command puts log events to a log stream named ``20150601`` in the log group ``my-logs``::

  aws logs put-log-events --log-group-name my-logs --log-stream-name 20150601 --log-events file://events

Output::

  {
      "nextSequenceToken": "49542672486831074009579604567656788214806863282469607346"
  }

The above example reads a JSON array of events from a file named ``events`` in the current directory::

  [
    {
      "timestamp": 1433190184356,
      "message": "Example Event 1"
    },
    {
      "timestamp": 1433190184358,
      "message": "Example Event 2"
    },
    {
      "timestamp": 1433190184360,
      "message": "Example Event 3"
    }
  ]

Each subsequent call requires the next sequence token provided by the previous call to be specified with the sequence token option::

  aws logs put-log-events --log-group-name my-logs --log-stream-name 20150601 --log-events file://events2 --sequence-token "49542672486831074009579604567656788214806863282469607346"

Output::

  {
      "nextSequenceToken": "49542672486831074009579604567900991230369019956308219826"
  }