What is an RFC?: An RFC is a document that proposes a change to smithy-rs or the AWS Rust SDK. Request for Comments means a request for discussion and oversight about the future of the project from maintainers, contributors and users.
When should I write an RFC?: The AWS Rust SDK team proactively decides to write RFCs for major features or complex changes that we feel require extra scrutiny. However, the process can be used to request feedback on any change. Even changes that seem obvious and simple at first glance can be improved once a group of interested and experienced people have a chance to weigh in.
Who can submit an RFC?: An RFC can be submitted by anyone. In most cases, RFCs are authored by SDK maintainers, but everyone is welcome to submit RFCs.
Where do I start?: If you're ready to write and submit an RFC, please start a GitHub discussion with a summary of what you're trying to accomplish first. That way, the AWS Rust SDK team can ensure they have the bandwidth to review and shepherd the RFC through the whole process before you've expended effort in writing it. Once you've gotten the go-ahead, start with the RFC template.
- RFC-0001: AWS Configuration
- RFC-0002: Supporting multiple HTTP versions for SDKs that use Event Stream
- RFC-0003: API for Presigned URLs
- RFC-0004: Retry Behavior
- RFC-0005: Service Generation
- RFC-0006: Service-specific middleware
- RFC-0007: Split Release Process
- RFC-0008: Paginators
- RFC-0009: Example Consolidation
- RFC-0010: Waiters
- RFC-0011: Publishing Alpha to Crates.io
- RFC-0012: Independent Crate Versioning
- RFC-0013: Body Callback APIs
- RFC-0014: Fine-grained timeout configuration
- RFC-0015: How Cargo "features" should be used in the SDK and runtime crates
- RFC-0016: Supporting Flexible Checksums
- RFC-0017: Customizable Client Operations
- RFC-0018: Logging in the Presence of Sensitive Data
- RFC-0019: Event Streams Errors
- RFC-0020: Service Builder Improvements
- RFC-0021: Dependency Versions
- RFC-0022: Error Context and Compatibility
- RFC-0023: Evolving the new service builder API
- RFC-0024: RequestID
- RFC-0025: Constraint traits
- RFC-0026: Client Crate Organization
- RFC-0027: Endpoints 2.0
- RFC-0028: SDK Credential Cache Type Safety
- RFC-0029: Finding New Home for Credential Types
- RFC-0030: Serialization And Deserialization
- RFC-0031: Providing Fallback Credentials on Timeout
- RFC-0032: Better Constraint Violations
- RFC-0033: Improving access to request IDs in SDK clients
- RFC-0034: The Orchestrator Architecture
- RFC-0035: Sensible Defaults for Collection Values
- RFC-0036: Enabling HTTP crate upgrades in the future
- RFC-0037: The HTTP wrapper type
- RFC-0038: Retry Classifier Customization
- RFC-0039: Forward Compatible Errors
- RFC-0040: Behavior Versions
- RFC-0041: Improve client error ergonomics
- RFC-0042: File-per-change changelog
- RFC-0043: Identity Cache Partitions
- RFC-0045: Configurable Serde