NewResilience, Continuity, the Pro levels and Agentic Verification: from safekeeping to proof you can recover.The new line-up is here.See what's new
ResourcesGuides and case studiesMagazineVideo guidesNews tickerIntegrationsEscrow agreement
Why this page looks like this. Production's /integrations/amazon-s3 is a short template: the pill "CUSTOM INTEGRATION", "Codekeeper x Amazon S3", one security paragraph, setup steps with screenshots and a Secure Upload note, closing on "Let's build bulletproof software resilience together". This rebuild keeps every production specific (the method, the steps, the step screenshots, how access is granted) and adds what the template leaves out: why a current deposit matters when you need to recover, what the integration works with, and the next step.
  • The pair and the pill say what connects to what, and how, before anyone reads a word. The pill is production's label, word for word.
  • The mock shows Amazon S3 as a deposit source in the app, with the Software Resilience Certificate and, on a Pro level, a change flagged since the last rebuild (monitoring between runs). Example values and fictional names.
  • Logos: the Amazon S3 logo is production's file. Platform logos name the integration here; check Amazon S3's brand guidelines before launch.
  • Integration count: production says "50+" (hub FAQ, product pages), but only 24 integration pages exist and its hub grid shows 41 cards (40 platforms). The kit keeps "50+" flagged everywhere and states no other count; reconcile the figure sitewide before launch.
Amazon S3 logo
CUSTOM INTEGRATION

Codekeeper + Amazon S3

Connect Amazon S3 once and your deposit keeps pace with the code you ship. When you need to recover, you start from the version you run, not one from months ago.

Book a demo Get the sample evidence pack
  • Trusted by 3,500+ teams
  • ISO/IEC 27001:2022 certified
  • Connected with access you control
The facts a technical buyer checks first. Method, deposit and steps are production's. "Daily" is production's sync claim (the deposit video guide says OAuth and Custom deposits get "daily update checks") and stays flagged ⚑ until product confirms it. "Works with": production offers integrations for every product family (Software, SaaS and Continuity Escrow and Software Backup); Resilience is new, so confirm deposits work the same way there.

At a glance

Amazon S3 and Codekeeper, in six facts.

Connection method
Custom integration, with an IAM policy, a user and an access key
What it deposits
The S3 buckets you name, through the access you create
How often it syncs
Daily, automatically
Works with
Every protection: Escrow, Resilience, Continuity and Backup
Set up by
Whoever holds the code: usually the vendor's tech team, or yours for an in-house application
Manual alternative
Secure Upload, in the Codekeeper app
Production's steps, reworded, with production's screenshots. Step order and content are production's (6 steps); the wording is tightened and "the necessary" becomes "listed in the in-app instructions", which production says hold the same steps. The screenshots are production files from the Codekeeper 2024 image set: old UI, replace when the new UI ships. I couldn't open them from the build environment, so check each still matches its step. Production's meta description says "Integrate your Amazon S3 repositories"; S3 holds buckets, not repositories. The page says buckets, as the production FAQ does ("bucket names or URLs").

Set up

Connect Amazon S3 in six steps.

You'll find the same steps in the Codekeeper app when you activate the integration.

What you'll need

  • Access to your AWS account, to create an IAM policy and a user
  • The credentials you generate there (an access key and its ID)
  • An active protection in Codekeeper. For Escrow, deposits open once every party has signed the agreement.
Need a hand? Our technical specialists can walk you through setup and your first deposit. Email contact@codekeeper.co or contact support.
1

Activate the integration

In the Codekeeper app, select Activate on the Amazon S3 integration.

Step 1: Activate the integration, in the previous design of the Codekeeper app
2

Create an IAM policy

In your AWS account, create a new IAM policy for Codekeeper.

Step 2: Create an IAM policy, in the previous design of the Codekeeper app
3

Set the access levels

Apply the access levels listed in the in-app instructions.

Step 3: Set the access levels, in the previous design of the Codekeeper app
4

Add a user

Add a user with the required credential type, and attach the policy to that user.

Step 4: Add a user, in the previous design of the Codekeeper app
5

Generate an access key

Generate the access key, then copy the key and its ID.

Step 5: Generate an access key, in the previous design of the Codekeeper app
6

Enter the credentials in Codekeeper

Return to Codekeeper and enter the credentials in the fields provided.

Step 6: Enter the credentials in Codekeeper, in the previous design of the Codekeeper app
Say how access is granted, in plain words. Production's security paragraph for this page: "We take advantage of your platform's built-in access management features and, combined with our own multi-layered security, ensure that the once-off integration activation process allows Codekeeper to seamlessly integrate…" The first card says the same thing plainly. The encryption card uses confirmed facts only (AES-256 at rest, TLS in transit), and ISO/IEC 27001:2022 is the only certification claimed: production's integrations hub also shows ISO 9001, 27017, 27018, SOC, PCI and CSA badges, which aren't confirmed. "Industry-standard technologies" and "multi-layered security" are dropped because they say nothing checkable. The mint strip is production's Secure Upload alternative ("Deposit your Amazon S3 assets manually with our Secure Upload feature"), with the trade-off production leaves out: an integration keeps the deposit current on its own, an upload doesn't. "Just upload your assets and we'll do the rest!" is dropped as vague, and so is the old-UI screenshot (deposit-assets.png). The button goes to the tech team briefing, which covers the deposit methods.

Security

How the connection stays secure.

Access you define in AWS

You create the IAM policy and user in your own AWS account, with the access levels the integration needs, and enter the credentials in Codekeeper once.

Encrypted in transit and at rest

Traffic between Amazon S3 and Codekeeper is encrypted with TLS, and deposits are encrypted at rest with AES-256.

Certified security

Codekeeper is ISO/IEC 27001:2022 certified, audited by BSI. Policies and audit summaries are in the Trust Center.

Prefer to upload by hand? Use Secure Upload.

Upload files straight to your deposit from the Codekeeper app, with nothing to connect. Amazon S3 keeps the deposit current on its own; a manual upload stays as it is until you upload again, so you can use both.

Read the tech team briefing
Step 4, the proof: connect the integration to recovery. Production says only "ensuring the most recent version is always ready for recovery". Readiness is shown, not implied: every protection includes an automated check and a Software Resilience Certificate; Escrow Pro, Resilience Pro and Continuity Pro add Agentic Verification (four rebuilds a year in the Codekeeper AI Verification Lab, a Recoverability Certificate) and monitoring between runs, which compares the deposit with the live repositories and flags what changed. All from MESSAGING §6. The daily sync stays flagged ⚑.

Why it matters

A current deposit is one you can recover from.

Recovery starts from what's in the deposit. Keeping it in step with Amazon S3 means the version we hold is the version you run.

Kept in step

Changes in Amazon S3 reach the deposit daily, without anyone remembering to upload them.

Checked and certified

Every protection includes an automated check of what's deposited, with a vault report and a Software Resilience Certificate.

Rebuilt to prove it

With Escrow Pro, Resilience Pro and Continuity Pro, Agentic Verification rebuilds the deposit in the Codekeeper AI Verification Lab, with four rebuilds a year that you start, and issues a Recoverability Certificate.

Changes flagged between runs

On those levels, we also compare the deposit with your live repositories and flag what changed, so you know when to rebuild.

How Agentic Verification works
Keep platform searchers moving. Integration pages are mostly reached from search ("Amazon S3 escrow", "Amazon S3 backup"), and production gives them nowhere to go but the demo button. Eight related integrations: Amazon CodeCommit comes first because it's the closest alternative, then other cloud storage integrations, then the most-used ones. Each card shows production's method label.

Related integrations

Codekeeper also connects with.

Amazon CodeCommit logoAmazon CodeCommitCustom integration Azure logoAzureOAuth integration Google Cloud Platform logoGoogle Cloud PlatformOAuth integration GitHub logoGitHubOAuth integration GitLab logoGitLabOAuth integration Bitbucket logoBitbucketOAuth integration Azure DevOps logoAzure DevOpsOAuth integration GitHub Enterprise logoGitHub EnterpriseCustom integration

More integrations, plus Secure Upload for anything else. See all integrations

The secondary conversion, on every page. Visitors who aren't ready to talk can still leave their email. The sample evidence pack is the same offer on every page, so the site has one lead magnet instead of a different e-book per page. It also carries the launch story: proof, not promises. The button goes to the sample evidence pack page.

Sample evidence pack

See what your auditor would receive.

An anonymised set of outputs from a real Agentic Verification run, so you can judge the evidence before you talk to us.

  • Recoverability Certificate
  • Run report
  • SBOM and Exit workbook excerpts
Get the sample evidence pack
The questions a tech lead asks before connecting. Answers come from production's integrations hub FAQ, the deposit video guide ("OAuth and Custom Deposits allows for daily update checks"; "choose the desired asset… repeat this process") and the kit FAQ ("Deposits open once the agreement is signed"; "no per-deposit fees", flagged in to-confirm). There's no cost question on purpose: production says integrations carry "no additional cost" while also selling an Advanced Integrations add-on. Confirm, then add the answer.

Questions

Before you connect Amazon S3.

How often does the deposit update?

The integration checks Amazon S3 for changes daily and adds them to the deposit, with no per-deposit fees. You can also add files by hand at any time with Secure Upload.

What exactly gets deposited?

The S3 buckets you name, through the access you create. You choose each one when you connect, and repeat for every one the deposit needs. The agreement lists what should be deposited, and the automated check confirms what's there.

What access does Codekeeper need?

An IAM policy, a user and an access key that you create, with the access the in-app instructions list. You enter it in Codekeeper once.

When can we start depositing?

As soon as the protection is active. For Escrow, deposits open once every party has signed the agreement.

Does a connected integration prove we could recover?

It keeps the deposit current, which is where any recovery starts. The proof comes from the automated check and the Software Resilience Certificate, and with Escrow Pro, Resilience Pro or Continuity Pro, from Agentic Verification: a rebuild in the Codekeeper AI Verification Lab and a Recoverability Certificate.

The same close on every page. Integration pages close on the same two actions as every page. Visitors who arrive from a platform search see the whole story only if they're invited to take the next step. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Keep your Amazon S3 deposit ready to recover.

Book a demo and we'll walk through the connection with you. Not ready to talk? See the evidence a rebuild produces.

Book a demoGet the sample evidence pack
Chat widget goes here. Production runs HubSpot chat in this corner. Keep it on launch: it catches visitors with a quick question who won't book a demo yet. Route it to sales during office hours.