In future, Amazon’s Outposts can be used with the Simple Storage Service (S3). The former are servers operated by AWS but installed and administered in the customer’s data center, with which companies can provide the same services locally, including Elastic Compute Cloud (EC2), Elastic Block Store (EBS) and Relational Database Service (RDS), as in the regular cloud -Environment of the provider should be preserved.
S3, in turn, represents an object storage service that has de facto established itself as the standard at AWS and some other providers. Outposts are always assigned to a specific AWS region, so far, the local systems could only access S3 objects there. Data can now be uploaded to the Outposts systems in your own data center via the S3 APIs and processed there before users – if desired – move them to the cloud.
Local and encrypted data with S3
Amazon is also introducing a related class, S3 Outposts, for the object storage service. It is designed to hold data redundantly on different local systems and encrypts it on the server as standard via SSE-S3. Alternatively, companies can use their own keys with SSE-C. Each Outpost can be configured with 48 or 96 TB of storage for S3, and each server can handle up to 100 buckets.
Readers can find details on how to use S3 with the Outposts in the related blog entry on amazon.com. Amazon also introduced its Outposts at re: Invent 2019 in Europe, but the provider announced the local AWS servers the year before. Other providers such as Oracle with the Cloud @ Customer want to win their customers’ data center as the location of their cloud.