version 1.1
Current as of:
Purpose:
ESDIS Review Gates serve to ensure application success upon launch within the Earthdata Cloud. The following template is meant to guide discussion among application stakeholders to:
- Reduce technical risk
- Promote common understanding
- Identify remaining gaps
- Facilitate cross-team coordination to resolve issues
Completed templates are maintained in the review register for future reference and revision as necessary
Scope:
ESDIS Review Gate is the first in a two-stage review process that focuses on cloud-specific issues such as:
- Operations points of contact
- Shared operational responsibilities
- EDC tenant run-rules
- Cloud services, restrictions, and limitations
- Cloud cost monitoring, control, and compliance
- Cloud and on-premises network connectivity, capacity, and performance
- Security compliance
End-to-End System Readiness is the second review in the two-stage process prior to public release and is focused on mission and business readiness considerations.
Process
Tables below should be filled out prior to or during the ESDIS Review Gate.
BLUE highlighted cells should capture the collected team inputs and reference information.
GREEN highlighted cells are provided at each step to capture notes and action items related to the item in question.
| <please fill out> | <please fill out> | <use if needed> |
Review Metadata
Date conducted:
Attendees:
| Readiness Review Results | Notes | Action Items |
|---|---|---|
<to be completed at conclusion of review> |
Application / Mission Context
Please provide slides, links, or other reference materials to provide context for the application / mission for which this review is being conducted.
Please include a data-flow diagram in these artifacts.
Examples may include:
- Mission / Concept / Business-Case information
- Development Timelines / Milestones
- Requirement Statements
| Date | Artifact | POC | Notes | Action Items |
|---|---|---|---|---|
10/1/2021 | SDRT-1112 - Getting issue details... STATUS | This feature was requested by ESDIS and the most desirable solution was to leverage a new version of the Earthdata Access application. |
Anticipated Public Release Date
| Date | Notes | Action Items |
|---|---|---|
| SIT DNS cutover | |
| UAT DNS cutover | |
| Prod DNS Cutover |
Earthdata Cloud AWS account info
| CloudTamer Project Name | CloudTamer OU | Primary Region | Notes | Action Items |
|---|---|---|---|---|
| <add rows as needed> |
Application References
| DNS Entries | CloudFront URLs | AWS Endpoints (URL / ARN) | AART Registration | Notes | Action Items |
|---|---|---|---|---|---|
| <add rows as needed> |
Points of Contact
Application / Mission
| Name | Role | Notes | Action Items | |
|---|---|---|---|---|
| Mark Reese | Product Owner | mreese@element84.com | ||
| Ryan Abbott | Technical POC | ryan@element84.com | ||
| Operations POC | ||||
| Security POC | ||||
| <add rows as needed> |
EDC Platform Operations
| Name | Role | Notes | Action Items | |
|---|---|---|---|---|
| Product Owner | ||||
Operations Lead | ||||
| Scrum Master | ||||
| <add rows as needed> |
ESDIS Financial Management
| Name | Role | Notes | Action Items | |
|---|---|---|---|---|
| App Admin | ||||
| <add rows as needed> |
ESDIS Security Management
| Name | Role | Notes | Action Items | |
|---|---|---|---|---|
| ESDIS Security | ||||
| <add rows as needed> |
Application Functionality within EDC
Earthdata Cloud provides tenants with direct access to Cloud Service Provider resources, services, and functionality. Various guard-rails have been implemented to provide assurance of compliance with NASA/ESDIS policies and limit risk of compromise or cost overruns. Applications must perform adequate pre launch testing to validate proper functionality within the guard-rails established by EDC.
General:
| Validation Item | Completed (Y / N) | Reference Artifact, Link, or Comment if needed | Notes | Action Items |
|---|---|---|---|---|
| Has application team conducted end-to-end testing within the EDC and confirmed existing EDC services are sufficient to meet application needs? | Ongoing | Experiencing a timeout at the moment, continuing to debug. | ||
| Has application team confirmed that existing in-cloud networking (ex: NGAP managed App-VPC) is sufficient to meet application needs? | ||||
| Has application team conducted network connectivity testing for any data ingest flows and confirmed existing ingest options are sufficient to meet application needs? | N/A | |||
| Has application team confirmed that system administrator connectivity options are sufficient to meet application needs? | Y |
NGAP References:
- Earthdata Cloud User Guide
- Available AWS Services Sub-Section: AWS Services Approval Status Page
Data Egress:
| Validation Item | Completed (Y / N) | Reference Artifact, Link, or Comment if needed | Notes | Action Items |
|---|---|---|---|---|
| Has the application team conducted network connectivity and performance testing for any data egress flows and confirmed existing egress options are sufficient to meet application needs? | ||||
Has the application team conducted testing to ensure application continues to operate while in a bandwidth throttled mode? (not mandatory but recommended for high volume S3 distributors) | N | |||
Is application team aware of AUTOMATED egress related cost monitoring, alerting, and enforcements?
| ||||
Have both application team and platform team received approved egress cap and throttling threshold values from ESDIS? | ||||
| <add rows as needed> |
NGAP References:
- Application Publication Sub-Section: Earthdata Cloud Egress Controls and Traffic Flows
Cloud Finances
| Validation Item | Completed (Y / N) | Reference Artifact, Link, or Comment if needed | Notes | Action Items |
|---|---|---|---|---|
| Does application team have an ESDIS approved Cost-Model on file? | ||||
| Does target EDC account(s) have sufficient funds allocated in CloudTamer for anticipated cloud costs? | ||||
Is application team aware of AUTOMATED AWS account level cost monitoring, alerting, and enforcements?
Manual actions to delete resources will be considered above Freeze-Spend and Circuit Breaker levels | ||||
| Are CloudTamer budget-based notifications configured to send emails to all desired app-team individuals? | ||||
Is application team aware of AWS options for monitoring and alerting on cloud costs expenditures specific to their account and use-case
| ||||
| Does application team have a process to monitor / audit cloud expenditures and take action if required? | ||||
| <add rows as needed> |
NGAP References:
Operations
| Validation Item | Completed (Y / N) | Reference Artifact, Link, or Comment if needed | Notes | Action Items |
|---|---|---|---|---|
| Does application team have processes in place to address operations issues that arise with their application in the EDC? | ||||
Do application team and platform team have a common understanding of the shared operational responsibilities between:
| ||||
| Does application team have any "critical" functionality requiring 24/7 on-call platform support? "Critical" is scoped to items where the loss of functionality will irrevocably harm science data retention. (Ex: satellite data will be lost with no means of recovery) | ||||
| Is application team aware of and familiar with NGAP Service Desk (NASD): NASD Link | ||||
| Is application team aware of and familiar with AWS Enterprise Support | ||||
| Is application team aware of and subscribed to NGAP Announcements: Subscribe to the Announcements Mailing List | ||||
| Is application team aware of NGAP / Security Office Hours? Office Hours Link | ||||
| <add rows as needed> |
Compliance
| Validation Item | Completed (Y / N) | Reference Artifact, Link, or Comment if needed | Notes | Action Items |
|---|---|---|---|---|
| Has the application team reviewed the EDC Tenant Run Rules and confirmed they are able to operate within those rules? Earthdata Cloud Tenant Run Rules | ||||
| Has the application team noted any needed exceptions / waivers from EDC Tenant Run Rules? If so, have those requests been approved? | ||||
| Does the application team have an approved Operational Security Agreement (OSA) on file with ESDIS Security? OSA Template Handbook | ||||
Is application team leveraging EDC CICD for deployments or alternative mechanisms? (NOTE: not required, just for record keeping) | ||||
Is application team aware of software vulnerability scanning and reporting requirements?
| ||||
| Has application team aware of, or been made aware of via ESDIS Security of known vulnerabilities. Are known vulnerabilities addressed, mitigated, or residual risk within acceptable levels? | ||||
| Does the application team have processes in place to identify, assess, and address security vulnerabilities if they occur? | ||||
| <add rows as needed> |
Other Notes and Action Items
| Notes | Action Items |
|---|---|
Overview
Content Tools