Jay-Rajput/oci_data huggingface dataset:
Configuring Private Networks


You can configure Anomaly Detection to access data sources hosted in private networks.

By configuring data OCI to access a private network, you can:

Connect to OCI data sources that are only accessible privately.
Connect to on-premises data sources that are connected to an OCI Virtual Cloud Network (VCN) using Site-to-Site VPN or FastConnect.
 Note

You can access on-premises or private data sources in Anomaly Detection using their Fully Qualified Domain Name (FQDN). The FQDN must have an A record in the configured DNS server and must not be an Oracle reserved public domain, such as oracle.com or adb.oracle.com. Valid FQDN examples: wxyz.adb.oracle.com and <hostname>.<subnet DNS label>.<VCN DNS label>.oraclevcn.com.

To enable data assets to access a private network, you must:

Create a private endpoint for your data asset.
Use the private endpoint when you create a data asset.

Ensure that you have created the required Anomaly Detection service policies.

You can perform the following private endpoint tasks:

Creating a Private Endpoint
Viewing Private Endpoints
Getting Private Endpoint Details
Editing a Private Endpoint
Deleting a Private Endpoint
Moving a Private Endpoint Between Compartments
Set Up Users, Access Roles, and Permissions

Use Oracle Identity Cloud Service for Authentication
Use Identity and Access Management Identity Domains for Authentication
Assigning Roles for the Oracle Blockchain Platform Network and REST APIs
Using Permissions and Policies to Administer Oracle Blockchain Platform
Web Application Firewall
 Network Address List
Log Group Management


Learn about how to create and manage log groups.

You can perform the following log group tasks:

Creating a Log Group

Listing Log Groups

Getting a Log Group's Details

Editing a Log Group

Moving a Log Group Between Compartments

Tagging a Log Group

Deleting a Log Group
Matching Events with Filters

Background
Event Matching with Filters
Examples of Simple Filters
Examples of Filters with Event Payload Attributes
Examples of Arrays in Filters
Examples of Wildcard Matching in Filters
Pretrained Models


Learn about the Language service pretrained models.

Single Requests

A record can be up to 1,000 characters. We encourage you to use Batch Requests that support records up to 5,000 characters and support more than one record in a single request.

There's no minimum number of characters that must be provided, but the output quality is highly dependent on the amount of information provided to the models.

Batch Requests

A batch can have up to 100 records.

A record can be up to 5,000 characters long.

The total number of characters to process in a request can be up to 20,000 characters.
Extreme Reliability

Phase 1: Distribute Instances Across Fault Domains
Phase 2: Deploy Resources in Multiple Regions
Explore More
Access to Microsoft Azure

Highlights
Availability
Overview of Supported Traffic
Important Implications of Connecting Clouds
Setting Up a VNet-to-VCN Connection
Managing a VNet-to-VCN Connection
Resizing a Volume

Required IAM Policy
Online Resizing of Block Volumes Using the Console
Offline Resizing of Block Volumes Using the Console
Network Performance

Testing Methodology
Signing In to an Identity Domain Using an Alternative Login Method


If you’ve set up more than one 2-step verification method or at least one 2-step verification method and a bypass code, then you can switch to an alternative login method when you can’t use your default.

Before You Begin:

Set up more than one 2-step verification method. Or, set up one 2-step verification method and generate a bypass code. To learn how to set up 2-step verification and generate a bypass code, see Setting Up Account Recovery and 2-Step Verification.

Use an alternative login method when your default method isn’t available. For example, if you don’t have your phone with you but you do have your bypass code, use the bypass code as an alternative login method to verify your identity.

To use an alternative login method, complete the following steps:

Enter your username and password in an MFA-protected environment.
Click Show alternative login methods.
All 2–Step Verification methods that you're enrolled in and a bypass code option (if you’ve set a bypass code) appear in the Alternative login methods section.
Select a different verification method.
Enter the required verification.
Select the Make this my default method check box to set this 2-Step Verification method as your default. The next time that you log in, you are prompted to verify your identity using this method of verification.
Listing Vantage Points

Sample List
Synchronize Query Server with Hive

Synchronizing Query Server using the PL/SQL API
Enabling Query Server Full Synchronization
Applications Environment Management

Get Started
Learn about environment management concepts
Plan an environment
Get started with a new subscription
Support
Get help and contact Support
Create a service request
Manage Environments
Create an environment
View the status of your environment
Access the application service console
Community
Oracle Cloud Infrastructure blog
Cloud infrastructure community forum
Manage Access
Learn about policies
Add a group and policy
Add users
Troubleshooting
Troubleshoot applications environments
Managing Approved Senders


Learn about managing approved senders using the Email Delivery service.

An approved sender must be set up for all “From:” addresses sending mail through Oracle Cloud Infrastructure, or mail is rejected. An approved sender is associated with a compartment and only exists in the region where the approved sender was configured. That is, if you create an approved sender in the US West (Phoenix) region, you cannot send email through the US East (Ashburn) region with that sender.

Use of multiple addresses in the email From header is discouraged. If you use multiple addresses, it increases the possibility that your mail is placed in a spam folder or discarded (because of DMARC From alignment rules). The performance of your emails is reduced because all addresses have to be authorized as approved senders. A best practice for the SMTP envelope From address is to match the header From address when you submit mail to Email Delivery. If you use mismatched addresses, it reduces the performance of your emails because both addresses need to be authorized as approved senders. Certain future platform features will not be available if you use mismatched addresses.

The approved senders that you add must use a domain name that you own and control. The following sending domains cannot be used to create approved senders:

@oracle.com - This sending domain name is reserved for Oracle employee and corporate system use.
@*.oraclevcn.com - This domain name is reserved for private use within an Oracle Cloud Infrastructure VCN. Email sending domains must have SPF and DKIM records that can be resolved on the public internet, and oraclevcn.com is only reachable within private Oracle Cloud Infrastructure networks. Use of this sending domain results in delivery delays, failures, and a possible blocklist addition.
@gmail.com, @hotmail.com, @yahoo.com, and other public mailbox service providers - You cannot use a sending domain from a public mailbox service provider such as gmail, hotmail, icloud, yahoo, and so on. These providers tend to have restrictive DMARC records and will not delegate permission to third-party Email Delivery services (through SPF and DKIM records). Use of these sending domains results in delivery delays, failures, and a possible blocklist addition.

The following sending domain is problematic for use as an approved sender:

@oraclecloud.com - This sending domain name is reserved for Oracle Cloud system use.

Approved senders should not be created in the root compartment. If approved senders exist in the root compartment, you are required to create a policy to manage approved senders in the entire tenant. Creating approved senders in a compartment other than the root allows the policy to be specific to that compartment.

You can perform the following approved senders management tasks:
Creating an Approved Sender
Deleting an Approved Sender
Moving an Approved Sender
Managing Tags for an Approved Sender
Searching for Artifacts in Artifact Registry

Using the Console
Artifact Registry Events

Repository Events
Artifact Events
References for Using the Events Service
Enterprise Architecture

Next Steps
Overview of Oracle Cloud Migrations

Oracle Cloud Migrations Terminologies
Tenancy Resources Used in Migration
Accessing Oracle Cloud Migrations
Regions and Availability Domains
Limits and Quotas in Oracle Cloud Migrations
Getting Started
 With MySQL HeatWave Service
Security Best Practices
Supporting Documentation
Tutorials



For more information click here https://docs.oracle.com/en-us/iaas/Content/cloud-marketplace/what-do-i-need-to-know-to-get-started.htm#what-do-i-need-to-know-to-get-started

For more information click here https://docs.oracle.com/en-us/iaas/mysql-database/doc/getting-started.html

For more information click here https://docs.oracle.com/en-us/iaas/Content/document-understanding/using/getting_started.htm#getting_started

For more information click here https://docs.oracle.com/en-us/iaas/Content/data-labeling/using/getting-started.htm

For more information click here https://docs.oracle.com/en-us/iaas/Content/bigdata/get-started.htm

For more information click here https://docs.oracle.com/en-us/iaas/access-governance/doc/getting-started.html

For more information click here https://docs.oracle.com/en-us/iaas/Content/API/SDKDocs/ansiblegetstarted.htm#Getting_Started_with_Oracle_Cloud_Infrastructure_and_Ansible
Managing Policies

Required IAM Policy
Tagging Resources
Working with Policies
Writing Policy Statements with the Policy Builder
Using the Console
Using the API
Implementing Cloud Advisor recommendations


This section describes how to implement recommendations using fix-it flows in Cloud Advisor. It contains procedures to complete the following tasks:

Required IAM policies
Resource Actions
Managing Recommendations
Viewing Recommendation History
Managing Work Requests
Recommendation Strategies
 Note

For manual implementation instructions, see Implementing the Recommendation in the descriptions of each recommendation in Categories and Recommendations.
Frequently Asked Questions About Cloud Security Testing

Do I need Oracle’s permission for all penetration and vulnerability tests?
How can I notify Oracle for penetration and vulnerability tests?
Which instances can I test?
What other actions on my part are required after I receive an authorization to perform my tests?
What do I do when I believe that I have discovered a potential security issue related to Oracle Cloud?
What limitations do I need to be aware of regarding my tests?
Can I conduct any tests that may exceed the bandwidth quota for my subscription?
Can I use my hosted instances to conduct assessments against other services not hosted by Oracle?
Creating a Snapshot


Create a snapshot of a File Storage file system. A snapshot is a point-in-time view of the file system.

After creation, snapshots are accessible under the root directory of the file system at ./snapshot/<snapshot_name>. If the snapshot is needed for only a limited time, you can add an expiration time. You can also create policy-based snapshots.
Console
CLI
API
Open the navigation menu and click Storage. Under File Storage, click File Systems.
In the List scope section, under Compartment, select a compartment.
Click the name of the file system that you want to take a snapshot of.
On the file system's details page, under Resources, click Snapshots.
Click Create Snapshot.

In the Create Snapshot dialog box, provide the following information:

Name: Enter a name for the snapshot. It must be unique among all other snapshots for this file system. The name can't be changed. Avoid entering confidential information.
To tag the snapshot, click Show tagging options.

If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, skip this option or ask an administrator. You can apply tags later.

Click Create.
Container Instances Shapes

Ephemeral storage
Adding Applications


You can add Custom Applications, if you're assigned to either the identity domain administrator role or the application administrator role.

See Assigning Users to Roles for information about assigning users to administrator roles.

You can add the following types of custom applications in IAM:

App Catalog application: Add an application from the Application Catalog, which contains pre-configured application templates.

Security Assertion Markup Language (SAML) application: Accessed by multiple users and hosted in a secure and protected place (server). Create a SAML application that supports SAML for single sign-on. This allows users to single sign-on (SSO) into your software as a service (SaaS) applications that support SAML for SSO.

Mobile application: Hosted directly on the resource owner's browser, machine, or mobile device. An example of this type of application is an Android or iPhone application. A mobile application can run in multiple environments outside of your control. Since these environments aren't trusted, this type of application has reduced integration options.

Confidential application: Accessed by multiple users and hosted in a secure and protected place (server). The application uses OAuth 2.0. Applications that can protect their OAuth client id and client secret are called confidential applications

Enterprise application: Web applications that require App Gateway to integrate with IAM for authentication purposes. App Gateway passes HTTP headers to the application after authenticating and authorizing user's access.

 Tip



You can access the Onboarding Applications infographic to see how to add custom applications in IAM.

You can access the Integrating a Custom Client Application tutorial to see how to integrate a custom client application with IAM.

You can access the Integrating a Custom Resource Server Application tutorial to see how to integrate a custom resource server application with IAM.

See Manage IAM App Gateways for information on integrating an enterprise application with IAM.
Vault
 learning videos
Email Delivery Metrics


Monitor the health, capacity, and performance of the Email Delivery service by using metrics, alarms, and notifications.

This topic describes the metrics emitted by the metric namespace oci_emaildelivery (the Email Delivery service).

Oracle Cloud Infrastructure Email Delivery (Email Delivery) is an email sending service that provides a fast and reliable managed solution for sending high-volume emails that need to reach your recipients' inbox. Email Delivery service metrics help you measure counts for emails accepted, emails relayed, email complaints, emails hard bounced, and emails soft bounced.

Emails Accepted: Emails accepted consists of the unique emails accepted and sent by the Email Delivery service. Emails are defined by the number of unique emails and the number of unique recipients per message attempted to be delivered, resulting in successful delivery and blocked email. For example, sending an email with 10 recipients means 10 emails accepted.
Emails Relayed: Emails relayed consists of the number of emails that the Email Delivery service has successfully transferred to a recipient domain. The recipient domain has accepted responsibility and will typically deliver these emails, but can still choose to discard, quarantine, or bounce. A single email may be both relayed and bounced.
Emails Hard Bounced: Hard bounces occur when a mailbox provider provides a signal that the email address you have tried to send to is not valid. Most often, this happens because the email address does not exist. You should not try to send an email to hard bounced address again in the future. The emails hard bounced metric consists of the number of emails hard bounced (permanent failure) for a sender by the recipient domain's email service.
Emails Soft Bounced: Soft bounces are messages from a mailbox provider that provide a signal that the email address you have tried to send to is not valid for the time being. Usually, a message soft bounces when the inbox is full or cannot be reached. You can try to send an email to soft bounced address again in the future. The emails soft bounced metric consists of the number of emails soft bounced (persistent transient failure) by the recipient domain's email service or because of an inability to reach that service.
Email Complaints: Email complaints consists of the number of email complaints for a sender by the Email Delivery service.
Emails Suppressed: Emails suppressed consists of the number of emails suppressed by the Email Delivery service.
 Note

Email Delivery is billed for every 1,000 emails accepted.
Mount Command Fails

Missing network security rules
Network peering configuration incorrect
Missing export option
Export option disallows instance
Mount command is incorrect or includes a typo
Mount command using an FQDN fails, but succeeds with an IP address
A third-party security module on the instance restricts NFS mounting
Using Health Checks


Learn how the OCI users can work with self-service Health Checks to validate their environment health.

To use Health Checks:

In the dashboard, click the hamburger menu (three horizontal lines) at the top-left corner.
From the navigation pane, click Health Checks.
In the Health Checks page, click Create Execution.
In the Create Execution page, select the Service from top banner.
Select the Environment where health checks need to be performed. This list is populated with all the environments associated with the support identifier (SI).
For Health Check Type, select any of the following:
Application and Database Servers
Database Servers
Application Servers
Click Customer Note to add an action plan or any other relevant information you want included in the RFC.
Click Next.

The Schedule Execution pop-up opens. Provide the timestamp and the health checks can be scheduled after 15 minutes of the current time.

Click Submit.

The execution is scheduled and the details can be seen on the health checks main page.
About Application Performance Monitoring


Businesses depend on their applications to deliver core business processes. As emphasis shifts to remote and online access, accuracy, speed, and consistency become paramount. These dynamics call for proactive steps to ensure that online customers can successfully access information and complete transactions in a timely manner. The Oracle Cloud Infrastructure Application Performance Monitoring service provides deep visibility into the performance of applications and provides the ability to diagnose issues quickly in order to deliver a consistent level of service. This includes the monitoring of the multiple components and application logic spread across clients, third-party services, and back-end computing tiers, on premises or on the cloud.

Here's a diagram that provides an overview of the Application Performance Monitoring service in Oracle Cloud Infrastructure, its features and components, and the other Oracle Cloud Infrastructure services it works with:

Here are the features of Application Performance Monitoring:

Distributed Tracing: Collects and processes transaction instance trace data using Application Performance Monitoring data sources, open-source tracers, or directly using API. Distributed Tracing monitors transaction performance, volume, and error rate and notifies you of issues. It analyzes load, usage patterns, performance, and capacity across out-of-the-box and custom dimensions.
Synthetic Monitoring: Evaluates the availability of your application by testing it periodically from multiple vantage points. This ensures the early detection of availability and systemic performance issues. Synthetic Monitoring also provides deep transaction visibility by correlating monitor execution results to collected traces.
Real User Monitoring: Provides an insight into the experience of the end user directly from the browser. Real User Monitoring identifies performance degradation by monitoring page load time and user action. It enables complete end-user support by tracking user sessions.
Server Monitoring: Collects performance and usage metrics from monitored application servers. Server Monitoring provides alerting and charting capabilities by integrating with the Oracle Cloud Infrastructure Monitoring service.

In addition, you can use the Oracle-defined dashboards provided with Application Performance Monitoring for a comprehensive view of the performance and availability of your applications and end-user experience in real time.
Detaching a Boot Volume

Required IAM Policy
Using the Console
Using the API
Creating a Model


Create and then train a model in Anomaly Detection.

Console
CLI
API

You can create the model in an existing project or create a project for it.

Open the navigation menu and click Analytics & AI. Under AI Services, click Anomaly Detection.
In the left-side navigation menu, click Projects.
Select the compartment that contains the project that you want to use, or select the compartment that you want to create a project in.
Perform one of the following actions:
To use an existing project, click its name.
To create a new project, click Create Project.
On the project's details page, click Create and train model.
Select an existing data asset if any exist or click Create a new data asset.
Click Next.
On the Train model page, select the compartment to create the model in, and then enter an optional name and description for the model. If you don't provide a name, one is automatically generated.
For Target false alarm probability(FAP), specify a value 0 to 0.05.

FAP indicates model performance. Lower FAP indicates better model performance.

For Training fraction ratio, specify a value 0.5 to 0.8.

Training fraction ratio indicates the split ratio between training data and validation data.

(Optional) For Algorithm Hint, specify one of the hints to know what type of algorithm the model uses.
Perform one of the following actions:
To set the Window size, click Automatic window size, and then specify a value 1 to 100.
Let the service set the window size, click Automatic window size.
(Optional) Click Show advanced options to assign tags to the resource. Tags help you to easily find and track resources by selecting a tag namespace, and then entering the key and value.

To add more than one tag, click Add tag.

Tagging describes the various tags that you can use organize and find resources including cost-tracking tags.

Click Next.
Review the training data and model information. Use Previous to make any changes, and then return to the Review panel.
Click Create and train.
Training a model can take awhile. The page is automatically refreshed every 20 seconds.
Database Migration Policies

Creating a Policy
Analytics Cloud
 Community
Copyright © 2021, Oracle and/or its affiliates.
About Oracle
Contact Us
Legal Notices
Terms of Use & Privacy
Document Conventions
Cookie Preferences
Adding Multiple Authentication Servers to the same API Deployment

Using the Console to Add Multiple Authentication Servers to the same API Deployment
Editing a JSON File to Add Multiple Authentication Servers to the same API Deployment
Examples
Troubleshooting Data Labeling

File Content is not Displayed when Clicking a Record
Only Some Images are Saved to Object Storage
Only Some Saved Images are Available for Dataset Creation