4 ms·

For S3 specifically, we support IAM-based role assumption. If you go to Data > Import from Amazon S3 > Add S3 Bucket, you can grant our AWS account permissions

For S3 specifically, we support IAM-based role assumption. If you go to Data > Import from Amazon S3 > Add S3 Bucket, you can grant our AWS account permissions to read an S3 bucket in your account. We also have dedicated hosting options for our Enterprise tier. If there's a specific data source you'd like us to support OAuth integration for, let me know, and we'll add it.

glitchc 3y ago
> you can grant our AWS account permissions to read an S3 bucket in your account. That seems like a huge privacy hole. It sounds like you're offering spreadsheet-as-a-service, where you scale up AWS spot instances based on query size.
Terretta 3y ago
Great to hear you can do the policy. Are you able to be “NSL-proof”? This means, if you are served a national security letter with a gag order saying to turn over my data without telling me, can you? If you are not NSL proof, are you able to demonstrate who from your firm can, and cannot, by technical guarantee not by policy in the “signed agreement” sense, see my data, and can I see in an audit log any time and every time any of those people do see my data?
- dmurray 3y ago
  If you need protection from the US security apparatus, you're not the target market.
  - Terretta 3y ago
    On the contrary, that scenario (as well as, "what if your SaaS provider or CSP is hostile?"), are great "clarifying" questions to understand the security architecture of a product that is very likely to see some incredibly sensitive data. It is possible for the answer to be that a service is NSL proof -- with asterisks, and the asterisks are very interesting to discuss. And no, it's not about the US security apparatus for most firms, although if you take a look at AWS's security teams, you'll see there is a lot of experience exchanged, and AWS does secure the US security apparatus' data. They're quite good at it.
    - fragmede 3y ago
      > AWS does secure the US security apparatus' data. with the exception of red teams, AWS isn't securing AWS from US security apparatus attack though.

glitchc 3y ago

> you can grant our AWS account permissions to read an S3 bucket in your account. That seems like a huge privacy hole. It sounds like you're offering spreadsheet-as-a-service, where you scale up AWS spot instances based on query size.

Terretta 3y ago

Great to hear you can do the policy. Are you able to be “NSL-proof”? This means, if you are served a national security letter with a gag order saying to turn over my data without telling me, can you? If you are not NSL proof, are you able to demonstrate who from your firm can, and cannot, by technical guarantee not by policy in the “signed agreement” sense, see my data, and can I see in an audit log any time and every time any of those people do see my data?

dmurray 3y ago
If you need protection from the US security apparatus, you're not the target market.
- Terretta 3y ago
  On the contrary, that scenario (as well as, "what if your SaaS provider or CSP is hostile?"), are great "clarifying" questions to understand the security architecture of a product that is very likely to see some incredibly sensitive data. It is possible for the answer to be that a service is NSL proof -- with asterisks, and the asterisks are very interesting to discuss. And no, it's not about the US security apparatus for most firms, although if you take a look at AWS's security teams, you'll see there is a lot of experience exchanged, and AWS does secure the US security apparatus' data. They're quite good at it.
  - fragmede 3y ago
    > AWS does secure the US security apparatus' data. with the exception of red teams, AWS isn't securing AWS from US security apparatus attack though.