# DevOps Guidelines

Weslley Fernandes

# Access Requests

# AWS Account Access Request

Access to the AWS account is controlled to ensure security and compliance. Team members must follow the outlined process to request and gain access.

# Request Process

Fill out the AWS Access Request Form.
Specify the level of access required (e.g., read-only, administrator, developer).

The request will be reviewed by the DevOps Staff, expect a response within 2 business days.

Once approved, access will be granted through IAM roles or users with MFA enabled.\
Instructions for login and setup will be sent to your email.

Notes

Temporary credentials or limited-time access may be issued for one-time tasks. Always follow least privilege principles.

# GitHub Organization Access Request

# Overview

Access to the DNA GitHub organization is restricted to ensure the integrity of repositories and workflows.\

# Request Process

Contact the DevOps Staff via email or the internal access form.
Specify the level of access required (e.g., repository access, organization admin).\

Requests will be reviewed by the Repository Maintainer or DevOps Staff.
Response time: within 2 business days.

Approved users will be invited to the organization.
Set up SSH keys or use GitHub PATs for secure authentication.

Notes

Always commit following repository-specific contribution guidelines. Access will be periodically reviewed, and unused accounts may be deactivated.

# Release Window

# Definition

A Release Window is a pre-scheduled timeframe for deploying updates, patches, or new features to production environments.

Policy

Releases are allowed only within designated windows to ensure stability and availability. Release windows are typically scheduled during low-traffic hours.
Weekdays: 8PM - 6AM GMT-5
Weekends: 6PM - 8AM GMT-5

# Guidelines

Perform thorough testing in staging environments.
Obtain approval from the DevOps and Development leads.

Monitor systems in real-time for any anomalies.
Be prepared to rollback changes if needed.

Confirm the system's stability.
Update the release logs and notify stakeholders.

# Maintenance Window

# Definition

A Maintenance Window is a designated period for performing system updates, backups, and infrastructure changes.

Policy

Maintenance windows are scheduled in advance to minimize disruptions.
Standard maintenance periods:
Weekdays: 8PM - 6AM GMT-5
Weekends: 6PM - 6AM GMT-5

# Guidelines

Notify stakeholders 72 hours in advance of any planned maintenance.

Ensure changes are documented in the Change Management System (if applicable) and follow the approved maintenance plan to prevent unplanned downtime.

Verify system functionality and update stakeholders with a summary of activities performed.