Install AWS Nitro API Co-signer

Overview

To install a Nitro Co-signer in AWS and connect it to your workspace, follow these steps:

1. Setup and configure your AWS environment
   Prepare your AWS environment by creating and configuring the required resources. Ensure it meets the necessary specifications and security settings.
2. Add a Co-signer to the workspace using an API user
   Using the Fireblocks Console or APIs, create an API user and use it to add a Co-signer to the workspace.
3. Install and connect the Co-signer to the workspace
   Download the installation script to the Nitro-capable EC2 machine and run the script to install the Co-signer. Once installation is complete, the workspace owner approves the new MPC key shares for the API user through the Fireblocks mobile app.

You can now view the Co-signer and its paired API user in your Fireblocks Console. Additionally, you can retrieve information about them using the Co-signer APIs.

---

Step 1: Setup and configure your AWS environment

Proper configuration of your AWS environment is straightforward but must be performed step by step in the specified order. Any misconfiguration could compromise the Co-signer's functionality or security.

Required AWS account permissions

You must have the necessary AWS account permissions to enable network access to required domains and to create and configure the following resources:

• IAM Role
• Customer Managed Key (CMK)
• S3 bucket
• Nitro-capable EC2 machine

1.1. Allowlist domains

To ensure the Co-signer can be installed and operated successfully, add the following domains to your allowlist:

Fireblocks-owned domains differ based on the specific Fireblocks SaaS environment you are connected to. If you are connected to the European or Swiss SaaS, update your allowlist according to the domains listed in the table below:

1.2. Setup and configure an IAM role

IAM roles are used to delegate access to your AWS resources. Create an IAM security role that ties everything together by granting only the necessary permissions to the specific resources.

1. From the “Identity and Access Management (IAM)” page, select “Roles” and “Create role”. On the “Select trusted entity” page, select:
   1. Trusted entity type: AWS service
   2. Service or use case: EC2
2. Click Next. On the “Add permissions” page, don’t make any selections.
3. Click Next. Enter the role’s name and select “Create role” without changing the trust policy.
4. Select the newly created role and copy the IAM ARN for the next steps. The IAM ARN has the following structure: arn:aws:iam::{ACCOUNT-ID}:role/{ROLE-NAME}

When you finish, the “Permissions policies” section will be empty (as shown below). After setting up the S3 bucket and the Customer Managed Key (CMK) in the Key Management Service (KMS), you will return to it to add the required policies for those resources.

1.3. Setup and configure an S3 bucket

Create the S3 bucket that serves as the Co-signer's persistent storage.

1. From the “Amazon S3” page, select “Create bucket”. Enter its name, leave everything else as default and create the bucket.
2. Select the newly created bucket and on the bucket’s details page, select “Permissions”.
3. In the “Bucket policy” section, select “Edit” and paste the following S3 policy.
4. Click “Save changes” to complete the operation.

Make sure you replace the{BUCKET-NAME}, {ACCOUNT-ID} and {ROLE-NAME} with the correct values.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Deny",
            "Principal": "*",
            "Action": [
                "s3:PutObject",
                "s3:GetObject",
                "s3:DeleteObject",
                "s3:ListBucket",
                "s3:ListBucketMultipartUploads",
                "s3:AbortMultipartUpload",
                "s3:GetObjectAcl",
                "s3:PutObjectAcl",
                "s3:RestoreObject"
            ],
            "Resource": [
                "arn:aws:s3:::{BUCKET-NAME}",
                "arn:aws:s3:::{BUCKET-NAME}/*"
            ],
            "Condition": {
                "ArnNotEquals": {
                    "aws:PrincipalArn": "arn:aws:iam::{ACCOUNT-ID}:role/{ROLE-NAME}"
                }
            }
        }
    ]
}

1.4. Setup and configure a KMS Customer Managed Key (CMK)

Create a Customer Managed Key (CMK) in KMS, which safeguards the Co-signer’s MPC keyshares.

1. Open the Key Management Service (KMS) page and select “Create key”.
2. On the “Configure key” page, select the following:
   1. Key type: Symmetric.
   2. Key usage: Encrypt and decrypt.
3. Expand the “Advanced options” section, then select the following:
   1. Key material origin: KMS.
   2. Regionality: Single-Region key. Select the Multi-Region key only if the EC2 instance is in a different region.
4. Click Next. On the “Add labels” page, set a display name for the key in the “Alias” field (in this example: fireblocks-nitro-cosigner). The “Description” and “Tags” fields are optional.
5. Click Next. On the “Define key administrative permissions” page, leave the “Key administrators” section blank and leave the “Key deletion” option checked.
6. Click Next. On the “Define key usage permissions”, leave the “Key users” section blank.
7. Click Next. Scroll down the “Review” page until you reach the “Key policy” section. Paste the following KMS policy in the “Key policy” section and select “Finish”.

Ensure you replace the {ACCOUNT-ID} and {ROLE-NAME} with the correct values.

The value for PCR8 varies based on the Fireblocks SaaS environment you are connected to. Copy the correct value into the CMK policy:

{
    "Version": "2012-10-17",
    "Id": "key-consolepolicy-4",
    "Statement": [
        {
            "Sid": "Enable enclave data processing for specific role",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::{ACCOUNT-ID}:role/{ROLE-NAME}"
            },
            "Action": [
                "kms:Decrypt",
                "kms:Encrypt",
                "kms:GenerateDataKey",
                "kms:GenerateDataKeyPair",
                "kms:GenerateDataKeyWithoutPlaintext",
                "kms:GenerateDataKeyPairWithoutPlaintext",
                "kms:GenerateRandom",
                "kms:GetKeyPolicy"
            ],
            "Resource": "*",
            "Condition": {
                "StringEqualsIgnoreCase": {
                    "kms:RecipientAttestation:PCR8": "{PCR8-VALUE}"
                }
            }
        },
        {
            "Sid": "Allow GetKeyPolicy to co-signer",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::{ACCOUNT-ID}:role/{ROLE-NAME}"
            },
            "Action": "kms:GetKeyPolicy",
            "Resource": "*"
        },
        {
            "Sid": "Allow policy management to root user",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::{ACCOUNT-ID}:root"
            },
            "Action": [
                "kms:DescribeKey",
                "kms:GetKeyPolicy",
                "kms:PutKeyPolicy",
                "kms:CreateAlias"
            ],
            "Resource": "*"
        }
    ]
}

1.5. Edit the IAM role's policy

Return to the IAM service and select the IAM role you created.

1. In the “Permissions policies” section, select “Attach policies”, select the AmazonSSMManagedInstanceCore policy and then click “Add permissions”.

2. In the “Permissions policies” section, select “Create inline policy” and choose “JSON” in the “Policy editor” section. Paste the following IAM policy in there. Finally, create the policy and assign it a name.

Make sure you replace the {BUCKET-NAME}, {KEY-REGION}, {ACCOUNT-ID} and {KEY-ID} with the correct values.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "ListBuckets",
            "Effect": "Allow",
            "Action": "s3:ListAllMyBuckets",
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "s3:ListBucket",
                "s3:GetBucketLocation"
            ],
            "Resource": "arn:aws:s3:::{BUCKET-NAME}"
        },
        {
            "Sid": "WritePermissionsOnBucket",
            "Effect": "Allow",
            "Action": [
                "s3:PutObject",
                "s3:PutObjectAcl",
                "s3:GetObject",
                "s3:GetObjectAcl",
                "s3:DeleteObject"
            ],
            "Resource": "arn:aws:s3:::{BUCKET-NAME}/*"
        },
        {
            "Sid": "AccessToTheKey",
            "Effect": "Allow",
            "Action": [
                "kms:Encrypt",
                "kms:Decrypt",
                "kms:GenerateDataKey",
                "kms:GenerateDataKeyPair",
                "kms:GenerateDataKeyWithoutPlaintext",
                "kms:GenerateDataKeyPairWithoutPlaintext",
                "kms:GenerateRandom",
                "kms:GetKeyPolicy"
            ],
            "Resource": [
                "arn:aws:kms:{KEY-REGION}:{ACCOUNT-ID}:key/{KEY-ID}"
            ]
        }
    ]
}

1.6. Setup and configure an EC2 instance

1. Create a Nitro-capable EC2 instance by selecting “Launch instances” from the EC2 “Instances” page.
   Enter its name and choose the Amazon Machine Image (AMI) “Amazon Linux 2023 AMI” with 64-bit (x86) architecture.

2. In the “Instance type” section, select c5.xlarge (4vCPUs & 8GB RAM) or c5a.xlarge if the former is not available in your region.
3. In the “Network settings” section, set where to allow SSH traffic from. We recommend restricting access as much as possible.
4. In the “Advanced details” section:
   1. IAM instance profile: select the IAM Role you created in the previous steps.
   2. Nitro Enclave: select “Enable”. Note that this field is grayed if you selected an instance type that is incompatible with Nitro.
   3. Metadata version: ensure to select “V2 only (token required)”.
   4. Metadata response hop limit: ensure it is kept to a minimum of 2 (two).

When you’re done, launch the instance.

1.7. Additional security recommendations

It is highly recommended to control user and network access to your AWS environment and EC2 instance by properly configuring your VPC and security groups. Learn more about controlling network traffic in the AWS documentation.

See API Co-signer security checklist and recommended defense and monitoring systems for further information.

---

Step 2: Add a Co-signer to the workspace using an API user

Follow the instructions to add a new Co-signer to the workspace. Ensure you copy to your clipboard the following items, which you will use during the installation process:

• The API user's pairing token
• The download link of the Co-signer's installation script

---

Step 3: Install and connect the Co-signer to the workspace

Note: You must have root privileges on the EC2 instance to install the Co-signer. Ensure you are logged in as a root user or use sudo to execute the installation commands.

3.1. Download and unpack the installation package

Using the download link of the AWS Nitro Co-signer installation package you copied from the Console, run the wget command to download the package directly to your machine.

Paste the appropriate URL into the following command:

wget -O nitro-cosigner.tar.gz "URL"

Unpack the installation package by running the following command:

tar -xzf nitro-cosigner.tar.gz

3.2. Run the installation script

The installation package contains an Enclave Image File (EIF) and installation scripts. To install the Co-signer, navigate to the directory where the installation package was unpacked and run:

./install.sh

You will be prompted to enter the following parameters:

• Pairing token: enter the API user’s pairing token that you copied from the Fireblocks Console. This token pairs the API user with the Co-signer, establishing the connection between the Co-signer and the workspace.
• S3 bucket name: enter the name of the S3 bucket that you created before
• CMK ARN: enter the Amazon Resource Name (ARN) of the CMK that you created before

At this stage, you will have the option to configure the Callback Handler parameters for the API user connecting the Co-signer to the workspace. This feature is optional. You can configure it later through the Console, APIs, or locally from the Co-signer's host machine.

For detailed instructions on setting up your Callback Handler's interface to the Co-signer and implement its logic and code, refer to the Setup API Co-signer Callback Handler section.

Once the installation is complete, the Co-signer will automatically start running.

3.3. Approve MPC key shares for the API user

If the API user used to pair with the Co-Signer and connect it to your workspace has an Admin or User role, the workspace owner will receive a notification. This notification will prompt them to approve a new MPC key share request for that API user using the Fireblocks mobile app.

You can now see the Co-signer you installed in the Co-signers tab within the Console's Developer Center. Observe it is online and that the API user is paired to it.

---

ℹ️

To check the Co-signer's status and observe the logs, see the AWS Nitro Co-signer Maintenance article.

---