This issue is to track the investigation work on using localstack to mock and test AWS metricbeat module and filebeat module.
Right now in metricbeat and filebeat, we have integration tests for aws module, which requires CI to have certain AWS credentials in order to run them. Or developers can run these integration tests locally with required AWS credentials. Since we don't have the credentials in CI right now, the integration tests do not run currently when PRs are created in Beats repo. If one day we do decide to add AWS credentials into CI environment, it will be very expensive potentially to run these integrations tests for each PR.
LocalStack provides an easy-to-use test/mocking framework for developing Cloud applications. It spins up a testing environment on your local machine that provides the same functionality and APIs as the real AWS cloud environment. Please see https://localstack.cloud and https://github.com/localstack/localstack for more details.
This issue is to track the investigation work on using localstack to mock and test AWS metricbeat module and filebeat module.
Right now in metricbeat and filebeat, we have integration tests for aws module, which requires CI to have certain AWS credentials in order to run them. Or developers can run these integration tests locally with required AWS credentials. Since we don't have the credentials in CI right now, the integration tests do not run currently when PRs are created in Beats repo. If one day we do decide to add AWS credentials into CI environment, it will be very expensive potentially to run these integrations tests for each PR.
LocalStack provides an easy-to-use test/mocking framework for developing Cloud applications. It spins up a testing environment on your local machine that provides the same functionality and APIs as the real AWS cloud environment. Please see https://localstack.cloud and https://github.com/localstack/localstack for more details.