Yes, when using the AWS deployment option, SailPoint shares an Amazon Machine Image (AMI) with the customer’s AWS account in the selected region. This AMI contains the pre-configured Virtual Appliance (VA) image that the customer can use to deploy within their own AWS environment, simplifying the deployment process and ensuring compatibility with AWS services.

Key Reference from SailPoint Documentation:

AWS AMI for VA Deployment: SailPoint provides a dedicated AMI that is shared with customers in their chosen AWS region to facilitate the deployment of the Virtual Appliance.

The provided use case incorrectly describes the provisioning process on a source that has provisioning disabled. If provisioning is disabled for a source, automated provisioning via the Virtual Appliance and connectors is not possible. The Virtual Appliance cannot retry or carry out the provisioning in this case, as the system explicitly prevents automated provisioning operations on sources marked as non-provisionable.

When a source has provisioning disabled, the system only supports manual provisioning , where a task is opened in IdentityNow for a person to manually execute the provisioning steps. The Virtual Appliance does not handle provisioning for disabled sources, so the described scenario where it retries the request and carries out provisioning is inaccurate.

References:

SailPoint IdentityNow Provisioning Configuration Guide.

SailPoint IdentityNow Virtual Appliance and Connector Operations Documentation.

No, microservice architecture does not inherently make identities take up less space in the cloud. Microservices are primarily focused on improving scalability, resilience, and modularity by breaking down an application into smaller, independent services. While this architecture may optimize resource usage and improve performance, it does not specifically reduce the storage space required for identities or data. Data storage concerns are more related to optimization techniques like data deduplication or compression rather than the architecture style itself.

References:

SailPoint IdentityNow Microservices Architecture Guide.

SailPoint IdentityNow Cloud Storage and Data Management Documentation.

The /home/sailpoint/config.yaml file is not used to configure the Virtual Appliance (VA) to use a static IP address. This file is generally used for other configuration purposes related to the SailPoint IdentityNow application settings, not for network configurations like setting static IP addresses. Network configurations are handled at the system or network service level within the VA ' s Linux environment.

References:

SailPoint IdentityNow Virtual Appliance Configuration Guide.

SailPoint IdentityNow Networking Configuration Documentation.

No, IdentityNow administrators do not have the option to choose how often updates to their tenant occur. SailPoint operates a multi-tenant SaaS model , where updates are rolled out centrally by SailPoint on a predefined schedule. SailPoint controls and manages updates to ensure consistency and security across all tenants. This means that all tenants receive updates automatically as part of SailPoint’s continuous delivery model, without the ability for individual admins to control or delay updates.

References:

SailPoint IdentityNow SaaS Release Management Guide.

SailPoint IdentityNow Multi-Tenant Environment Overview.

https://identityNowacme.com is not typically considered a vanity URL. While it includes the " identityNow " term, it does not appear to follow the format of a vanity URL, which generally includes a company-specific subdomain (like my) and a custom domain (example.com). In this case, the URL is more generic and lacks the branding or simplicity typically associated with vanity URLs.

Key Reference from SailPoint Documentation:

Vanity URL Structure in IdentityNow: Vanity URLs typically feature a customized subdomain that reflects the organization’s branding, and identityNowacme.com does not fit this pattern.

Yes, IdentityNow releases are controlled and coordinated by SailPoint. SailPoint manages the software release cycle for IdentityNow, which follows a SaaS (Software-as-a-Service) delivery model. This means updates, new features, patches, and other improvements are automatically rolled out by SailPoint without requiring manual intervention by customers. The release schedule is typically structured around planned maintenance windows and communicated to customers in advance. SailPoint ensures these updates are deployed securely and efficiently to all tenants.

References:

SailPoint IdentityNow SaaS Release Management Guide.

SailPoint IdentityNow Product Updates and Release Notes.

Testing connectivity from the virtual appliance (VA) to the source is a crucial troubleshooting step when dealing with connection issues such as timeouts. This can be done by accessing the VA and performing network tests (e.g., ping, telnet, or curl commands) to verify that the VA can communicate with the source over the required network paths. Ensuring that the VA has network access to the source can help identify if the problem is related to network configuration or firewall restrictions.

Key Reference from SailPoint Documentation:

VA to Source Connectivity Testing: Verifying network connectivity between the VA and the source is a fundamental step in diagnosing connection issues, as outlined in SailPoint’s troubleshooting guidelines.

Turning off the Virtual Appliance’s (VA) internal firewall is not recommended as a standard troubleshooting step in SailPoint IdentityNow. The VA’s firewall is crucial for maintaining the security of the environment, and disabling it can expose the system to unnecessary risks. Instead, an IdentityNow engineer should verify the VA’s network configuration and ensure that the required ports are open for communication between the VA and the source.

Key Reference from SailPoint Documentation:

VA Configuration and Network Troubleshooting: Troubleshooting connection issues typically involves checking network connectivity and firewall rules, not turning off the internal firewall.

No, IdentityNow administrators do not have the option to choose how often updates to their tenant occur. As part of SailPoint’s multi-tenant SaaS platform, updates are managed and controlled by SailPoint and are pushed out automatically to all tenants. Administrators do not have the ability to schedule or defer updates, as this ensures all customers are running on the latest and most secure version of the software.

References:

SailPoint IdentityNow SaaS Release and Update Policy.

SailPoint IdentityNow Multi-Tenant Environment Overview.