PAGE CONTENTS
Objectives
The overarching objective of the COPI project is to enable new space-based data business models and related applications by improving the access, adaptability, automatization, and responsiveness of Spire’ multi-constellations operations and infrastructure.
Under the COPI project Spire is developing a full web User Interface (UI) for customers, akin to Amazon’s AWS Admin dashboard, that includes satellite mission management and optimization features that makes deploying, operating, and scaling applications in space faster and easier using Spire Space Services.
Challenges
A crucial ingredient of granting access to space to new users and applications is the removal of the complexity, risk, and even visibility from the space component. Users of space infrastructures do not care about launch dates and sensor specs as much as they care about receiving their data on time and in a very simple way. Spire is doing it by internalizing the infrastructure, process, and R&D that used to be part of its customers’ core business, as well as by creating new business models for the infrastructure component that mirrors service-based monthly pricing.
Ultimately, this kind of offering aims at non-expert customers who interact with their space application through an API without even realizing it. This vision for Spire is a way to enable space-based data services and applications as part of the everyday life of any commercial entity such as the cloud is today.
System Architecture
The system architecture is explained through the following diagram:
The sequence begins with a user’s browser interacting with Amazon Cognito, accessing the authentication page, and submitting their credentials (username and password). Upon receiving this information, Amazon Cognito requests multi-factor authentication (MFA) from the user, providing an extra layer of security. The user responds by providing the MFA, typically a code sent to their device. Once the MFA is successfully received and validated, Cognito generates a secure JSON Web Token (JWT) containing the user’s authentication and profile information and sends it back to the browser.
In the next stage, the browser, equipped with the JWT token, sends a request to the internal console’s /api/ endpoint. The request includes the JWT token in the Bearer field of the header. On receiving the request, the console reaches out to Amazon Cognito to verify the token’s validity. Cognito confirms the token’s authenticity and relays this verification back to the console. After confirming the token’s validity, the console requests Cognito to provide additional user information embedded within the token. Cognito processes this request and returns the relevant information, including the organization ID associated with the authenticated user.
With the user now authenticated and their credentials verified, the console initiates communication with the internal tasking service. It sends a request to the Tasking service’s /satellites/ endpoint, incorporating the user’s organization ID and email in the request. The Tasking service receives and processes this request, returning data associated with the satellites linked to the specific organization ID.
Upon receiving the satellites data from the Tasking service, the console renders this information and displays it to the user via their browser. Hence, the sequence reflects a secure authentication and data retrieval process that involves the user’s browser, Amazon Cognito for authentication, and the internal console and tasking services to accurately deliver satellite data to an authenticated user.
Plan
Kick-off Meeting : T0
Requirements Review (Incl. CDR) : T0 + 6 months
APIs Validation Review (Incl. TRR1) : T0 + 12 months
UIs Validation Review (Incl. TRR2) : T0 + 18 months
Final Review (Incl. FAT) : T0 + 24 months
Current Status
Successful Kick-Off of the Constellation Operation Infrastructure project On 18 January 2023, the “Constellation Operation Infrastructure” COPI project was officially launched by Spire and ESA
Companies
