SP-018-002 AWS console-managed resources procedure
Procedure flowchart
Purpose
This procedure defines the process for creating, configuring, updating and decommissioning AWS resources that are managed through the AWS Management Console, CLI or SDK.
Scope
This procedure applies to all AWS console-managed resources, including but not limited to:
- Lambda functions
- ECR repositories
- ECS services and task definitions
- S3 buckets
- RDS databases
- API Gateway endpoints
- CloudWatch alarms and dashboards
Responsibilities
JD-001 and JD-003
- To approve the creation or decommissioning of AWS resources.
JD-005
- To ensure that resource changes follow the methodology established in this procedure.
- To review IAM permissions assigned to each resource.
JD-007
- To perform the technical operations described in this procedure and record the corresponding evidence.
Inputs
- Requirements or justification for the new, updated or decommissioned resource.
Outputs
- The created, updated or decommissioned AWS resource.
- Updated
T-018-001 Infrastructure list and control plan. - Updated
T-013-002 Risk Management Record(if applicable).
Development
Creating a new resource
-
The team member requesting the resource communicates the need and justification to
JD-005. -
JD-005evaluates the request and obtains approval fromJD-001orJD-003. -
JD-007creates the resource in the AWS Console (or via CLI/SDK) following these principles:-
Naming convention: Resources must be named using lowercase letters, numbers and hyphens (e.g.
legit-health-api-production). -
Region: All resources must be created in the agreed-upon AWS region unless there is a justified technical reason to use a different one.
-
Tagging: Every resource must include at least the following tags:
Tag key Example value EnvironmentproductionOwnergerardo-fernandezProjectlegit-health
-
-
JD-007configures the appropriate IAM permissions, ensuring the minimum access policy is applied. Only the IAM groups ("Administrators" or "Developers") that need access to the resource shall be granted permissions. -
JD-007registers the resource inT-018-001 Infrastructure list and control plan. -
JD-005updates theT-013-002 Risk Management Recordif the new resource introduces or modifies any risk.
Updating an existing resource
- The team member proposing the change communicates it to
JD-005. - For changes that affect availability, security or data integrity,
JD-005must obtain approval fromJD-001orJD-003before proceeding. Minor configuration changes (e.g. adjusting a CloudWatch alarm threshold) do not require prior approval. JD-007applies the change and updatesT-018-001 Infrastructure list and control planaccordingly.
Decommissioning a resource
JD-005identifies the resource to be decommissioned and obtains approval fromJD-001orJD-003.JD-007verifies that no other active resources or services depend on the resource to be removed.JD-007removes the resource and updatesT-018-001 Infrastructure list and control plan.JD-005updates theT-013-002 Risk Management Recordto reflect the removal.
Document signature meaning
- Author: JD-007 Gerardo Fernández
- Review: JD-005 Mr. Alfonso Medela
- Approval: JD-001 Ms. Andy Aguilar
Signature meaning
The signatures for the approval process of this document can be found in the verified commits at the repository for the QMS. As a reference, the team members who are expected to participate in this document and their roles in the approval process, as defined in Annex I Responsibility Matrix of the GP-001, are:
- Author: Team members involved
- Reviewer: JD-003 Design & Development Manager, JD-004 Quality Manager & PRRC
- Approver: JD-001 General Manager