Deploy Azure AI Services In Containers

By Ashwin Venugopal -

 






Introduction

Containers allow you to run Azure AI services either in your local environment or within Azure. For instance, if your application relies on sensitive information stored in an on-premises SQL Server to access an Azure AI service, you can implement Azure AI services in containers on the same network.

This ensures that your data remains within your local network instead of being transferred to the cloud. Furthermore, deploying Azure AI services in a local container will reduce latency between the service and your data, which can enhance performance.

Understand Containers

When you launch a software service, it needs to be placed in an environment that supplies the necessary hardware, operating system, and supporting runtime components required by the service. Azure AI services are offered as a cloud service, where the service software is maintained within an Azure data center that supplies the core runtime services, operating system, and hardware.

Additionally, some Azure AI services can be deployed within a container, which wraps the required runtime components and is subsequently hosted on a container host that provides the essential operating system and hardware.

What is a Container?

A container includes an application or service along with the essential runtime components required for its operation, while concealing the details of the operating system and hardware beneath. In reality, this abstraction leads to two major advantages:

  • Containers are portable across hosts, which may be running different operating systems or use different hardware - making it easier to move an application and all its dependencies.

  • A single container host can support multiple isolated containers, each with its own specific runtime configuration - making it easier to consolidate multiple applications that have different configuration requirement.

The software and configuration that a container must support are specified in the container image that encloses the container. You can keep a collection of images in your own registry or save them in a central registry like Docker Hub.

Container Deployment

In order to use a container, you usually need to specify any necessary configuration parameters, pull the container image from a registry, and deploy it to a container host. The container host may be located on your local computer, in a private network, or in the cloud.

Conclusion

We have successfully learnt some basics about containers.

 


Comments

Post a Comment

Popular posts from this blog

Information Protection Scanner: Resolve Issues with Information Protection Scanner Deployment

By Ashwin Venugopal -
Image
  About If you are experiencing problems with the Microsoft Purview Information Protection scanner, check the health of your deployment by utilizing the Start-ScannerDiagnosticsPowerShell cmdlet to start the scanner diagnostic tool. The diagnostics tool checks the following details and then creates a log files with the results: Whether the database is up to date. Whether network URLs are accessible. Whether there's a valid authentication token and policy can be acquired. Whether the profile is defined in the Azure portal. Whether offline/online configuration exists and can be acquired. Whether the rules configured are valid.  The Start-ScannerDiagnostics command does not perform a comprehensive check of prerequisites. If you encounter problems with the scanner, you need to verify that your system meets the scanner's requirements, and that your scanner's configuration and installation are finished.  Verify Scanning Details Per Scanner Node and Repository Run the Get-ScanSt...
Read more

How AMI Store & Restore Works?

By Ashwin Venugopal -
Image
  CreateStoreImageTask The CreateStoreImageTask API stores an AMI as a single object in an S3 bucket. The API initiates a task that collects all the data from the AMI and its associated snapshots, subsequently using an S3 multipart upload to store this data in an S3 object. It gathers all elements of the AMI, including most of the non-Region-specific metadata and all EBS snapshots included in the AMI, and consolidates them into a single object in S3. During the upload process, the data is compressed to minimize the space utilized in S3, which means that the S3 object could be smaller than the total sizes of the snapshots in the AMI. If the account making this API call has access to AMI and snapshot tags, they will be retained. The S3 object shares the same ID as the AMI, except it has a .bin extension. Additionally, the S3 metadata tags for the object include the AMI name, AMI description, AMI registration date, AMI owner account, and a timestamp indicating when the store operation...
Read more

Create A Store Image Task

By Ashwin Venugopal -
Image
  Introduction When you save an AMI in an S3 bucket, a task for storing the image is initiated. This store image task allows you to track the progress and result of the procedure. Securing your AMIs It is crucial to verify that the S3 bucket is set up with adequate security to protect the content of the AMI and that this security is upheld for the entire duration that the AMI objects are stored in the bucket. If this cannot be achieved, it is advisable to refrain from using these APIs. Make sure that public access to the S3 bucket is prohibited. It is suggested to activate Server-side encryption for the S3 buckets where you keep the AMIs, even though it’s not mandatory. When AMI snapshots are transferred to the S3 object, they are sent over TLS connections. It is possible to save AMIs that contain encrypted snapshots; however, the snapshots will be decrypted during the storing process. Identify the source AMI used to create a new Amazon EC2 AMI You can determine the AMI that was us...
Read more