AWS Simple Storage Service
Export Configuration#
Exporting an S3 service via a Tranquil Data peer extends the configuration object with the following fields:
| Field Name | Type | Required | Default |
|---|---|---|---|
| endpoint | string | http://defaultServiceHost:80 |
|
| region | string | us-east-1 |
|
| id | string | ||
| key | string | ||
| certificate | string |
The value of type must be s3.
The value of endpoint is a string of the form PROTOCOL://HOST:PORT, where the default value for PORT is 80 if the PROTOCOL is https, and 443 if https.
The values of key and id are the Access Key ID and Secret Access Key (respectively) used to authenticate to both the Tranquil Data software, and the backing S3 service. In this release, all connections are made as this identity, and the authentication to the Tranquil Data software will match those in the backing S3 service.
HTTPS connections require that the certificate field contains the S3 certificate.
Context Interaction#
Context is formed by using objects that are of a well-known data format. Currently, Tranquil Data supports JSON, FHIR, and Apache Parquet documents in S3.
Sessions may be defined by re-using HTTP keep-alive connections. For instance, if you use a library like Boto3 to do S3 operations from AWS Lambda, it will keep connections pooled and open for the duration of the function. The effect is that the Lambda function defines a session similar to a SQL Transaction.
Context forms and policy is evaluated for the following S3 REST calls:
GET /{bucket}/{object}PUT /{bucket}/{object}