Project Objectives
- Build the AWS production infrastructure required to support Release Bot.
- Migrate production and test Release Bot functions, API endpoints, deployment workflows, configuration, and integrations.
- Validate deployment and application behavior through smoke, integration, and end-to-end release testing.
- Cut over Release Bot to the production account and decommission the legacy AWS development resources.
Scope of Work
- AWS access and IAM execution-role configuration for Lambda, API Gateway, and deployment operations.
- Four Lambda functions: cut Release, cut Release Test, release Automation Merge back, and release Automation Merge back Test.
- API Gateway routes POST /beta/cut and POST /beta/merge, with production and test stages.
- Lambda runtime, handler, environment variables, secrets, logging, and Datadog related configuration.
- GitHub Actions secrets and parallel deployment jobs for the validation period.
- Slack application endpoint updates, Jira webhook validation, GitHub configuration access, and release-cycle testing.
- Controlled cutover, removal of parallel deployment logic, credential rotation, documentation, and decommissioning.
Responsibilities/Expectations
- Own the migration plan and technical execution from discovery through decommissioning.
- Use infrastructure-as-code or repeatable automation where supported by the existing repository and account standards.
- Preserve existing function names and application behavior unless a change is required and approved.
- Maintain a rollback path until production acceptance is complete.
- Protect credentials and tokens; do not expose secret values in source, logs, tickets, or documentation.
- Produce implementation notes, test evidence, risk decisions, change records, and support documentation.
- Coordinate with CloudOps/SRE, application owners, AWS account administrators, Slack administrators, Jira/GitHub owners, and observability stakeholders.
IR35 Status:
Not specified
Seniority Level:
Not Specified