Getting started with 1A Object Storage

Customer setup values

1A Object Storage is designed to work with S3-compatible tools and workflows that support custom endpoints. For v1, customers should use path-style addressing with the endpoint assigned by the 1A team.

Endpoints and storage cells

The endpoint includes the service name, public grouping, and storage cell. The cell name should not change the SigV4 signing region, which remains us-central-1.

Example public/semi-public cell endpoints include s3.us-central-1a-c01.1awebservices.com, s3.us-central-1a-c02.1awebservices.com, and s3.us-central-1b-c01.1awebservices.com.

Bucket and object URL patterns

https://s3.us-central-1a-c01.1awebservices.com/{bucket}
https://s3.us-central-1a-c01.1awebservices.com/{bucket}/{key}
https://s3.us-central-1a-c01.1awebservices.com/acme-vendor-uploads/incoming/vendor-file.pdf

Access keys

Access keys and secret keys are provided by 1A during onboarding. Do not place credentials in source control, public documentation, client-side code, or support tickets.

AWS CLI examples

aws --endpoint-url https://s3.us-central-1a-c01.1awebservices.com s3 ls
aws --endpoint-url https://s3.us-central-1a-c01.1awebservices.com s3 mb s3://acme-vendor-uploads
aws --endpoint-url https://s3.us-central-1a-c01.1awebservices.com s3 cp ./file.pdf s3://acme-vendor-uploads/incoming/file.pdf
aws --endpoint-url https://s3.us-central-1a-c01.1awebservices.com s3 ls s3://acme-vendor-uploads

Presigned URLs

Presigned GET and PUT URLs are intended for temporary download and upload workflows, including vendor upload portals and customer handoff processes.

Important beta notes

• Use path-style addressing.
• Do not use virtual-hosted bucket style for v1 unless instructed by 1A.
• Your assigned endpoint may differ based on your storage cell.
• Do not hardcode another customer's cell endpoint.