Document
Library

User Guide

Overview
What's new
Contracts
- Licenses purchased from Fortinet
- FortiFlex
- Subscribing on Public Cloud Marketplace
Two-Factor Authentication
Getting started
- Onboarding applications
- Example: Changing DNS records on AWS Route 53
- Changing IP addresses of origin servers
- Restricting direct traffic & allowing FortiWeb Cloud IP addresses
- How does FortiWeb Cloud choose regions?
- CDN
- Understanding block mode and action
Global settings
- Application management
- Templates
- Admin management
- Role management
- Settings
- Contracts
- Cloud Connectors
- Custom block pages
- Audit logs
- Reports
- Usage
Threat Analytics
- Threat Analytics
- Attack logs
- Gateways
Log Settings
Configuring network
- Origin Servers
- Endpoints
- Supported cipher suites & protocol versions
WAF modules
- How to add or remove a module
- Security Rules
- Client Security
- Access Rules
- Bot Mitigation
- DDoS prevention
- Advanced Applications
  - Custom Rule
  - WebSocket Security
- API Protection
- Application Delivery
- Global Trustlist
Vulnerability Scan
FortiView
Using FortiWeb Cloud with DevOps tools
- Configuring FortiWeb Cloud with Terraform
- Configuring FortiWeb Cloud with Ansible
- Configuring FortiWeb Cloud with Jenkins
Use cases
- Using FortiWeb Cloud behind a Content Distribution Service
- Network settings for applications serving different content over HTTP and HTTPS
- FortiWeb Cloud and Splunk
- Fortinet Security Fabric
- Managing External IdP roles in FortiCloud IAM
- Frequently used regular expressions
Best practices
- Using Dashboard to monitor important notices
- Utilizing FortiView to reduce false positives
- Setting up a secure environment
- How to block the ongoing DDoS attack
Maximum configuration values
Sequence of scans
Supported cipher suites & protocol versions
FAQs
- Onboarding applications
- Network
- Security
- Logs
- Subscriptions and Contracts
- Cost and Billing
- Accounts
- Miscellaneous
Contacting customer service

Home FortiWeb Cloud User Guide

Migrating to IAM user

Migrating to IAM user

FortiWeb Cloud will cease to support Sub-user and Admin (Legacy) accounts starting from version 24.2.a, which is scheduled for release in June 2024. To ensure uninterrupted access, kindly migrate Sub-user and Admin (Legacy) to IAM user in advance. Failure to do so may result in users losing access to FortiWeb Cloud.

For how to migrate, refer to Migrating sub users.

For Admin (Legacy) accounts, if they don't appear in the active sub-users list, you should create an IAM user as needed. See Adding IAM users.

Please be aware that Sub-user and Admin (Legacy) accounts have their permissions currently configured under Global > Administrators > Role Management. However, upon migration to FortiCloud, these permissions will be managed by FortiCloud through permission profiles. Therefore, it's essential to create the appropriate permission profiles for them in FortiCloud. For how to create permission profiles in FortiCloud, see Permission profiles.

Previous

Next

Migrating to IAM user

FortiWeb Cloud will cease to support Sub-user and Admin (Legacy) accounts starting from version 24.2.a, which is scheduled for release in June 2024. To ensure uninterrupted access, kindly migrate Sub-user and Admin (Legacy) to IAM user in advance. Failure to do so may result in users losing access to FortiWeb Cloud.

For how to migrate, refer to Migrating sub users.

For Admin (Legacy) accounts, if they don't appear in the active sub-users list, you should create an IAM user as needed. See Adding IAM users.

Please be aware that Sub-user and Admin (Legacy) accounts have their permissions currently configured under Global > Administrators > Role Management. However, upon migration to FortiCloud, these permissions will be managed by FortiCloud through permission profiles. Therefore, it's essential to create the appropriate permission profiles for them in FortiCloud. For how to create permission profiles in FortiCloud, see Permission profiles.

Previous

Next