On the integration doc page https://www.elastic.co/docs/current/integrations/aws#api-requests, address the following feedback:

"if we rely on that table to explain the costs associated monitoring then I think we need an new issue to ensure that the table is complete. When reading invocation logs, this integration may rely on SQS depending on configuration settings. The table doesn't account for SQS API costs related to reading S3 notifications (i.e. sqs:ReceiveMessage, sqs:DeleteMessage, sqs:ChangeMessageVisibility)."

CC @andrewkroh