Skip to content

Document reasoning about aws region #105

Description

@dkropachev

Jira task: https://scylladb.atlassian.net/browse/DRIVER-669
Jira epic: https://scylladb.atlassian.net/browse/DRIVER-27

Copied from Jira epic DRIVER-27:

There is a problem that we provide bogus AWS region name to the aws client.

If client have tracing/debuging or anything else that looks at aws region it can create confusion or missbehavior.

We need to document reasoning behind bogus AWS region and a way to set it properly.

Example case: https://github.com/scylladb/alternator-load-balancing/issues/30

Migrated from GitHub issue: scylladb/alternator-load-balancing#32

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions