Job Summary
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.
Key Responsibilities
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.
Skill Requirements
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.
Other Requirements
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.