Spring Boot S3 File Uploads with React

Consult the official AWS SDK for Java documentation to learn about migrating from version 1 to version 2, and set up dependencies via pom.xml in your Maven project.

Configure temporary AWS credentials and store them in home/.aws/credentials to enable S3 interactions in a Spring Boot and React project, creating a programmatic user with appropriate AWS console permissions.

Create access and secret keys for programmatic access via the AWS CLI, tools SDK, or API, then store them locally and rotate keys as a best practice.

Create and edit the local AWS credentials file at ~/.aws/credentials using the default profile, and securely store the access key ID and secret access key, keeping them confidential.

Learn to use Amazon S3, the object storage service, to store data—from analytics and logs to videos and pictures—by creating buckets and configuring an S3 client for programmatic access.

Configure a Spring Boot S3 client bean using the AWS S3 SDK, set the region in application.yaml, and prepare a fake local-file implementation for testing without credentials.

Implement a Spring service with an S3 client to upload and download objects in a bucket. Create a putObject method that takes bucket name, key, and a request body byte array, then call s3Client.putObject, and manage buckets via infrastructure as code.

Implement a get object method with an S3 client to download an object, read bytes from the response input stream, handle errors with try-catch, and return the byte array.

Create a new S3 bucket in the AWS console, configure the region, and verify by writing code that uses two methods to upload files to S3.

Demonstrates uploading and downloading to an S3 bucket from a Java IntelliJ setup, using a bucket name and key, storing a Hello world byte array, and handling credential errors.

Configure the S3 bucket name via application.yaml to enable profile-specific bucket changes without code edits, inject AWS S3 buckets, and access the customer bucket through getters.

Expose upload and download endpoints in the customer controller to store and retrieve profile images, using multipart file uploads and a byte array return via a dedicated customer service.

Implement a service method to upload customer profile images to S3, checking customer existence, constructing a bucket key with customer and image ids, uploading bytes, and handling errors.

Implement the service method to download a customer's profile image from S3, handle empty image IDs, map the customer data, and prepare to store the image ID in the database.

Add an optional profile_image_id column to the customer table via migration, enforce uniqueness, and map it in the customer entity to store and retrieve profile image keys for S3 uploads.

Showcases updating a customer's profile image id using both JDBC and JPA in a Spring Boot app, with repository queries and SQL statements.

Update the JDBC data access service to include a new column in select statements, adjust the customer row mapper, and run tests to validate updates and profile image id handling.

Store the profile image by updating the customer DAO with the profile image ID in AWS, then retrieve by ID and map it to the DTO via the row mapper.

Fix compilation errors and test failures by correcting the customer dto and row mapper, updating tests, and validating unit and integration tests with docker and s3.