Can GitLab and Amazon S3 talk in both directions?

Yes. Build one flow that starts in GitLab and acts in Amazon S3, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect GitLab to Amazon S3

Move data between GitLab and Amazon S3 the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore GitLab Explore Amazon S3

GitLab triggers: 1
GitLab actions: 2
Amazon S3 triggers: 1
Amazon S3 actions: 8

Automation ideas

What you can build with GitLab and Amazon S3

A few flows teams run between GitLab and Amazon S3. Use one as a starting point, or build your own from scratch.

New Project Issue Event in GitLab creates Upload File in Amazon S3
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.
New or Updated File in Amazon S3 creates Create Issue in GitLab
Triggers when you add or update a file in your bucket. The bucket/folder you choose must not contain more than 10,000 files.
New Project Issue Event in GitLab creates Read File in Amazon S3
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.
New or Updated File in Amazon S3 creates Custom API Call in GitLab
Triggers when you add or update a file in your bucket. The bucket/folder you choose must not contain more than 10,000 files.
New Project Issue Event in GitLab creates Generate signed URL in Amazon S3
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.