Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow s3 bucket for audit sessions and dynamodb to exist in different regions #2007

Closed
darend opened this issue Jun 12, 2018 · 3 comments
Closed

Allow s3 bucket for audit sessions and dynamodb to exist in different regions #2007

darend opened this issue Jun 12, 2018 · 3 comments
Assignees
@kontsevoy
Labels
documentation
Milestone
3.1.6 "West Village"

Comments

@darend
Copy link
Contributor

darend commented Jun 12, 2018

Currently when you use s3 for audit sessions and dynamodb for storage, they must exist in the same region. Supporting them existing in different regions would allow for more flexibility in how the resources are deployed.

For example: you may want to create a shared bucket in an account and have all your teleport clusters store their sessions within it without forcing everything to be exist in the same region.
@kontsevoy kontsevoy added the feature-request Used for new features in Teleport, improvements to current should be #enhancements label Jun 25, 2018
@klizhentas klizhentas added this to the 3.1.6 "West Village" milestone Feb 9, 2019
klizhentas added a commit that referenced this issue Feb 9, 2019
@klizhentas
Allow S3 buckets in different regions, implements #2007
cf7766b 
This commit allows additional configuration
for the `audit_sessions_uri` parameter:

`audit_sessions_uri: s3://example.com/path?region=us-east-1`

Additional query parameter `region` will override
default `audit` section `region` if set.
@klizhentas klizhentas added documentation and removed feature-request Used for new features in Teleport, improvements to current should be #enhancements labels Feb 9, 2019
@klizhentas
Copy link
Contributor

I've added additional configuration
for the audit_sessions_uri parameter:

audit_sessions_uri: s3://example.com/path?region=us-east-1

Additional query parameter region will override
default audit section region if set.

@klizhentas
Copy link
Contributor

Also it's worth documenting that path is possible to set, so sessions will be located in a separate path.

@kontsevoy
Copy link
Contributor

LGTM

klizhentas added a commit that referenced this issue Feb 10, 2019
@klizhentas
Allow S3 buckets in different regions, implements #2007
4fa988a 
This commit allows additional configuration
for the `audit_sessions_uri` parameter:

`audit_sessions_uri: s3://example.com/path?region=us-east-1`

Additional query parameter `region` will override
default `audit` section `region` if set.
klizhentas added a commit that referenced this issue Feb 10, 2019
@klizhentas
Allow S3 buckets in different regions, implements #2007
f4635de 
This commit allows additional configuration
for the `audit_sessions_uri` parameter:

`audit_sessions_uri: s3://example.com/path?region=us-east-1`

Additional query parameter `region` will override
default `audit` section `region` if set.
kontsevoy added a commit that referenced this issue Feb 14, 2019
@kontsevoy
Documented the new region argument to AWS S3
425e583 
Closes #2007
@kontsevoy kontsevoy mentioned this issue Feb 14, 2019
Merged
kontsevoy added a commit that referenced this issue Feb 14, 2019
@kontsevoy
Documented the new region argument to AWS S3
cbe179d 
Closes #2007
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kontsevoy kontsevoy

Labels
documentation
Projects
None yet
Milestone
3.1.6 "West Village"
Development

No branches or pull requests
3 participants
@klizhentas @kontsevoy @darend