├── AWS CloudFormation vs. Terraform Which One Should You Choose.md ├── Amazon EBS vs EFS vs S3 Picking the Best AWS Storage Option.md ├── How does AWS CodeBuild & AWS CodePipeline Compare.md └── README.md /AWS CloudFormation vs. Terraform Which One Should You Choose.md: -------------------------------------------------------------------------------- 1 | # Introduction 2 | 3 | The Comparison between Different AWS Services is a Series containing different blog posts that provide a basic understanding of key differences Between different aws services. Each post covers the detailed guide on difference between the AWS Services and Which is preferred more . This series aims at providing "Comparison Between Different AWS Services." 4 | 5 | **Infrastructure as code [IaC]** is a big buzzword these days, and it’s no mystery why. IaC, referred to as software-defined infrastructure, is defined as an IT setup wherein developers or operations teams automatically manage and provision the technology stack for an application through software, rather than using a manual process to configure discrete hardware devices and operating systems. It’s a cornerstone of DevOps, designed to boost the agility, productivity and quality of work within organizations. 6 | 7 | When people look for tools to implement infrastructure as code on AWS, they often narrow the choice between AWS CloudFormation or the open-source tool Terraform. Let’s review the differences between the two so you can determine which is right for your needs. 8 | 9 | ![image](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/lxyj39005us8i9308ist.png) 10 | 11 | *My Background: I am Cloud , DevOps & Big Data Enthusiast | 4x AWS Certified | 3x OCI Certified | 3x Azure Certified .* 12 | 13 | ![image](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/xx5nd97sf7xub58rahyx.png) 14 | 15 | ## CloudFormation 16 | 17 | AWS CloudFormation is a managed AWS service with a common language for you to model and provision AWS and third-party application resources for your cloud environment in a secure and repeatable manner. This provides a single reference point for both AWS infrastructure mapping and development. 18 | 19 | CloudFormation abstracts away many of the subtleties involved in managing dependencies between AWS resources. Additionally, CloudFormation allows for the modification and destruction of provisioned resources in a prescribed and predictable manner, making versioning and iterating on your infrastructure much more accessible. CloudFormation is AWS-focused, and AWS-native. 20 | 21 | With CloudFormation, you don’t need to figure out which AWS services need to be provisioned or the subtleties of how to make these dependencies connect together — CloudFormation takes care of this for you in a siloed kind of manner. Once deployed, you can destroy and modify AWS resources in a controlled and predictable way within CloudWatch, allowing you to version control your own AWS infrastructure. This allows for iterative testing, as well as rollback (when configured properly). 22 | 23 | ## Terraform‍ 24 | 25 | Created by HashiCorp, Terraform is an open-source infrastructure-as-code software tool that helps users with the task of setting up and provisioning datacenter infrastructure. A cloud-agnostic tool, Terraform codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned. 26 | 27 | Now that we’ve defined these two IaC platforms, let’s review some of the key differences in more depth. 28 | 29 | ## State Management 30 | 31 | With both CloudFormation and Terraform, you need to keep track of all resources under management. 32 | 33 | With CloudFormation, users can perform regular drift detection on their entire provisioned infrastructure, and receive detailed responses if anything has changed. Some resources in a CloudFormation stack are able to have parameters changed without destroying and rebuilding the targeted resource, while others are considered immutable and will be rebuilt. Additionally, before CloudFormation will delete a resource, it will determine dependencies and fail the command if any exist (which would remain after resource removal). 34 | 35 | Terraform stores the state of the infrastructure on the provisioning computer, or in a remote site (for team use). This state file is a custom JSON format which serves as a map for Terraform, describing which resources it manages, and how those resources should be configured. 36 | 37 | Since CloudFormation is a managed AWS service, it does this for you. CloudFormation will consistently check infrastructure it has provisioned to detect if it is maintaining that state and configuration. If you’re using Terraform, it stores its state on a local disk, and there is a remote state option, which writes the state data to a remote data store, to be shared between all members of a team. Remote state supports Amazon S3, but you need to configure it yourself. 38 | 39 | Now that we’ve covered differences in state management, let’s move on to the topic of modularity. 40 | 41 | ## Modularity 42 | 43 | In the constantly changing world of infrastructure requirements, flexibility is key. CloudFormation and Terraform have unique ways of addressing this need. 44 | 45 | Terraform has a modules, which are containers for multiple resources that are used together. Modules allow developers to abstract their infrastructure into reusable, shareable code and increases iteration speed for teams (much like functions do in a programming language like Ruby). 46 | 47 | CloudFormation utilizes a system called “nested stacks.” That is, CloudFormation templates being called from within CloudFormation templates. These nested stacks can further be abstracted into StackSets. It should be noted that StackSets require additional permissions, beyond those of normal AWS CloudFormation. 48 | 49 | A benefit of Terraform is increased flexibility over CloudFormation with regards to modularity. Terraform modules can be pulled in for any provider supported, or organizations can roll their own. 50 | 51 | Conversely, in a multi-cloud or hybrid environment, CloudFormation doesn’t easily allow users to provision or natively coordinate non-AWS resources. It’s not impossible, as there is a custom resources feature in CloudFormation, but it requires additional templating and design to bring in third party resources, or those AWS services not available organically. 52 | 53 | ## Configuration 54 | 55 | CloudFormation and Terraform differ in how they handle configuration and parameters. 56 | 57 | Terraform uses provider specific data sources. The implementation is in a modular fashion, allowing data to be fetched or computed for use elsewhere in a Terraform configuration. This lets a Terraform configuration make use of information defined outside of Terraform (such as an Elastic IP address), to update or provision infrastructure. 58 | 59 | CloudFormation uses parameters, and has a maximum of 60 parameters per template. Each parameter must have a logical and unique ID among all others in the template. The parameters must be of a type supported by CloudFormation and they have to be provided at the stack’s runtime. Additionally, each parameter must be declared and referenced from within the same template. CloudFormation does have the capability to use Dynamic References to retrieve parameters at runtime from AWS Systems Manager parameter store, if one has been configured properly. 60 | 61 | ## Language‍ 62 | 63 | Terraform uses HashiCorp Configuration Language (HCL), a language built by HashiCorp. It is fully compatible with JSON, and was created to strike a balance between human-friendly and machine-friendly languages, while remaining interpretable to humans. 64 | 65 | AWS CloudFormation utilizes either JSON or YAML, with the YAML version being slightly easier to read (as well as more compact). CloudFormation also has a limit of 51,000 bytes for the template body itself. If a larger template is needed, AWS advises developers to separate resources into nested stacks. 66 | 67 | 68 | 69 | ![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3p6pm88p29jl5mqwo4op.png) 70 | 71 | ## The Bigger Picture — CloudFormation or Terraform‍ 72 | 73 | Both are powerful cloud infrastructure management tools. If you’re already on AWS and using all AWS tools, CloudFormation may be more convenient, especially if you have no external tie ins from 3rd parties. However, if you’re looking for additional flexibility from a cloud-agnostic platform that integrates with AWS services (and those of all other popular providers), Terraform might be of greater utility for your organization. It’s important to not only look at what is working currently - but what the future state of any infrastructure might be. There are long-term benefits with both toolsets, and the final decision may come down to simple usability and developer comfort. Whichever choice you make, using either of these “swiss army knives” of AWS infrastructure is sure to increase productivity, portability, and efficiency. 74 | 75 | 76 | --- 77 | 78 | Hope this guide helps you understand the key differences between AWS CloudFormation and Terraform, feel free to connect with me on [LinkedIn.](https://www.linkedin.com/in/adit-modi-2a4362191/) 79 | You can view my badges [here.](https://www.youracclaim.com/users/adit-modi/badges) 80 | If you are interested in learning more about AWS then follow me on [github.](https://github.com/AditModi) 81 | If you liked this content then do clap and share it . Thank You . -------------------------------------------------------------------------------- /Amazon EBS vs EFS vs S3 Picking the Best AWS Storage Option.md: -------------------------------------------------------------------------------- 1 | # Introduction 2 | 3 | The Comparison between Different AWS Services is a Series containing different blog posts that provide a basic understanding of key differences Between different aws services. Each post covers the detailed guide on difference between the AWS Services and Which is preferred more . This series aims at providing "Comparison Between Different AWS Services." 4 | 5 | The **storage strategy** you choose plays a major role in the performance you receive, as well as the costs you’ll expend. To achieve peak efficiency, you must match your computing, application, and processing needs to the appropriate storage technology. But which option is right for you? 6 | 7 | To answer this question, we’ll explore the differences between Amazon Elastic Block Store (Amazon EBS), Amazon Elastic File System (Amazon EFS), and Amazon Simple Storage Service (Amazon S3) and understand each solution’s unique benefits and uses. This will make it easier to pick the best solution to support your business objectives and storage needs. 8 | 9 | ![image](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/idvhggqn8i6vwu64yh51.png) 10 | 11 | 12 | My Background: I am Cloud , DevOps & Big Data Enthusiast | 4x AWS Certified | 3x OCI Certified | 3x Azure Certified . 13 | 14 | ## What’s The Difference Between Amazon EBS Vs EFS Vs S3? 15 | 16 | Amazon EFS, Amazon EBS, and Amazon S3 are AWS’ three different storage types that can be applicable for different types of workload needs. Let’s take a closer look at the key features of each option, as well as the similarities and differences. 17 | 18 | Amazon EBS delivers high-availability block-level storage volumes for Amazon Elastic Compute Cloud (EC2) instances. It stores data on a file system which is retained after the EC2 instance is shut down. Amazon EFS offers scalable file storage, also optimized for EC2. It can be used as a common data source for any application or workload that runs on numerous instances. Using an EFS file system, you may configure instances to mount the file system. The main differences between EBS and EFS is that EBS is only accessible from a single EC2 instance in your particular AWS region, while EFS allows you to mount the file system across multiple regions and instances. 19 | 20 | Finally, Amazon S3 is an object store good at storing vast numbers of backups or user files. Unlike EBS or EFS, S3 is not limited to EC2. Files stored within an S3 bucket can be accessed programmatically or directly from services such as AWS CloudFront. This is why many websites use it to hold their content and media files, which may be served efficiently from AWS CloudFront. 21 | 22 | ## So how can you choose between Amazon EBS vs EFS vs S3? 23 | 24 | That depends on what benefits you’re looking for, and your use case for your workload. Let’s take an in-depth look at each one to understand their benefits and use cases. 25 | 26 | ## Amazon Elastic Block Store (Amazon EBS) 27 | 28 | Use Amazon EBS to provide storage for the drives of your virtual machines. It stores data in equally-sized blocks and organizes them into a hierarchy similar to a traditional file system. The volumes are provisioned in size and attached to EC2 instances in a way that’s similar to the local disk drive on a physical machine. Here are EBS’ benefits and use cases: 29 | 30 | ## Amazon EBS Benefits 31 | 32 | Performance optimization: Increase throughput by devoting network capacity and minimizing the network contention between your instances and EBS. 33 | 34 | Low-latency performance: By using SSD EBS volumes, it offers reliable I/O performance scaled to meet your workload needs. 35 | Highly available and secure storage: EBS volumes offer redundancy within its Availability Zones while access control and encryption bolster security. 36 | 37 | Geographic interchangeability: With EBS, you can duplicate snapshots throughout AWS regions and place resources and data in multiple locations. This makes disaster recovery, data center migration, and geographical expansion simple. 38 | 39 | Easy data backup and restoration: Point-in-time volume snapshots safeguard data. 40 | 41 | Rapid up- or down-scaling: EBS can quickly scale volumes, ensuring you get the right performance and capacity for changing computing needs. 42 | 43 | ## Amazon EBS Use Cases 44 | 45 | Testing and development: You can scale, archive, duplicate or provision your testing, development, or production environments. 46 | 47 | NoSQL databases: EBS offers NoSQL databases the low-latency performance and dependability they need for peak performance. 48 | Relational databases: EBS scales to meet your changing storage needs. This makes it a great choice for deploying databases, including PostgreSQL, MySQL, Oracle, or Microsoft SQL Server. 49 | 50 | Business consistency: Copy EBS Snapshots and Amazon Machine Images (AMIs) to run applications in different AWS regions. This reduces data loss and speeds recovery time by backing up log files and data regularly, across geographies. 51 | 52 | Enterprise-wide applications: It can meet a variety of enterprise computing needs through powerful block storage that can support your most important applications, such as Microsoft Exchange, Oracle, or Microsoft SharePoint. 53 | 54 | ## Amazon Elastic File System (Amazon EFS) 55 | 56 | EFS is the best choice for running any application that has a high workload, requires scalable storage, and must produce output quickly. It scales automatically, even to meet the most abrupt workload spikes. After the period of high-volume storage demand has passed, EFS will automatically scale back down. EFS can be mounted to different AWS services and accessed from all your virtual machines. Use it for running shared volumes, or for big data analysis. You’ll always pay for the storage you actually use, rather than provisioning storage in advance that’s ultimately wasted. 57 | 58 | ## Amazon EFS Benefits 59 | 60 | Performance that scales to support any workload: EFS offers the throughput changing workloads need. It can provide higher throughput in spurts that match sudden file system growth, even for workloads up to 500,000 IOPS or 10 GB per second. 61 | 62 | Energetic elasticity: Automatically scale your file system storage up or down. Remove or add files and never disturb applications. Once you make your EFS file system you can add files without worrying about storage provisioning. 63 | 64 | Accessible file storage: On-premises servers and EC2 instances can access shared file systems concurrently. EC2 instances can also access EFS file systems located in other AWS regions through VPC peering. 65 | 66 | Comprehensive managed service: EFS is a complete managed service, meaning your firm will never have to patch, deploy, or maintain your file system. 67 | 68 | Cost savings: The only storage you’ll pay for is exactly what you use, as there’s no advance provisioning, up-front fees, or commitments. Moreover, you can use Lifecycle Management to transfer files that have been unused for a month to a more cost-effective storage class, which can lower expenses up to 85%. 69 | Tighter security and compliance: You can securely access the file system with your current security solution, or control access to EFS file systems using AWS Identity and Access Management (IAM), Amazon Virtual Private Cloud (Amazon VPC), or POSIX permissions. And, EFS can encrypt your data, whether it’s in transit or at rest. This gives you dependable security and makes regulatory compliance easier. 70 | 71 | ## Amazon EFS Use Cases 72 | 73 | Lift-and-shift application support: EFS is elastic, available, and scalable, and enables you to move enterprise applications easily and quickly without needing to re-architect them. 74 | 75 | Analytics for big data: It has the ability to run big data applications, which demand significant node throughput, low-latency file access, and read-after-write operations. 76 | 77 | Content management system and web server support: EFS is a robust throughput file system capable of enabling content management systems and web serving applications, such as archives, websites, or blogs. 78 | 79 | Application development and testing: Only EFS provides a shared file system needed to share code and files, across multiple compute resources to facilitate auto-scaling workloads. 80 | 81 | ## Amazon S3 82 | 83 | Amazon S3 provides object storage. Each object has its own unique identifier or key, for access through web requests from any location. S3 also supports static web content hosting that can be accessed from the S3 bucket or from AWS CloudFront. And S3 is notably secure, providing. “eleven nines” - 99.999999999 of data durability. 84 | 85 | ## Amazon S3 Benefits 86 | 87 | Robust performance, scalability, and availability: Amazon S3 scales storage resources free from resource procurement cycles or investments upfront. It keeps your data safe from errors, failures, and threats and makes it available when you need it. 88 | Cost-saving storage classes: Storing data throughout S3 storage classes saves costs and maintains high levels of performance. Storage class analysis enables you to locate data that may be moved to a lower-cost storage class. Then you can make the transfer using an S3 Lifecycle policy. 89 | 90 | Finally, S3 intelligent-tiering enables the storage of data that has changing or unknown access patterns by tiering objects, which cuts storage costs. 91 | 92 | Easier security, compliance, and audit features: S3 can store data and protect it from unauthorized access using its powerful access management and encryption tools. S3 has features that make it easy to comply with regulatory requirements, and Amazon Macie can deny irregular access requests to your sensitive data. Plus, S3 works well with AWS’ many auditing features. 93 | 94 | Exacting data control: An array of management tools enable you to classify and report on data. S3 has storage class analysis that monitors access patterns, while S3 Lifecycle analyzes object transfers to lower-cost storage. 95 | S3 Object Lock assigns retention dates to objects to prevent deletion, and S3 Inventory offers visibility of stored objects and their encryption and metadata. Finally, S3 Batch Operations can run storage management maintenance for billions of objects while AWS Lambda can be used to automate workflows, define alerts and log activities without added management of infrastructure. 96 | 97 | ## Amazon S3 Use Cases 98 | 99 | Data lake and big data analytics: Create a data lake to hold raw data in its native format, then use machine learning tools, query-in-place, and analytics to draw insights. S3 works with AWS Lake Formation to create data lakes, then define governance, security, and auditing policies. Together, they can be scaled to meet your growing data stores, and you’ll never have to make an investment upfront. 100 | 101 | Backup and restoration: Secure, robust backup and restoration solutions are easy to build when you combine S3 with other AWS offerings, including EBS, EFS, or S3 Glacier. These offerings enhance your on-premises capabilities, while other offerings can help you meet compliance, recovery time, and recovery point objectives. 102 | 103 | Reliable disaster recovery: S3 storage, S3 Cross-Region Replication and additional AWS networking, computing, and database services make it easy to protect critical applications, data, and IT systems. It offers nimble recovery from outages, no matter if they are caused by system failures, natural disasters, or human error. 104 | 105 | Methodical archiving: S3 works seamlessly with other AWS offerings to provide methodical archiving capabilities. S3 Glacier and S3 Glacier Deep Archive enable you to archive data and retire physical infrastructure. There are three S3 storage classes you can use to retain objects for extended periods of time at their lowest rates. 106 | 107 | S3 Lifecycle policies can be created to archive objects at any point within their lifecycle, or you can upload objects to archival storage classes directly. 108 | 109 | S3 Object Lock meets compliance regulations by applying retention dates objects to avoid their deletion. And unlike a tape library, S3 Glacier can restore any archived object within minutes. 110 | 111 | ![image](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/455ibg4awp8z3qyht4ho.png) 112 | 113 | 114 | Hope this guide helps you understand the Different AWS Storage Options, feel free to connect with me on [LinkedIn.](https://www.linkedin.com/in/adit-modi-2a4362191/) 115 | You can view my badges [here.](https://www.youracclaim.com/users/adit-modi/badges) 116 | If you are interested in learning more about AWS then follow me on [github.](https://github.com/AditModi) 117 | If you liked this content then do clap and share it . Thank You . 118 | -------------------------------------------------------------------------------- /How does AWS CodeBuild & AWS CodePipeline Compare.md: -------------------------------------------------------------------------------- 1 | # Introduction 2 | 3 | The Comparison between Different AWS Services is a Series containing different blog posts that provide a basic understanding of key differences Between different aws services. Each post covers the detailed guide on difference between the AWS Services and Which is preferred more . This series aims at providing "Comparison Between Different AWS Services." 4 | 5 | ## What is AWS CodeBuild? What is AWS CodePipeline? 6 | 7 | **AWS CodeBuild** is a fully managed build service in the cloud. AWS CodeBuild compiles the source code, runs unit tests, and produces artifacts that are ready to deploy. CodeBuild eliminates the need to provision, manage, and scale own build servers. It provides prepackaged build environments for popular programming languages and build tools such as Apache Maven, Gradle, and more. You can also customize build environments in CodeBuild to use your own build tools. CodeBuild scales automatically to meet peak build requests 8 | 9 | **AWS CodePipeline** on the other hand, is a fully managed continuous delivery service that helps to automate the release pipelines for fast and reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of the release process every time there is a code change, based on the release model you define. This enables a rapid and reliable delivery of features and updates. AWS CodePipeline can easily integrate with third-party services such as GitHub or any other custom plugin. 10 | 11 | 12 | ![image](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vzvxteb1vwu50a3winfd.png) 13 | 14 | My Background: I am Cloud , DevOps & Big Data Enthusiast | 4x AWS Certified | 3x OCI Certified | 3x Azure Certified . 15 | 16 | 17 | 18 | ## What are the differences? 19 | 20 | The main difference between the two is; AWS CodeBuild can be classified as a tool in the Continuous Integration category, while AWS CodePipeline is grouped under Continuous Deployment. 21 | 22 | 23 | ## What is Continuous Integration? 24 | 25 | Continuous integration is a software development method where members of the team can integrate their work at least once a day. In this method, every integration is checked by an automated build to search the error. 26 | 27 | In continuous integration after a code commit, the software is built and tested immediately. In a large project with many developers, commits are made many times during a day. With each commit code is built and tested. If the test is passed, build is tested for Deployment. If the Deployment is a success, the code is pushed to production. This commit, build, test, and deploy is a continuous process, and hence the name continuous integration/deployment. 28 | 29 | ## What is Continuous Delivery? 30 | 31 | Continuous delivery is a software engineering method in which a team develops software products in a short cycle. It ensures that software can be easily released at any time. 32 | 33 | The main aim of continuous delivery is to build, test, and release software with good speed and frequency. It helps you to reduce the cost time and risk of delivering changes by allowing for frequent updates in production. 34 | 35 | ## What is Continuous Deployment 36 | 37 | Continuous deployment is a software engineering process in which product functionalities are delivered using automatic deployment. It helps testers to validate whether the codebase changes are correct and stable or not. 38 | 39 | The team can achieve continuous deployment by relying on infrastructure that automates different testing steps. Once each integration meets this release criteria, the application is updated with a new code. 40 | 41 | 42 | ## How do you run AWS CodeBuild and AWS CodePipeline? 43 | 44 | You can use the AWS CodeBuild or AWS CodePipeline console to run CodeBuild. You can also automate the running of CodeBuild by using the AWS Command Line Interface (AWS CLI) or the AWS SDKs. 45 | 46 | ![image](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2u8085gkpy5bihz6d53h.png) 47 | 48 | 49 | Source: stackshare.io 50 | 51 | 52 | 53 | You can then add CodeBuild as a build or test action to the build or test stage of a pipeline in AWS CodePipeline. AWS CodePipeline is a continuous delivery service that you can use to model, visualize, and automate the steps required to release your code. This includes building your code. 54 | 55 | A pipeline is a workflow construct that describes how code changes go through a release process. See the illustration below; 56 | 57 | ![image](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/esp0wlxm5cdtcog793kx.png) 58 | 59 | 60 | Source: stackshare.io 61 | 62 | 63 | 64 | ## What are some of the tools that integrate with AWS CodeBuild and AWS CodePipeline? 65 | 66 | Some of the tools that integrate with AWS CodeBuild include; GitHub, GitHub Enterprise, Jenkins, Bitbucket, AWS CodeCommit, AWS CodeFormation, AWS Elastic Beanstalk, and Amazon S3. 67 | 68 | On the other hand, some of the tools that integrate with AWS CodePipeline include; GitHub, AWS Elastic Beanstalk, Amazon EC2, Amazon S3, Jenkins, Cloudbees, and Runscope. 69 | 70 | ## What are some alternatives to AWS CodeBuild and AWS CodePipeline? 71 | 72 | #### Jenkins 73 | 74 | Jenkins is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project. 75 | 76 | #### AWS CodeDeploy 77 | 78 | AWS CodeDeploy is a service that automates code deployments to Amazon EC2 instances. AWS CodeDeploy makes it easier to rapidly release new features, helps you avoid downtime during deployment, and handles the complexity of updating your applications. 79 | 80 | #### AWS CodeStar 81 | 82 | AWS CodeStar provides a unified user interface, enabling you to easily manage your software development activities in one place. 83 | 84 | #### Apache Maven 85 | 86 | Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. 87 | 88 | #### GitLab CI 89 | 90 | GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline. 91 | 92 | ## Conclusion 93 | 94 | Every project has its own requirements and every CI/CD is unique. But when you have such great and easy to use tools available for you, you might as well want to make smarter use of them. AWS CodeBuild and AWS CodePipeline protects your secrets, automates jobs, reduces chances of error, and saves time and effort. In a poll by Stackshare in its community, “Pay per minute” is the primary reason why developers consider AWS CodeBuild over the competitors, whereas “Simple to set up” was stated as the key factor in picking AWS CodePipeline. 95 | 96 | Hope this guide helps you understand the key differences between two of most used CI/CD services of aws, feel free to contact me on [LinkedIn.](https://www.linkedin.com/in/adit-modi-2a4362191/) 97 | You can view my badges [here.](https://www.youracclaim.com/users/adit-modi/badges) 98 | If you are interested in learning more about AWS then follow me on [github.](https://github.com/AditModi) 99 | If you liked this content then do clap and share it . Thank You . 100 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Comparing-Different-AWS-Services 2 | 3 | Comparing Different AWS Services Series' Articles 4 | 5 | Feel free to make suggestions, I am open to any advice! You can reach me on [Twitter](https://twitter.com/adi_12_modi) or [LinkedIn](https://www.linkedin.com/in/adit-modi-2a4362191/). 6 | 7 | ##### Enjoy! 😉👍 8 | 9 | ![visitors](https://visitor-badge.glitch.me/badge?page_id=/AditModi/Comparing-Different-AWS-Services)[![Website](https://img.shields.io/website?label=Dev.to&up_message=@aditmodi&url=https%3A%2F%2Fdev.to/aditmodi)](https://dev.to/aditmodi) 10 | 11 | ![Comparing-Different-AWS-Services](https://user-images.githubusercontent.com/48589838/177519581-27bc453c-54e2-4266-b996-96e1134e37c1.jpg) 12 | 13 | 14 | | | Topic | Personal Website | Hashnode | 15 | | ------------ | ------------ | ---------------- | ------------ | 16 | | 1 | How does AWS CodeBuild & AWS CodePipeline Compare? |[ Link ]() |[ Hashnode ]() 17 | | 2 | Amazon EBS vs EFS vs S3: Picking the Best AWS Storage Option |[ Link ]() |[ Hashnode ]() 18 | | 3 | AWS CloudFormation vs. Terraform Which One Should You Choose |[ Link ]() |[ Hashnode ]() 19 | --------------------------------------------------------------------------------