Storage Integration

AWS S3

Deliver screenshot images, HTML, PDFs, and video outputs directly to your own AWS S3 bucket after every capture job — using secure cross-account access with no credentials to manage.

This page

AWS S3 — Cross-account

Grant ScreenshotCenter write access to your bucket via AWS ACL. No API keys to store or rotate.

Also available

S3-compatible — Key / Secret

Works with any S3-compatible endpoint (Cloudflare R2, Wasabi, MinIO) using your own access key and secret.

How it works

Cross-account access lets ScreenshotCenter write to your bucket without you ever sharing credentials. Instead, you grant access to our AWS Canonical ID through the bucket's ACL.

1

Create a bucket in AWS

In the AWS Console, create an S3 bucket in the region of your choice. Leave object ownership settings to allow ACL-based access.
2
Grant access to our Canonical ID

Go to Permissions → Access Control List (ACL), click Add account, and enter the ScreenshotCenter Canonical ID:
```
877f5fce8118db233f7c1d7167b0ee8cbe9601e3b83000e7904d53706af361c9
```
Grant List objects and Write objects permissions.
3

Create the app in the dashboard

In ScreenshotCenter, go to Apps, choose AWS S3 (Cross-account), and enter your bucket name and optional region. No access key required.
4

Include the app ID in screenshot requests

Add your app ID to the apps parameter. Outputs are uploaded to your bucket as soon as the job finishes.

Quick start

curl "https://api.screenshotcenter.com/api/v1/screenshot/create\
  ?key=YOUR_API_KEY\
  &url=https://example.com\
  &apps=my-aws-s3-app"

import { ScreenshotCenterClient } from 'screenshotcenter';

const client = new ScreenshotCenterClient(process.env.SCREENSHOTCENTER_API_KEY);

const shot = await client.screenshot.create('https://example.com', {
  apps: ['my-aws-s3-app'],
});

console.log(shot.apps[0].output_url); // S3 object URL

from screenshotcenter import ScreenshotCenterClient

client = ScreenshotCenterClient(api_key="YOUR_API_KEY")

shot = client.screenshot.create(
    "https://example.com",
    apps=["my-aws-s3-app"],
)

print(shot["apps"][0]["output_url"])  # S3 object URL

use ScreenshotCenter\Client;

$client = new Client(getenv('SCREENSHOTCENTER_API_KEY'));

$shot = $client->screenshot->create('https://example.com', [
    'apps' => ['my-aws-s3-app'],
]);

echo $shot['apps'][0]['output_url']; // S3 object URL

import (
    "fmt"
    sc "github.com/juliensobrier/screenshotcenter-go"
)

client := sc.New("YOUR_API_KEY")

shot, _ := client.Screenshot.Create("https://example.com", &sc.ScreenshotParams{
    Apps: []string{"my-aws-s3-app"},
})

fmt.Println(shot.Apps[0].OutputURL) // S3 object URL

require "screenshotcenter"

client = ScreenshotCenter::Client.new(ENV["SCREENSHOTCENTER_API_KEY"])

shot = client.screenshot.create("https://example.com",
  apps: ["my-aws-s3-app"],
)

puts shot["apps"][0]["output_url"] # S3 object URL

import io.screenshotcenter.ScreenshotCenterClient;
import io.screenshotcenter.models.*;
import java.util.List;

public class Main {
    public static void main(String[] args) throws Exception {
        var client = new ScreenshotCenterClient("YOUR_API_KEY");

        var shot = client.screenshot().create("https://example.com",
            new ScreenshotParams()
                .apps(List.of("my-aws-s3-app")));

        System.out.println(shot.getApps().get(0).getOutputUrl()); // S3 object URL
    }
}

using ScreenshotCenter;

var client = new ScreenshotCenterClient("YOUR_API_KEY");

var shot = await client.Screenshot.CreateAsync("https://example.com", new ScreenshotParams {
    Apps = new[] { "my-aws-s3-app" },
});

Console.WriteLine(shot.Apps[0].OutputUrl); // S3 object URL

The uploaded file URL is returned in apps[].output_url once the job finishes.

Custom file paths

Use a path template to control how files are named and organised inside the bucket:

screenshots/{domain}/{yyyy}{mm}{dd}-{id}.png

Available variables: {id}, {domain}, {yyyy}, {mm}, {dd}, {shot}, {browser}, {country}.

Why cross-account?

No credential rotation

Access is tied to your bucket ACL, not to an IAM key. Nothing to rotate or expire.

Least-privilege access

ScreenshotCenter can only write to the specific bucket you grant — no broader account access.

You own the data

Outputs land directly in your bucket under your account. Revoke access at any time by updating the ACL.

Get started

1. Create an S3 bucket and grant write access to Canonical ID 877f5fce...361c9.
2. In the dashboard, go to Apps → Connect a new app → AWS S3 (Cross-account).
3. Enter your bucket name and optional path template, then save and verify.
4. Add the app ID to your screenshot requests.

Get started free S3-compatible (key/secret) API reference