Amazon RDS & AWS Marketplace – Managed SQL Server and Seller Reporting
Hardening managed SQL Server on Amazon RDS and improving AWS Marketplace seller reporting pipelines.
At AWS I worked on two closely related areas: Amazon RDS for SQL Server (managed relational databases) and AWS Marketplace (seller reporting & analytics). The focus was on security-sensitive database features and reliable reporting pipelines for large sellers.
On RDS for SQL Server, I contributed to TLS/cipher configuration, led the initial design for linked servers on RDS Custom, and helped harden SSAS as a managed option.
On AWS Marketplace, I improved the ETL and operational guardrails behind seller usage and revenue reports so data arrived consistently and with clear guarantees.
Role: Software Development Engineer, RDS SQL Server & AWS Marketplace
Tech: Amazon RDS (SQL Server, RDS Custom), SSAS, AWS Kinesis, AWS Glue, Amazon Athena, Amazon S3, AWS Lambda, AWS Step Functions, CloudWatch, ETL pipelines.
Amazon RDS for SQL Server – Security & Enterprise Features
On the RDS SQL Server team I worked on features that made the managed service a better fit for regulated and enterprise workloads, especially around network security and connectivity.
TLS and cipher configuration: Co-designed and implemented support for configuring TLS versions and cipher suites through DB parameter groups, so customers could disable legacy protocols (for example TLS 1.0/1.1) and meet their compliance baselines without custom scripting.
Linked servers on RDS Custom: Led the initial design for enabling linked servers from RDS Custom for SQL Server to other engines (SQL Server, Oracle, PostgreSQL, etc.), defining the security model, credential storage, and driver-management story that the team later used for the public launch.
SSAS support hardening: Helped stabilize SQL Server Analysis Services as an RDS option by fixing bugs and extending tests around provisioning, authentication, and backup/restore flows.
AWS Marketplace – Seller Reporting & Analytics
In AWS Marketplace I worked on the reporting stack that generates usage, billing, and revenue reports for Marketplace sellers, with a focus on making the pipelines more predictable and support-friendly.
ETL pipeline improvements: Contributed to Kinesis → Glue → Athena pipelines that transform raw usage events into seller-facing CSV reports, tightening data contracts and handling late or duplicated events more gracefully.
Operational guardrails: Added validations, retries, and alarms around report generation and S3 delivery so issues surfaced early and could be attributed to a specific stage instead of appearing as opaque report failures.
Customer experience: Worked with PMs and support to align the system’s behaviour with documented SLAs and expectations (for example when data is considered complete for a given period).
What I Focused On (Engineering Notes)
Secure configuration surfaces: Designing TLS/cipher configuration as a first-class managed feature rather than a one-off script, so security teams could treat RDS SQL Server like any other hardened asset.
Working with database engineers: Collaborating with SQL Server experts on feasibility and performance for linked servers and SSAS support, then turning their constraints into clear API and UX trade-offs.
Reliability and debuggability: Instrumenting Marketplace reporting pipelines so data issues were observable in metrics and logs instead of surfacing as mysterious gaps in seller dashboards.
Documentation and handover: Writing internal and external docs that clarified how to use the features safely and how the underlying systems behaved in edge cases.