Back to engineering work

Sony · Cloud identity platform

Secure identity and resilient large-file workflows on AWS

Built and improved authenticated cloud workflows spanning Java services, AWS serverless components, large-file uploads and React interfaces.

JavaSpring BootOIDC / JWTAWSReact

The system

At Sony India Software Centre, I worked on a professional identity platform with authenticated APIs and media-oriented uploads running on AWS.

What had to be solved

Authentication and upload workflows needed to stay reliable across long-running transfers and unreliable networks while remaining secure, observable and understandable to users and support teams.

Non-negotiable requirements

  • Large transfers needed resumability instead of restarting after a transient failure.
  • Authorization had to remain consistent across gateway, service and UI layers.
  • Upload progress and failure state needed to be visible without weakening security controls.
  • Deployment changes required health checks and safe rollback behavior.

What I implemented

  • Implemented OIDC/JWT authentication flows and role-aware API behavior.
  • Contributed to multipart upload flows with resumability, integrity checks and real-time progress reporting.
  • Worked across Java services, API Gateway, AWS storage and React clients to validate end-to-end behavior.
  • Improved CloudWatch logging, correlation, dashboards and alarms for operational diagnosis.
  • Supported blue/green deployment practices with health checks and rollback awareness.

Key implementation choices

01

Model uploads as workflows

Large uploads were implemented as resumable stateful operations rather than single fragile HTTP requests.

02

Layer security controls

Gateway controls and application-level authorization were used together to protect both entry points and domain operations.

03

Correlate the journey

Signals were designed so authentication, API, storage and frontend events could be followed as one user flow.

Engineering outcome

  • Large-file operations became more tolerant of transient network interruption.
  • Authentication and upload failures became easier to isolate and support.
  • The platform gained stronger operational visibility across cloud and application layers.
Next case studyMulti-user draft, publish and event-recording workflows