CloudTamer Project Name	CloudTamer OU	Primary Region
esdis-application-edsc-sit-8022	ESDIS-EDSC	us-east-1
esdis-application-edsc-uat-8982	ESDIS-EDSC	us-east-1
esdis-app-edsc-prod-7557	ESDIS-EDSC	us-east-1
<add rows as needed>

Application References

DNS Entries	CloudFront URLs	AWS Endpoints (URL / ARN)	AART Registration	Notes	Action Items
https://access.sit.earthdata.nasa.gov	NASD-2636	NASD-2639	https://aart.nasa.gov/entities/1325187	DNS entry currently point to on-prem application.	NASD-2723
https://access.uat.earthdata.nasa.gov	NASD-2637	NASD-2640	https://aart.nasa.gov/entities/1463111	DNS entry currently point to on-prem application.	NASD-2724
https://access.earthdata.nasa.gov	NASD-2638	NASD-2641	https://aart.nasa.gov/entities/1286711	DNS entry currently point to on-prem application.	NASD-2725
<add rows as needed>

...

Points of Contact

...

Validation Item	Completed (Y / N)	Reference Artifact, Link, or Comment if needed	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	N	Waiting on NASD-2636 & NASD-2639Experiencing 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?	Y
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

...

Validation Item	Completed (Y / N)	Reference Artifact, Link, or Comment if needed	Notes
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?	Y	Egress from Access is extremely minimal. Given that use of Access is limited and the nature of the application, there will be almost no discernable change in egress as a result of deploying Access to NGAP.
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	Y
Have both application team and platform team received approved egress cap and throttling threshold values from ESDIS?	Y		Once we are up, we could/should consider filing for Cloudfront Egress Waiver (like Earthdata Search SIT has).
<add rows as needed>

NGAP References:

...

Validation Item	Completed (Y / N)	Reference Artifact, Link, or Comment if needed
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	Y
Has the application team noted any needed exceptions / waivers from EDC Tenant Run Rules? If so, have those requests been approved?	Y	None needed
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)	Y
Is application team aware of software vulnerability scanning and reporting requirements? EC2/AMI Lifecycle and Patching Policy Additional CICD scanning/reporting requirement in development	Y
Has Is application team aware of, or been made aware of via the ESDIS Security of , any known vulnerabilities. Are known vulnerabilities addressed, mitigated, or residual risk within acceptable levels?	N
Does the application team have processes in place to identify, assess, and address security vulnerabilities if they occur?	Y
<add rows as needed>

...

...