Prerequisites
- A BIG-IP whose HTTPS management interface CloudThinker can reach. This connection runs from CloudThinker Cloud, so allow CloudThinker’s egress IPs on the management interface. These docs don’t publish the list: ask your CloudThinker contact, or contact us. F5 advises against opening the management interface to the internet, so see Reaching private services.
- A BIG-IP account with the Administrator or User Manager role, which can create user accounts.
- The Admin role in your CloudThinker workspace, which can add and edit connections. See Roles.
Setup
Create a dedicated user
- User Name:
cloudthinker - Password: enter and confirm a strong password
- Partition Access: the partitions agents should see, or All
- Role: Auditor for read-only access, or a role that can change the modules you want agents to manage. See Required permissions.
- Terminal Access: Disabled
Add the connection in CloudThinker
BIG-IP 17.1.1 connected; system inventory is readable. Provisioned modules: afm, ltm.Connection details
/Common/app-pool.
Required permissions
The BIG-IP user’s role and partition access set what agents can read and change.Agent capabilities
Verify the connection
/Common/app-vs.
Example prompts
Troubleshooting
The accordion titles below are the messages CloudThinker shows when the connection test fails.BIG-IP rejected the username or password. Repeated failures lock the account.
BIG-IP rejected the username or password. Repeated failures lock the account.
BIG-IP rejected token sign-in or system access. Check the user role and its authentication provider.
BIG-IP rejected token sign-in or system access. Check the user role and its authentication provider.
The user cannot read module provisioning. Give it read access to the BIG-IP system inventory.
The user cannot read module provisioning. Give it read access to the BIG-IP system inventory.
The management certificate is not trusted. Set Verify TLS certificate to No for a self-signed certificate.
The management certificate is not trusted. Set Verify TLS certificate to No for a self-signed certificate.
Could not reach the management address over HTTPS.
Could not reach the management address over HTTPS.
That address answered, but not as the BIG-IP iControl REST API. Use the management address root, with no path.
That address answered, but not as the BIG-IP iControl REST API. Use the management address root, with no path.
https:// and the management address.BIG-IP answered with a redirect. Use the exact management https address.
BIG-IP answered with a redirect. Use the exact management https address.
https:// management address, not an http:// address or a load-balanced name that redirects.Security
- Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
- Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
- Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
- Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
- Use a dedicated user. Give CloudThinker its own BIG-IP user with no terminal access, so you can audit and revoke it on its own.
- Short-lived tokens. CloudThinker exchanges the password for a temporary iControl REST token for each task and removes the token afterwards.
- Verify the certificate. Treat Verify TLS certificate: No as a setting for BIG-IP’s default certificate. Switch to Yes once the management interface has a trusted certificate.