All Products
Document Center


Last Updated: Aug 31, 2018

fcli is a powerful command line tool that helps you manage your Function Compute resources conveniently.

You can click here to download fcli. After the installation, you can run fcli shell to go to the shell mode and complete the initial configurations.

  1. fcli shell
  2. Please input the endpoint (example:
  4. Please input the access key id:
  5. fakeaccesskeyid
  6. Please input the access key secret:
  7. fakeaccesskeysecret
  8. Store the configuration in: /Users/testuser/.fcli
  9. Welcome to the function compute world. Have fun!


  • The account ID can be obtained in the console.

  • If you do not have a valid AccessKey, you can create one in RAM. You can use the AccessKey of the primary account, but this action is not recommended.

You can run the help command to view available commands.

  1. >>> help
  2. Commands:
  3. attach attach the policy to a role
  4. cd change the current resource
  5. clear clear the screen
  6. config config the fcli
  7. detach detach the policy from a role
  8. exit exit the program
  9. grant grant the permission
  10. help display help
  11. info display the resource detail info
  12. invk invoke the function
  13. logs display the service/function logs
  14. ls list the child resources of the current resource
  15. mkf create the function
  16. mkir create the invocation role
  17. mkl create the log project and store
  18. mkrp create the ram policy
  19. mks create the service
  20. mksr create the service role
  21. mkt create the trigger
  22. pwd display the current resource
  23. rm delete the resource
  24. sbox a sandbox environment for installing the 3rd party libararies and trouble shooting
  25. upf update the function
  26. ups update the service
  27. upt update the trigger

For every command, you can run cmd --help to view detailed help information. For example, you can run mks --help which will print out the detailed help info.

  1. >>> mks --help
  2. -d, --description string service description
  3. --etag string service etag for update
  4. --help
  5. -p, --log-project string loghub project for logging
  6. -l, --log-store string loghub logstore for logging
  7. -g, --nas-groupid int32 group id to access NAS volume (default -1)
  8. --nas-mount-dir stringArray at least one nas dir is required to enable the NAS access
  9. --nas-server-addr stringArray at least one nas server is required to enable the NAS access
  10. -u, --nas-userid int32 user id to access NAS volume (default -1)
  11. -r, --role string role arn for oss code copy, function execution and logging
  12. --security-group-id string security group id is required to enable the vpc access
  13. --v-switch-ids stringArray at least one vswitch id is required to enable the vpc access
  14. --vpc-id string vpc id is required to enable the vpc access

In the Service Management, Function Management, and Trigger Management documents under the Developer guide, you can learn about more detailed descriptions and examples. If you have any questions, go to the project for a discussion.