Versions Compared

Key

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

Image Added

The Science Cloud is a new Managed Cloud Environment that unifies SMD-funded accounts from the SMCE, EarthData Cloud, and Mission Cloud Platform (science tenants only) into a modernized cloud infrastructure. It offers centralized governance, automated compliance, and single sign-on access across multiple cloud providers—currently AWS and Azure, with GCP and others planned for the future.

The Science Cloud delivers faster resource provisioning, enhanced security controls, and streamlined user management with PIV and federated authentication support. Building on lessons learned from the SMCE, the new infrastructure provides multi-cloud flexibility and improved operational efficiency while simplifying the user experience. These enhancements enable projects to access cloud resources across multiple providers more securely and efficiently.

The Science Cloud is currently available for FISMA Low projects, with FISMA Moderate capability coming in 2026. The full Science Cloud Minimal Viable Product (MVP), as defined by the project plan, will be attained by the end of Fiscal Year 2027. For more details about current MVP capabilities or to get started, please contact the Science Cloud team.


Livesearch
spaceKeySCKB
sizelarge
additionalpage excerpt
placeholderSearch the Science Cloud Knowledge Base
typepage

Image Removed


Getting Started in the Science Cloud

What is

Requesting a Science Cloud

, and how does it differ from SMCE?

Why is SMD making this change from individual to consolidated cloud infrastructure?

When will the Science Cloud be ready for use?

What can I expect during migration to the Science Cloud?

Science Cloud AWS Login Procedure

Migration Impact

Migration from SMCE to Science Cloud

What is going to happen to my reserved instances when I migrate from SMCE to Science Cloud?

Will my service accounts be affected during the migration?

What happens to IAM users or groups associated with custom IAM roles in my project during migration?

Will my application or service need to move to a new domain when I migrate from the SMCE to the Science Cloud?

Do we still get to choose any AMIs we like in Science Cloud?

How does the SMCE to Science Cloud migration process work?

Accounts and Security

Are Account Numbers going to change with the transition from SMCE to Science Cloud?

Where do I go to log into my Science Cloud accounts?

If NASA credentialed users going to be using Launchpad to log in, do we need to submit any NAMS requests?

How does login work for external collaborators who do not have PIV cards?

Will I be able to use my university's Multi-Factor Authenticator (MFA) instead of a Science Cloud specific MFA?

Will using the console require being on the VPN?

Is there also any barrier to international participation?

Account

Accessing Your Science Cloud Accounts

Budget Development Assistance

Service Desk Support

Science Cloud Regions: Available and Restricted

Science Cloud Tenant Roles

AWS Account Login Procedure

Financial Services

FinOps Overview

Funding Requirements and Procedures

Cost Monitoring and Management: Observable Measures and Analysis

Managing Multiple Cloud Accounts and Fund Allocations

Observational Analysis

User Access and Permissions

Cost Controls and Preventive Measures

FinOps Tools: Present and Future State

Request FinOps Features or Report Issues

Accounts and Security

Requirements for Login

Access for External Collaborators Without PIV Cards

Multi-Factor Authentication (MFA) App Requirements

Console Access for NASA Credentialed Users

Support for International Collaboration

Maintenance and Flaw Remediation Plan