Amazon S3 | Operate As Docs

Website: aws.amazon.com
Connects by: Pasting a Access key ID
Category: Files and docs
Part of: Amazon Web Services
Tools: 77

Service	Key	Base URL
Amazon S3	`amazon-s3`	`https://s3.{region}.amazonaws.com`

Your client also types their region (Where your resources are, such as us-east-1 or eu-west-2).

Connecting

Your client makes a Access key ID in their Amazon Web Services settings and pastes it on their link. Operate As tries it with Amazon Web Services before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "amazon-s3"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "amazon-s3"    ]  }]

Permissions

What the client reads	Permission it asks for
Use the Amazon Web Services key you paste, with only the access you gave that key	Chosen on the provider's screen

Tools

Install Amazon S3's typed package for your language:

pip install operate-as-amazon-s3

pip install operate-as-amazon-s3

Run amazon-s3.abort_multipart_upload

curl -X POST https://api.operate.as/v1/actions/amazon-s3.abort_multipart_upload \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "bucket": "<bucket>",
      "key": "<key>",
      "upload_id": "<upload_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/amazon-s3.abort_multipart_upload \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "bucket": "<bucket>",      "key": "<key>",      "upload_id": "<upload_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/amazon-s3.abort_multipart_upload

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://s3.{region}.amazonaws.com, with the parts in braces filled in from your client's account. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../amazon-s3GET /aws" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../amazon-s3GET /aws" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

A key works until your client deletes it in Amazon Web Services. They can paste a new one on the same link at any time, and your workflows carry on without changes.

See Keeping access alive and Removing access.

Calls answer, once the key is deleted

{
  "status": 401,
  "data": {
    "…": "the service's own error"
  },
  "encoding": "json"
}

{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}