Skip to content

Document iteration to tell people about S3 buckets #241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hannahkc merged 2 commits into from
Jan 23, 2026
Merged

Document iteration to tell people about S3 buckets #241

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
64e498e
Document iteration to tell people about S3 buckets
hannahkc Jan 23, 2026
246eca5
fix typo
hannahkc Jan 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 17 additions & 4 deletions design/features/getting-completed-form-submissions/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,11 +26,24 @@ Email was the starting point for the product as it is equivalent to the way many

This iteration added the option for form creators to also get the answers in a CSV file attached to each completed form email. The task list to create or edit a form was given an extra optional task to 'Get completed forms as CSV files' for form creators to turn the CSVs on or off.

### [JSON file email attachment, December 2024](version-3-json-submissions.md)
### [JSON file email attachment, December 2025](version-3-json-submissions.md)

This added the option for form creators to get form submissions in a JSON file attached to each completed form email.

### S3 buckets, late 2024
### S3 buckets, late 2025

We made it possible for completed form submissions to go to an AWS S3 bucket in 2025. Initially this is a manual process outside of the platform. The form owners have to set up the bucket and manage it themselves. They also have to choose to receive completed forms as either JSON or CSV files. When they've given us the details and we switch their form to S3, they then get completed forms sent to their S3 bucket instead of via email.

We later published some guidance about this option on the product site - [processing completed form submissions](https://www.forms.service.gov.uk/processing-completed-form-submissions).

### Telling people about the S3 buckets option, January 2026

We need to make several changes to the task list to properly represent the S3 option. While that is being prioritised, we wanted to do something smaller to at least tell people that this is an option.

So in January 2026, we added a details component to the page where form creators set the email address for completed forms. This tells them S3 buckets is an option, and links to the [processing completed form submissions](https://www.forms.service.gov.uk/processing-completed-form-submissions) guidance on the product site which has more information and tells them to contact us to set it up.






We offered teams the option to set up AWS S3 buckets to receive completed form submissions. Initially this was offered as a manual process outside of the platform.
The form owners would have to set up the bucket and manage it themselves. They would also have to choose to receive completed forms as either JSON or CSV files. Once we set it up, they would then get completed forms sent to their S3 bucket instead of via email.