Versions Compared

Old Version 1

changes.mady.by.user user-c2913

Saved on

compared with

New Version 2

changes.mady.by.user user-c2913

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

<add rows as needed>
DateArtifactPOCNotesAction Items

10/1/2021

Jira
serverEarthdata Ticketing System
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId9a2ac141-7181-31f1-a247-ccbc66e20158
keySDRT-1112

user-c2913 

Ryan Abbott 

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

DateNotesAction Items

 

SIT DNS cutover

 

UAT DNS cutover

 

Prod DNS Cutover<add rows as needed>

Earthdata Cloud AWS account info

...

NameRoleEmailNotesAction Items
Mark ReeseProduct Ownermreese@element84.com

Ryan AbbottTechnical POCryan@element84.com


Operations POC



Security POC


<add rows as needed>



...

Validation ItemCompleted
(Y / N)		Reference Artifact, Link, or Comment if neededNotesAction 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? <add rows as needed>Y


NGAP References: 

...

Validation ItemCompleted
(Y / N)		Reference Artifact, Link, or Comment if neededNotesAction 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?
  • Egress cut-off at egress cap
  • Bandwidth throttling over throttling threshold
  • Automated egress alerts subscriptions via NGAP provided AWS SNS topics
  • Per account egress consumption metrics via AWS CloudWatch Metrics




Have both application team and platform team received approved egress cap and throttling threshold values from ESDIS?





<add rows as needed>



...