Control-plane security

Updated at:

Control-plane processes include function permission control and the operations that add, delete, modify, and query code and configurations. These processes mainly cover the secure transmission and storage of function metadata, code, layers, and image caches. This topic describes the control-plane security assurance types of Function Compute.

Permission control is secured by the Alibaba Cloud Resource Access Management (RAM) service

  • Event source triggering: You must create a trigger for an event source and grant the trigger the required execution permissions before it can trigger function execution.

  • Cloud service access: When you access other cloud services, such as Object Storage Service (OSS), Simple Log Service (SLS), and Tablestore, you must grant the required access permissions.

  • RAM user (sub-account) authorization: By using the RAM service, Function Compute supports granting different function operation permissions to RAM users (sub-accounts).

  • Cross-account authorization: By using the RAM service, Function Compute supports granting different function operation permissions to other accounts.

Function metadata is secured by encryption in transit and encryption at rest

  • Function Compute APIs and internal communications both use TLS 1.2 or later to encrypt content in transit.

  • Function metadata is stored as AES256 ciphertext. During use, the decrypted metadata is cached for no more than 600 seconds.

Code and layer caches are secured by isolation, controlled access, and encryption in transit

When you create or update a function, you upload code to Function Compute by using methods such as OSS synchronization or API upload. Function Compute uses an isolated account to cache the code or layers in Object Storage Service. When a function instance is initialized, Function Compute requests a temporary download URL and downloads the code or layers to the execution environment. Virtualization isolation ensures that a function instance can access only its own code and configured layers.

With valid authentication, you can use methods such as API calls, the console, or tools to obtain a temporary download URL and download the code or layers yourself.

All transfers of code or layers within Function Compute are encrypted by using TLS 1.2 or later.

Image caches are secured by isolation, controlled access, and encryption in transit

When you upload container images to Function Compute, the images are cached in Container Registry (ACR) through an isolated account. Only that account has the permissions to download the images. When a function instance is initialized, Function Compute downloads the container images by using the TLS 1.2 or later encryption protocol.