Automation 360 Cloud FAQs
Answers to frequently asked questions (FAQs) and related information about Automation 360 Cloud provide insight into various aspects.
- Where can I find an overview of Automation 360 Cloud security?
- An overview and details about Automation 360 Cloud security can be found in this document, Automation 360 Cloud Security and Data Privacy.
- How can a customer start using Automation 360 Cloud?
- The prerequisites and additional, optional steps for getting started can be
found on the Automation Anywhere docs portal at the following location: Introduzione a Automation 360 Cloud.
For most customers, the basic requirement is to allow secure access, using HTTPS, to their new Control Room environment hosted on Automation 360 Cloud. If this is not already enabled, you need to open port 443 in your firewall to allow outward HTTPS communication from your browser and the Bot agent to the Control Room. After the Bot agent is installed, it establishes a web socket connection to the Control Room. No ports need to be open on the customer site for these inbound connections.
- Does Automation 360 Cloud provide a service level agreement (SLA) for service availability?
- Yes, an SLA for 99.9% monthly availability is provided for the customer's access to their production Control Room environment. The SLA does not include planned down time for maintenance and updates to the service. If a customer believes that the SLA has not been met, a service credit can be claimed through Support. Details can be found in our Availability Service Level Terms.
- How does Automation 360 Cloudsupport high availability (HA)?
- Each customer’s Automation 360 environment is deployed using application load balancing across highly available public Cloud infrastructure services. The infrastructure services support both microservices running on Docker containers in Kubernetes clusters and datastores (database, cache, logging, file system, storage) supporting HA across multiple zones within a region. Both AWS and GCP public clouds are used.
- Does Automation 360 Cloud support disaster recovery (DR)?
- Yes, Automation 360
Cloud supports DR. In case of major incidents where
imminent resolution seems unavailable, a disaster situation is declared and
all the tenants within the region affected by the incident are failed over
to another, remote region. The current objectives for this recovery are as
Nota: RPO is based on backups taken and pushed to another backup region.
- Recovery Time Objective (RTO)
- The time taken to get a new region up and running with the last backup data restored is six hours.
- Recovery Point Objective (RPO)
- The maximum duration for data loss during a restore is six hours.
- Are there maintenance windows for the Automation 360 Cloud?
- Yes, Automation Anywhere updates Automation 360
Cloud once every three months so that customers will
receive automatic and regular updates to the latest software version. For
more information, see Products and Services Lifecycle Policy.
The primary channel for communicating the timing of Cloud status and maintenance windows is the Automation 360 Cloud Service Status site. You can subscribe to this website and receive the updates. Note that you cannot choose when the updates are rolled out across the multi-tenant Cloud. The Automation 360 architecture is designed to allow these timeless updates to roll out without affecting customers’ botdevelopment life cycles.
- What actions should a customer take to plan for an Automation 360 maintenance window?
- A customer’s bot operations should take account of scheduling bots to run outside of the publis