elastic / elastic/integrations

[AWS] Clarify the role of "Default AWS Region"

Open
#12,749 5 comments 0 reactions 1 assignee Claimed by @zmoog View on GitHub
documentation Integration:aws Stalled Team:obs-ds-hosted-services
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
3d 4h
Merged PRs (30d)
209

Description

The AWS package allows for collecting logs & metrics from a rich selection of AWS services.

All integrations in the package share the global settings (access/secret keys, role, region, etc) to access the AWS API using the AWS SDK.

The "Default AWS Region" is essential in one of these settings. Its behavior is documented in the package UI (see screenshot below), but it does not have a dedicated space in the AWS package [docs](https://www.elastic.co/guide/en/integrations/current/aws.html).

The use of `us-east-1` as the default region creates authentication issues that are hard to troubleshoot when users deploy the Elastic Agent on AWS partitions like `aws-us-gov` or `aws-cn`.

We need to:

- Review the current package information on the UI and docs.
- Identify the gaps we need to address.
- Make changes to improve the OOTB user experience, including users from `aws-us-gov`, `aws-cn`, and other existing partitions.

![Image](https://github.com/user-attachments/assets/0a08db79-ada4-4d35-a58a-33f0d64511bb)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.