S3 Support #91

sjperkins · 2023-03-31T16:54:29Z

Closes #46

TODO

General KVstore

AWS4 signature calculation
ReadTask implemented
WriteTask implementd
DeleteTask implemented
ListTask implemented
Versioned Bucket support
Requester Pays
S3 specific rate-limiting (per endpoint?):

Testing

TestKeyValueStoreBasicFunctionality passes
Use localstack for S3 mocking
Install localstack in github actions
Benchmarking See S3 Support #91 (comment)
...

Authorisation

Credentials from Environment Variables
Credentials from ~/.aws/credentials
Anonymous Access (no Authorization header if credentials empty)
Add session token to AWS4 signature headers if available
Credentials from EC2 Metadata Server
Credential refresh/timeout functionality (similar to Google Authprovider)

Documentation

rst/yml docs

Polishing

Refactor S3RequestBuilder to insert required headers automatically.
clang-format -style=google
Remove YAGNI MD5 Digester .

Python AWS4 Calculation: https://gist.github.com/sjperkins/15d3d196387cff8b6dc0dcca7f756fe8

tensorstore/kvstore/s3/signature.cc

jbms · 2023-03-31T18:02:36Z

Thanks for starting work on this!

sjperkins · 2023-04-03T09:18:48Z

S3 Key-Value Store

This describes the implementation of an S3 Key Value Store.

S3 Builder Class

As suggested in #91 (review), an S3 Builder Class should be provided.

class S3RequestBuilder {
 public:
  S3RequestBuilder(std::string_view method);
  // Replicate HttpRequestBuilder methods here
  // ...

  S3RequestBuilder & AddAwsRegion(std::string_view aws_region);
  S3RequestBuilder & AddAwsAccessKey(std::string_view aws_access_key_id);
  S3RequestBuilder & AddAwsSecretKey(std::string_view aws_secret_key);
  // Adds a X-Amz-Security-Token to Headers
  S3RequestBuilder & AddAwsSSessionToken(std::string_view aws_session_token);
  S3RequestBuilder & AddEndpointUrl(std::string_view endpoint_url);
  HttpRequest BuildRequest();

 private:
  // Based on https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html
  // derives
  // 1. Canonical Request String
  // 2. Signing String
  // 3. Signature
  // and returns the AuthorizationHeader
  std::string AuthorizationHeader();

};

Obtaining configuration variables

AWS configuration data can be obtained from multiple locations, primarily:

Configuration files ~/.aws/credentials and ~/.aws/config.
Environment variables, primarily: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, AWS_PROFILE and AWS_SESSION_TOKEN.

Environment variables take precedence over configuration files.

Python pseudo-code for deriving AWS variables

aws_profile = os.environ.get("AWS_PROFILE", "default")
aws_credentials_file = os.environ.get("AWS_SHARED_CREDENTIALS_FILE", "~/.aws/credentials")
aws_config_file = os.environ.get("AWS_CONFIG_FILE", "~/.aws/config")

# Read credentials file
credentials = ConfigParser()
credentials.read(os.path.expanduser(aws_credentials_file))
aws_access_key = credentials.get(aws_profile, "aws_access_key_id")
aws_secret_key = credentials.get(aws_profile, "aws_secret_access_key")
aws_session_token = credentials.get(aws_profile, "aws_session_token")

config = ConfigParser()
config.read(os.path.expanduser(aws_config_file))
aws_region = config.get(aws_profile, "aws_region")

aws_region = os.environ.get("AWS_REGION", aws_region)  # AWS_DEFAULT_REGION?
aws_access_key = os.environ.get("AWS_ACCESS_KEY_ID", aws_access_key)
aws_secret_access_key = os.environ.get("AWS_SECRET_ACCESS_KEY", aws_secret_access_key)
aws_session_token = os.environ("AWS_SESSION_TOKEN", aws_session_token)

Constructing S3 Endpoint URLs

As per the AWS S3 Rest Api
there are two methods for constructing S3 URLS:

Virtual hosted-Style <bucket_name>.s3.<aws_region>.amazonaws.com
Path Style s3.<aws_region>.amazonaws.com/<bucket_name>

The above patterns are specific to AWS but custom endpoints are used to access other
S3 implementations such as:

minio
ceph

Currently, there is no agreed upon environment variable for overriding the endpoint URL. Something like TENSORSTORE_S3_ENDPOINT_URL may be the best way forward here.

S3 KVStore

TBD.

TODO

S3RequestBuilder class and tests
AWS INI file config parsing and environment variable reading
S3 KVStore

Questions

It is currently the responsbility of the GCS KVstore to construct the GCS endpoint urls for reads + writes.
Should this be the responsibility of the S3 KVStore or the S3RequestBuilder class, which seems to be configured
with more information?
Will the S3 KVStore be more less a cut and paste of the GCS KVStore? If so, should common elements be factored out?
Is there a preferred c++ INI file parser that should be used? There's a list of projects here. Other likely candidates:
- https://github.com/pulzed/mINI
- https://github.com/SemaiCZE/inicpp

jbms · 2023-04-03T18:36:17Z

S3 Builder Class

Looks good.

Obtaining configuration variables

Looks good for Amazon S3 endpoints. For other endpoints we may want to rely on a ContextResource to specify where to find the credentials, e.g. name of environment variables to read or path to configuration file.

Another important source for credentials is the EC2 metadata server.

Constructing S3 Endpoint URLs

As per the AWS S3 Rest Api there are two methods for constructing S3 URLS:

Virtual hosted-Style <bucket_name>.s3.<aws_region>.amazonaws.com

Path Style s3.<aws_region>.amazonaws.com/<bucket_name>

I think we want to support the following:

When talking to the real amazon s3, it should be possible to just specify the bucket, not the region, since there is a global namespace of buckets, either using a json spec: {"driver": "s3", "bucket": "my-bucket", "path": "my-path"} or a URL: "s3://my-bucket/my-path". You can determine the region from the x-amz-bucket-region response header. Whether we use virtual host style or path style URLs to make requests does not really matter, but note that:
- If you use virtual host style, you can just use <bucket_name>.s3.amazonaws.com (no region). However, you still need to know the region in order to generate a correct signature. I think you can make an initial request without a signature in order to determine the region. If the bucket name contains dots, then I think some special curl options will need to be set to avoid certificate validation errors.
- If you use path style, you need to know the region even to make an initial request. I think you can make an initial request to the default s3.amazonaws.com endpoint to determine the region, but you should check on that.
When talking to a non-Amazon s3 server, the endpoint should be specified either in the json spec: {"driver": "s3", "bucket": "my-bucket", "endpoint": "https://my-server", "path": "my-path"} or as a URL: "s3+https://my-server/my-bucket/my-path".
We don't want to rely on specifying the endpoint via environment variable because that prevents the same program from using more than one endpoint (e.g. copying from amazon s3 to non-amazon s3 server). However, this could potentially be supported solely for testing, as with the gcs driver.

One challenge with supporting multiple endpoints is that each endpoint requires its own credentials.

It is currently the responsbility of the GCS KVstore to construct the GCS endpoint urls for reads + writes.
Should this be the responsibility of the S3 KVStore or the S3RequestBuilder class, which seems to be configured
with more information?

Probably it would make sense to keep at least most of the logic for generating urls in the kvstore, rather than S3RequestBuilder.

Will the S3 KVStore be more less a cut and paste of the GCS KVStore? If so, should common elements be factored out?

If there are some common elements that can be factored out, that would probably be good. However note that the GCS kvstore driver uses the GCS "JSON" api rather than the s3-compatible API, so it won't be that similar. The largest difference will be in supporting List, which will require parsing the XML response. Not sure if that will require an XML library or if it can be done with just regular expressions.

As far as INI library --- you might have to be aware that there are variations in format. E.g. the mINI library seems to use ; as the comment character while AWS uses #. It might be simpler to just use regular expressions to parse.

sjperkins · 2023-04-05T10:19:19Z

I think you can make an initial request to the default s3.amazonaws.com endpoint to determine the region, but you should check on that.

By inspection, the following seems to work to get the bucket region for both public and private buckets.

$ curl -sI https://<bucket_name>.amazonaws.com | grep bucket-region

This then seems to be the region to use in Signature Calculations: quoting from the example here:

The bucket is assumed to be in the US East (N. Virginia) Region. The credential Scope and the Signing Key calculations use us-east-1 as the Region specifier. For information about other Regions, see Regions and Endpoints in the AWS General Reference.

I interpret this to mean that the signature depends on the actual bucket location and that the AWS_REGION and AWS_DEFAULT_REGION in config files/environment variables should probably be ignored.

Another important source for credentials is the EC2 metadata server.

Assume this refers to the following idea:

role_name=$( curl -s http://169.254.169.254/latest/meta-data/iam/security-credentials/ )
curl -s http://169.254.169.254/latest/meta-data/iam/security-credentials/${role_name}

I assume the precedence from highest to lowest would be:

EC2 Metadata Server
Environment Variables
Credentials files

Would, for example, a 200ms connect timeout on the Metadata Server connection be sufficient for a decent user XP w.r.t. timeouts outside AWS?

One challenge with supporting multiple endpoints is that each endpoint requires its own credentials.

True, and I suspect most software just assumes a single endpoint. One way I've dealt with this in the past (in combination with fsspec) is to have the following sort of configuration in yaml:

"s3://bucket-one":
  aws_access_key_id: ...
  aws_secret_access_key: ...

"s3+https://bucket-two":
  aws_access_key_id: ...
  aws_secret_access_key: ...

and then apply the following pseudocode when handling access keys:

s3url = "s3://bucket-two/path/to/data.bin"
aws_access_key_id = "ABCDEF..."

for url_prefix, config in yaml.load("s3config.yaml").items():
  if s3url.startswith(url_prefix):
    endpoint_url = config["endpoint_url"]
    aws_access_key = config["aws_access_key_id"]
    break

It's a bit messy when combined with ~/.aws/credentials, which has separate profile sections. Perhaps we could just override variables in the json spec? For example:

{"driver": "s3", "bucket": "my-bucket", "endpoint": "https://my-server", "path": "my-path", "profile": "myprofile"}
{"driver": "s3", "bucket": "my-bucket", "endpoint": "https://my-server", "path": "my-path", "aws_access_key_id": "...", "aws_secret_access_key": "...", "aws_session_token": "..."}

As far as INI library --- you might have to be aware that there are variations in format. E.g. the mINI library seems to use ; as the comment character while AWS uses #. It might be simpler to just use regular expressions to parse.

Yes, INI is simple enough for regex. Let's hold off on the XML library decision until the XML complexity is clearer.

EDIT: Suggest placing keys for specific endpoints in the JSON spec

jbms · 2023-04-06T22:53:07Z

I assume the precedence from highest to lowest would be:

EC2 Metadata Server

Environment Variables

Credentials files

Would, for example, a 200ms connect timeout on the Metadata Server connection be sufficient for a decent user XP w.r.t. timeouts outside AWS?

I think the order should be:

Environment variables
Credentials files
Metadata server

You might check the AWS SDK to see what it does -- I expect it uses something like that order. That is also how we handle Google Cloud Storage credentials.

As far as timeout, you might check to see what the AWS SDK does by default. In most cases I expect the connection will be refused immediately if not on EC2 and the timeout doesn't matter. Essentially the only time that the timeout actually comes into play is if you have no credentials and wish to use anonymous access, and you have a network configuration such that requests to the EC2 metadata server are silently dropped rather than are refused immediately.

tensorstore/internal/path.cc

jbms · 2023-04-06T23:07:14Z

I interpret this to mean that the signature depends on the actual bucket location and that the AWS_REGION and AWS_DEFAULT_REGION in config files/environment variables should probably be ignored.

Yes I believe that is correct.

By inspection, the following seems to work to get the bucket region for both public and private buckets.

Yes, looks right. I think there is one extra complication:
https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html

Buckets created in us-east-1 prior to Mar 1, 2018 could have names that are not DNS compatible. For those, we cannot use method you described to determine the region, since they cannot be used with the virtual hosted-style requests. However, we can instead detect that the bucket name does not conform to the new rules, and infer that it must be a us-east-1 bucket.

Perhaps we could just override variables in the json spec?

Yes, that would probably make sense. In any case it probably makes sense to first implement a basic version before worrying about all of the possible extra options.

laramiel · 2023-04-07T19:56:12Z

It's a bit messy when combined with ~/.aws/credentials, which has separate profile sections. Perhaps we could just override variables in the json spec? For example:
{"driver": "s3", "bucket": "my-bucket", "endpoint": "https://my-server", "path": "my-path", "profile": "myprofile"}
{"driver": "s3", "bucket": "my-bucket", "endpoint": "https://my-server", "path": "my-path", "aws_access_key_id": "...", "aws_secret_access_key": "...", "aws_session_token": "..."}

For other drivers we've avoided setting any secrets in the spec as they become easier to leak that way. It does make sense to allow a region setting in the verbose spec, as well as profile-related directives, IMO:

{"driver": "s3", "bucket": "my-bucket", "endpoint": "https://my-server", "path": "my-path", "region": "us-east-1"}

…ure Calculations

sjperkins · 2023-04-12T15:09:20Z

Some progress on:

Validating S3 Bucket Names
Validating S3 Object Names
S3 Signature URI Encoding

A review might not be worth it at this point, but one thing that may be controversial is the move of the following:

AsciiSet
PercentEncodeReserved
IntToHexDigit
HexDigitToInt

from path.cc into ascii_utils.{h,cc}. Let me know if this doesn't work or if you want it done differently.

Other than that, I broadly plan to implement in the following order:

S3RequestBuilder (including moving functionality from the signature.{h,cc} files), along with some basic Request testing here.
Configuration management (ini files, environment variable querying, EC2 metadata querying)
S3 KVStore

These might be logical points at which reviews may be worthwhile.

tensorstore/kvstore/s3/validate.cc

jbms · 2023-04-13T00:00:32Z

Some progress on:

Validating S3 Bucket Names

Validating S3 Object Names

S3 Signature URI Encoding

A review might not be worth it at this point, but one thing that may be controversial is the move of the following:

AsciiSet

PercentEncodeReserved

IntToHexDigit

HexDigitToInt

from path.cc into ascii_utils.{h,cc}. Let me know if this doesn't work or if you want it done differently.

Moving these is fine.

Other than that, I broadly plan to implement in the following order:

S3RequestBuilder (including moving functionality from the signature.{h,cc} files), along with some basic Request testing here.

Configuration management (ini files, environment variable querying, EC2 metadata querying)

I'd suggest that you just implement the minimum here initially, e.g. getting the access key from the env var, and then work on the S3 kvstore, before worrying about more complicated methods of getting the credentials. That way you will have a workable driver sooner.

S3 KVStore

These might be logical points at which reviews may be worthwhile.

tchaton · 2023-04-13T09:12:04Z

Any ETA for this PR to land ? This is a very exciting development. Really looking to try it out when it lands.

tchaton · 2023-04-13T09:36:36Z

Hey @sjperkins,

Could you share a snippet of the Python API ?

sjperkins · 2023-04-13T11:51:29Z

Any ETA for this PR to land ? This is a very exciting development. Really looking to try it out when it lands.

Hi @tchaton. I'm not developing this full time, so I can't estimate an ETA here.

Could you share a snippet of the Python API ?

I haven't touched any Python code yet, but I'd imagine the Python interface would be very similar to the GCS key-value driver https://google.github.io/tensorstore/kvstore/gcs/index.html

tensorstore/kvstore/s3/s3_credential_provider.cc

sjperkins · 2023-07-31T08:07:42Z

A localstack fixture has been added.

Added a host variable to the S3 json spec as localstack expects <bucket>.s3.<region>.localstack.localhost.com style hosts in the HTTP Requests. This could probably do with some more thought in the context of minio/ceph for e.g. so might need to change this.
This test in the basic test suite fails on localstack, but not on S3. Haven't had time to dig into this. Might be easily fixable in localstack itself.
No localstack install on github actions yet.
Added requester payer header if set in the spec.

…s optional

sjperkins · 2023-07-31T08:10:46Z

tensorstore/kvstore/s3/s3_key_value_store_test.cc

+
+
+ABSL_FLAG(std::string, localstack_binary, "",
+          "Path to the localstack");


@laramiel I adapted this from the gcs test bench, but didn't have enough time to understand and investigate how bazel linked (and installed?) the test bench utility. Might this be possible with localstack?

Yes, see here:
https://github.com/google/tensorstore/tree/master/third_party/pypa

Add to test_requirements.txt then run generate_workspace.py

I'd probably name this s3_localstack_test, then add to the BUILD file tags = ["manual"] so it's not triggered on every bazel test ... invocation.

... also, split the tests which don't require a running localstack into a separate test.

laramiel · 2023-07-31T22:32:17Z

tensorstore/kvstore/s3/s3_credential_provider_test.cc

+ };
+
+ void SetUp() override {
+    for(auto &pair: saved_vars) {


Saving the env vars shouldn't be necessary, since they are process scoped and should not leak past test execution.

laramiel · 2023-07-31T22:39:32Z

tensorstore/kvstore/s3/s3_key_value_store_test.cc

+static constexpr char kAwsRegion[] = "af-south-1";
+static constexpr char kUriScheme[] = "s3";
+static constexpr char kDriver[] = "s3";
+static constexpr char kLocalStackEndpoint[] = "http://localhost:4566";


The endpoint should be a flag. Otherwise, if localstack were spawned from the test itself, then ideally there would be a --port argument that you could pass, and use tensorstore/internal/http/transport_test_utils.h PickUnusedPortOrDie().

laramiel · 2023-07-31T22:51:02Z

tensorstore/kvstore/s3/s3_metadata_test.cc

+namespace {
+
+/// Exemplar ListObjects v2 Response
+/// https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html#API_ListObjectsV2_ResponseSyntax


Is is possible to get the response in json format? If not, maybe we should use a small xml parser such as ... (looking around) ... tinyxml2? expat?

laramiel · 2023-07-31T23:06:55Z

tensorstore/kvstore/s3/validate.cc

+  if(absl::EndsWith(bucket, "--ol-s3")) return BucketNameType::Invalid;
+
+  // Bucket name is a series of labels split by .
+  // https://web.archive.org/web/20170121163958/http://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html


Once we're using regexes, just write the full regex. something like:

static LazyRE2 kValidBucket = { "^(([a-z0-9][a-z0-9-]*[a-z0-9])|([a-z0-9]))" "(\.(([a-z0-9][a-z0-9-]*[a-z0-9])|([a-z0-9])))*$" }; static LazyRE2 kOldValidBucket = { "^(([a-zA-Z0-9][a-zA-Z0-9_-]*[a-zA-Z0-9])|([a-zA-Z0-9]))" "(\.(([a-zA-Z0-9][a-zA-Z0-9_-]*[a-zA-Z0-9])|([a-zA-Z0-9])))*$" }; if (!RE2::FullMatch(bucket, *kOldValidBucket)) { return BucketNameType::kInvalid; } if (bucket.size() <= 63 && RE2::FullMatch(bucket, *kValidBucket)) { return BucketNameType::kStandard; } return : BucketNameType::kOldUsEast;

laramiel · 2023-09-01T19:10:00Z

I'm preparing to submit most of this in the next day or so, with some minor changes.

Includes changes for includes, style, and some fixes from the following pull request: #91 This is still a work in progress, so it is not yet available by default. To use, add a bazel dependency on //tensorstore/kvstore/s3 #46 PiperOrigin-RevId: 562068999 Change-Id: Id660a72224ef865c858484c04985f9fc4f0e3bf5

sjperkins · 2023-09-02T10:26:04Z

I'm preparing to submit most of this in the next day or so, with some minor changes.

I think this makes sense -- The PR contains core S3 functionality and further additions can be split into smaller PR's which will be easier to review.

AWS4 Authorization Signature calculation

9f3a28c

sjperkins marked this pull request as draft March 31, 2023 16:54

jbms reviewed Mar 31, 2023

View reviewed changes

tensorstore/kvstore/s3/signature.cc Outdated Show resolved Hide resolved

laramiel reviewed Apr 6, 2023

View reviewed changes

tensorstore/internal/path.cc Outdated Show resolved Hide resolved

sjperkins added 9 commits April 11, 2023 18:11

Merge branch 'master' of github.com:google/tensorstore

7aead47

Add S3 bucket name validation and classification

3fed5f2

Refactor AsciiSet and Hex conversion into separate library

288620f

Implement Bucket and Object Name validation using AsciiSet's

84ff822

Move PercentEncodeReserved into ascii_utils and use within AWS Signat…

881885a

…ure Calculations

internal_ascii_utils -> internal for consistency

1390552

Remove use of ostringstream for hex conversion

5877956

Formatting

7302fc4

Comment

ec4358c

jbms reviewed Apr 12, 2023

View reviewed changes

tensorstore/kvstore/s3/validate.cc Outdated Show resolved Hide resolved

jbms reviewed Apr 12, 2023

View reviewed changes

tensorstore/kvstore/s3/validate.cc Show resolved Hide resolved

sjperkins added 3 commits April 20, 2023 14:22

Incorporate signature calculation into S3RequestBuilder class

aed0a4c

Remove discouraged chars test

e5256ca

Replace us of AsciiSets for bucket validation with regular expressions

e1f4a59

laramiel reviewed Jul 27, 2023

View reviewed changes

tensorstore/kvstore/s3/s3_credential_provider.cc Show resolved Hide resolved

sjperkins added 3 commits July 28, 2023 08:59

requester_pays = false

19a52b1

section_name from std::string to std::string_view

bca1a38

Remove unused S3RequesterPaysResource

785c942

This comment was marked as resolved.

Sign in to view

sjperkins added 4 commits July 28, 2023 17:13

Merge branch 'master' into s3

b665672

Include missing cache_key header specialisations

6673731

Revert section_name back to std::string

fc53d1d

Store signed header value as string_view

2084522

sjperkins added 7 commits July 31, 2023 10:08

Indentation

4f29a6d

GetTag returns Unescaped XML struct

25b517c

Support x-amz-requester-payer header

7cd6766

Add optional host member to S3KeyValueStoreSpecData

298c09f

endpoint doesn't need to be set to empty string in ParseS3Url as it i…

87beb30

…s optional

PercentDecode ParseS3URL paths

66408e9

Localstack test fixture

73e8718

sjperkins commented Jul 31, 2023

View reviewed changes

laramiel reviewed Jul 31, 2023

View reviewed changes

sjperkins closed this Sep 2, 2023

sjperkins deleted the s3 branch September 2, 2023 14:19

sjperkins mentioned this pull request Sep 5, 2023

Continue localstack test harness development #111

Closed

sjperkins mentioned this pull request Sep 21, 2023

Further S3 Support Umbrella Issue #114

Open

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

S3 Support #91

S3 Support #91

sjperkins commented Mar 31, 2023 •

edited

Loading

jbms commented Mar 31, 2023

sjperkins commented Apr 3, 2023 •

edited

Loading

jbms commented Apr 3, 2023

Constructing S3 Endpoint URLs

sjperkins commented Apr 5, 2023 •

edited

Loading

jbms commented Apr 6, 2023

jbms commented Apr 6, 2023

laramiel commented Apr 7, 2023 •

edited

Loading

sjperkins commented Apr 12, 2023

jbms commented Apr 13, 2023

tchaton commented Apr 13, 2023 •

edited

Loading

tchaton commented Apr 13, 2023

sjperkins commented Apr 13, 2023

This comment was marked as resolved.

This comment was marked as resolved.

sjperkins commented Jul 31, 2023 •

edited

Loading

sjperkins Jul 31, 2023

jbms Jul 31, 2023

laramiel Jul 31, 2023

laramiel Jul 31, 2023

laramiel Jul 31, 2023

laramiel Jul 31, 2023

laramiel Jul 31, 2023 •

edited

Loading

laramiel Jul 31, 2023 •

edited

Loading

laramiel commented Sep 1, 2023

sjperkins commented Sep 2, 2023 •

edited

Loading



		ABSL_FLAG(std::string, localstack_binary, "",
		"Path to the localstack");

S3 Support #91

S3 Support #91

Conversation

sjperkins commented Mar 31, 2023 • edited Loading

TODO

General KVstore

Testing

Authorisation

Documentation

Polishing

jbms commented Mar 31, 2023

sjperkins commented Apr 3, 2023 • edited Loading

S3 Key-Value Store

S3 Builder Class

Obtaining configuration variables

Python pseudo-code for deriving AWS variables

Constructing S3 Endpoint URLs

S3 KVStore

TODO

Questions

jbms commented Apr 3, 2023

Constructing S3 Endpoint URLs

sjperkins commented Apr 5, 2023 • edited Loading

jbms commented Apr 6, 2023

jbms commented Apr 6, 2023

laramiel commented Apr 7, 2023 • edited Loading

sjperkins commented Apr 12, 2023

jbms commented Apr 13, 2023

tchaton commented Apr 13, 2023 • edited Loading

tchaton commented Apr 13, 2023

sjperkins commented Apr 13, 2023

This comment was marked as resolved.

This comment was marked as resolved.

sjperkins commented Jul 31, 2023 • edited Loading

sjperkins Jul 31, 2023

Choose a reason for hiding this comment

jbms Jul 31, 2023

Choose a reason for hiding this comment

laramiel Jul 31, 2023

Choose a reason for hiding this comment

laramiel Jul 31, 2023

Choose a reason for hiding this comment

laramiel Jul 31, 2023

Choose a reason for hiding this comment

laramiel Jul 31, 2023

Choose a reason for hiding this comment

laramiel Jul 31, 2023 • edited Loading

Choose a reason for hiding this comment

laramiel Jul 31, 2023 • edited Loading

Choose a reason for hiding this comment

laramiel commented Sep 1, 2023

sjperkins commented Sep 2, 2023 • edited Loading

sjperkins commented Mar 31, 2023 •

edited

Loading

sjperkins commented Apr 3, 2023 •

edited

Loading

sjperkins commented Apr 5, 2023 •

edited

Loading

laramiel commented Apr 7, 2023 •

edited

Loading

tchaton commented Apr 13, 2023 •

edited

Loading

sjperkins commented Jul 31, 2023 •

edited

Loading

laramiel Jul 31, 2023 •

edited

Loading

laramiel Jul 31, 2023 •

edited

Loading

sjperkins commented Sep 2, 2023 •

edited

Loading