Understanding Amazon’s RFC Process

You can make changes in your AMS-managed environment or ask AMS to make changes on your behalf by submitting a request for change, or RFC.

You can use the AMS console or the API commands CreateRfc and SubmitRfc to generate an RFC. After selecting an AMS change type and RFC parameters (like schedule), you submit the request.

Two specifications make up an RFC: one covers the RFC itself, and the other addresses the change type (CT) parameters.

Formally speaking, a CT is described as a category, subcategory, item, and operation, or CSIO.

When the change is finished, whether it was successful (Success) or not (Failure), you are informed.

Let’s investigate who is able to submit an RFC.

Permission to create RFCs is granted to design team members.

An RFC (with the status OPEN) is created by the design team whenever they wish to modify a requirement.

The requirements manager for the client searches the RFC table for RFCs that have the status OPEN, meaning they are pending review.

The requirements manager may additionally ASSIGN these RFCs to particular client team members based on the kind of knowledge needed for the evaluation.

After receiving an email notification, those assigned can evaluate how the proposed modification would affect the project.

They add an ASSESSMENT OUTCOME (accepted/rejected) for each RFC based on their assessment.

The design team then reviews the results of the evaluations and sees if their demands have been addressed in the RFC table.