﻿{"id":765,"date":"2022-03-18T00:03:28","date_gmt":"2022-03-17T18:33:28","guid":{"rendered":"https:\/\/blogs.infosys.com\/infosys-cobalt\/?p=765"},"modified":"2022-03-18T00:03:28","modified_gmt":"2022-03-17T18:33:28","slug":"anaplan-cloudworks-aws-s3-vs-azure-blob","status":"publish","type":"post","link":"https:\/\/blogs.infosys.com\/infosys-cobalt\/cloud-applications\/oracle\/anaplan\/anaplan-cloudworks-aws-s3-vs-azure-blob.html","title":{"rendered":"Anaplan CloudWorks &#8211; AWS S3 vs Azure Blob"},"content":{"rendered":"<p>Anaplan has introduced a new feature called \u201cCloudWorks\u201d recently, wherein Anaplan can connect with any Cloud storage service provider like AWS S3, Azure Blob, Google Big Query to import data files into Anaplan Model manually or automatically. It\u2019s a 2-way connection, which means you can push data from Anaplan model into cloud storage service as well.<\/p>\n<p>Amazon AWS has captured 32% of the market, followed by Azure at 19% &amp; Google at 7% respectively. From Anaplan perspective, all 3 cloud storage services work well, so it\u2019s up to individual businesses to identify which cloud storage works well given their business requirement.<\/p>\n<p>In this topic, we will analysis AWS S3 &amp; Azure Blob, try to figure out which one provides more bang for the buck<\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"color: #000080\"><strong>Key Features of AWS S3 &amp; Azure Blob<\/strong><\/span><\/p>\n<p style=\"padding-left: 40px\"><strong>A. Quick Overview<\/strong><\/p>\n<p style=\"padding-left: 40px\">AWS S3 \u00a0is simple cloud storage service, where you could store, retrieve &amp; backup any amount of data at any point of time. S3 is an object-based storage which means all data are stored as objects.<br \/>\nAzure Blob<\/p>\n<p style=\"padding-left: 40px\">Azure Blob is Microsoft storage cloud service which can be used to store images, documents, videos, audios etc.<br \/>\nAzure is \u201cstorage account\u201d oriented storage tier setting<\/p>\n<p style=\"padding-left: 40px\"><strong>B. Scalability<\/strong><\/p>\n<p style=\"padding-left: 40px\">Both AWS S3 and Azure Cool Blob Storage can be scalable according to active user demands. Both provides auto scaling in form \u201cAWS Auto Scaling\u201d for AWS, &amp; \u201cAuto scale\u201d for Azure either vertically or horizontally.<\/p>\n<p style=\"padding-left: 40px\"><strong>C.\u00a0 Life Cycle Management<\/strong><\/p>\n<p style=\"padding-left: 40px\">This feature helps you to optimize your storage space &amp; be more cost effective. You can create a predefined rule to automate data transitions between different storage classes (Hot to cool storage, then archive or deletion, if required). Using this feature, user can optimize their standard cloud storage by transitioning data (which is no longer useful) from let say from S3 Standard to S3 Glacier\/Deep Glacier, as there are certain cost benefits associated to different storage classes. Both AWS &amp; Azure provides different range of storage classes &amp; associated benefits<\/p>\n<p style=\"padding-left: 40px\"><strong>D. Data Encryption<\/strong><\/p>\n<p style=\"padding-left: 40px\">AWS S3 uses Client-side encryption &amp; Server-side encryption (AWS AES-256 encryption key, whereas Azure Blob provides Client-side encryption only<\/p>\n<p style=\"padding-left: 40px\"><strong>E.\u00a0 Versioning<\/strong><\/p>\n<p style=\"padding-left: 40px\">This is very handy feature to have especially if you are uploading data with the same file name. Usually, when you upload data with the same file name, the data from the latest file overrides existing data stored in the storage account. If this is what you want in the first place, then it\u2019s okay, however if you want to keep the existing data along with the new one then its important to enable \u201cVersioning\u201d. AWS S3 &amp; Azure Blob, both provides file versioning capabilities<\/p>\n<p style=\"padding-left: 40px\"><strong>F. Access Control<\/strong><\/p>\n<p style=\"padding-left: 40px\">It is part of Identity and Access Management(IAM) which controls user access to various buckets, objects, container, blobs, data etc.<\/p>\n<p style=\"padding-left: 40px\">For example &#8211; AWS S3 follows Bucket policy. The policy can be created using JSON format manually or automatically. Similar features exist in Azure Blob, wherein user can disable public access to the storage account even if containers &amp; blobs access level is set for Public<\/p>\n<p style=\"padding-left: 40px\"><strong>G. Cross Region Application<\/strong><\/p>\n<p style=\"padding-left: 40px\">This feature allows objects\/blobs\/data to be shared with other users belonging to the same account in same region, or same account in different region or separate account in different region. Azure Blob allows you to create replication rule for replicate all blobs, or specific blobs as per your requirement<\/p>\n<p>&nbsp;<\/p>\n<p><strong><span style=\"color: #000080\">Data Integration with Anaplan<\/span><\/strong><\/p>\n<p>In terms of Data Integration (as part of CloudWorks), you need to create \u201cBucket\u201d in AWS S3 &amp; \u201cContainer\u201d in Azure Blob respectively.<\/p>\n<ul>\n<li><strong>AWS S3 Bucket &#8211;<\/strong> Objects cannot be independent; hence they need to store under a Bucket. You can create hundreds of buckets to store thousands of objects in each AWS account<\/li>\n<li><strong>Azure Blob Container &#8211;<\/strong> Container is like a folder to store all data objects\/blobs. A storage account can have hundreds of containers storing thousands of blobs<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong><span style=\"color: #000080\">How to create AWS Bucket and Azure Container<\/span><\/strong><\/p>\n<p>To create an AWS Bucket, you need to have a ASW S3 account. Once, you are registered<\/p>\n<ol>\n<li>Open AWS Management Console. Select \u201cS3\u201d under \u201cAll Services\u201d<\/li>\n<li>Click on \u201cCreate Bucket\u201d to create a new bucket<\/li>\n<li>Enter Bucket Name &amp; Region (Note: Bucket Name should be unique)<\/li>\n<\/ol>\n<p>To create an Azure Container, you need to have a Microsoft Azure account. Once, you are registered<\/p>\n<ol>\n<li>Create a \u201cStorage Accounts\u201d<\/li>\n<li>Once created, open the new storage account &amp; click on \u201cContainer\u201d to create the container<\/li>\n<li>Enter Container Name &amp; specify the public access level (Note: Container Name should be unique)<\/li>\n<\/ol>\n<p><strong><span style=\"color: #000080\">How to Load Objects (in Buckets) and Blobs (Container)<\/span><\/strong><\/p>\n<p>To upload objects into the bucket \u2013 AWS S3<\/p>\n<ol>\n<li>Select the Bucket<\/li>\n<li>Click on Upload. Once, the file is uploaded, it will reflect under the bucket<\/li>\n<\/ol>\n<p>To upload blobs into the container \u2013 Azure Blob<\/p>\n<ol>\n<li>Select the container<\/li>\n<li>Click on Upload. Once, the file is uploaded, it will reflect under the container<\/li>\n<\/ol>\n<p><strong><span style=\"color: #000080\">How to Integrate AWS S3 Bucket and Azure Blob using Anaplan CloudWorks?<\/span><\/strong><\/p>\n<p>There are 2 aspects into Anaplan CloudWorks &#8211; Connection &amp; Integration<\/p>\n<p>First, we need to <strong>establish the connection with the AWS S3 Bucket or Azure Blob<\/strong>, &amp; to do that there are some mandatory details which needs to be entered\/updated in Anaplan CloudWorks page-<\/p>\n<p><strong>AWS S3<\/strong><\/p>\n<ol>\n<li>Connection Name<\/li>\n<li>Access Key ID &gt; Copy the details from the AWS account<\/li>\n<li>Secret Access Key &gt; Copy the details from the AWS account<\/li>\n<li>Bucket &gt; Name of the Bucket from where you want to import the data<\/li>\n<\/ol>\n<p><strong>Azure Blob<\/strong><\/p>\n<ol>\n<li>Connection Name<\/li>\n<li>Storage Account Name &gt; Copy the details from the Azure account<\/li>\n<li>SAS token &gt; Copy the details from the Azure account<\/li>\n<li>Container &gt; Name of the container from where you want to import the data<\/li>\n<\/ol>\n<p>Once the connection is established, you will get to see the status as <strong><span style=\"color: #339966\">Connected<\/span><\/strong><\/p>\n<p>To import files from AWS S3 Bucket or Azure Blob, click <strong>\u201cCreate Integration &gt; Import\/Export\u201d<\/strong> &amp; enter\/update the mandatory details like \u2013<\/p>\n<ol>\n<li>Integration Name<\/li>\n<li>Connection Type &gt; AWS S3 or Azure Blob<\/li>\n<li>Anaplan Workspace Name<\/li>\n<li>Model Name<\/li>\n<li>Action Type &gt; Import<\/li>\n<li>Data Source &gt; Select the data file from the AWS S3 Bucket or the Azure Blob which needs to be imported<\/li>\n<\/ol>\n<p>There are couple of more additional benefits into Anaplan CloudWorks \u2013<\/p>\n<ul>\n<li>You can export data from Anaplan into AWS S3 Bucket or Azure Blob<\/li>\n<li>It allows you to schedule integration jobs, which means you can specify time, frequency etc. &amp; it will run automatically &amp; complete the integration process with no manual intervention<\/li>\n<\/ul>\n<p><span style=\"color: #000080\"><strong>Conclusion<\/strong><\/span><\/p>\n<p>Cloud storage service has come a long way in last 10 years, &amp; businesses are gradually making a transition from on-premises into cloud storage not just because it is cost effective, but it also provides a seamless coverage of their future requirements. Moreover, these storage accounts can be integrated with other ETL tool like AWS GLUE and Azure Data Factory. With respect to pricing, both offers competitive pricing, hence its up to respective businesses to identify &amp; select the best possible scenarios for their business requirement.<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Anaplan has introduced a new feature called \u201cCloudWorks\u201d recently, wherein Anaplan can connect with [&hellip;]<\/p>\n","protected":false},"author":127,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[85],"tags":[84,87,88,86],"coauthors":[83],"class_list":["post-765","post","type-post","status-publish","format-standard","hentry","category-anaplan","tag-anaplan","tag-budgeting","tag-forecasting","tag-planning"],"acf":[],"_links":{"self":[{"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/posts\/765","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/users\/127"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/comments?post=765"}],"version-history":[{"count":3,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/posts\/765\/revisions"}],"predecessor-version":[{"id":776,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/posts\/765\/revisions\/776"}],"wp:attachment":[{"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/media?parent=765"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/categories?post=765"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/tags?post=765"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.infosys.com\/infosys-cobalt\/wp-json\/wp\/v2\/coauthors?post=765"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}