Supply Chain Test Drive - Error/Wrong Permissions

The error you're encountering with the Supply Chain Test Drive feature in the AWS Management Console is likely due to a permissions issue related to the AWS Key Management Service (KMS) key.

Here are a few things you can try to resolve the issue:

Verify the KMS Key Policy:
    Ensure that the KMS key policy grants the necessary permissions for the Supply Chain Test Drive feature to access and use the KMS key.
    The guidelines for "Creating an Instance" typically refer to the permissions required for launching an instance, which may be different from the permissions required for the Supply Chain Test Drive feature.
    Review the KMS key policy and make sure it includes the required permissions for the Supply Chain Test Drive feature.

Check the KMS Key Availability:
    Verify that the KMS key used by the Supply Chain Test Drive feature is available and accessible in the eu-central-1 region.
    Ensure that the KMS key is not disabled or scheduled for deletion, as this could prevent the Supply Chain Test Drive feature from using it.

Verify the IAM User or Role Permissions:
    Check the permissions of the IAM user or role you're using to access the AWS Management Console and perform the Supply Chain Test Drive.
    Ensure that the IAM user or role has the necessary permissions to access and use the KMS key, as well as the permissions required for the Supply Chain Test Drive feature.
    You may need to review and update the IAM policies attached to the user or role.

Check for Service Limits or Quotas:
    Verify that you haven't reached any service limits or quotas in the eu-central-1 region that could be preventing the Supply Chain Test Drive feature from completing successfully.
    You can check the service limits in the Service Quotas service in the AWS Management Console.

Try a Different Region:
    If the issue persists in the eu-central-1 region, you can try using the Supply Chain Test Drive feature in a different region, such as us-east-1 or eu-west-1.
    Ensure that the necessary KMS key and IAM permissions are set up correctly in the new region.