Tag: AWS

What is DevOps and AZURE DEVOPS?

by bittu KCLOUD COMPUTING AND OPERATING SOFTWARE / DevOps Community / DevOps Practice and Process / DevOps ToolingLeave a Comment on What is DevOps and AZURE DEVOPS?

Introduction

Guys, today in this blog you will learn in detail about DevOps and Azure DevOps, so let’s know what is DevOps and Azure DevOps. DevOps is a term of the two words ‘development’ and ‘operations’. DevOps is not a technology, it is a combination of cultural, practices, and tools that increases an organization’s ability to deliver applications and services. Azure is one of the fast growing cloud computing platform. Microsoft Azure DevOps is built on multi-tier, scalable architecture. It is comprises a range of services covering the full development life-cycle.

What is DevOps?

DevOps is a software development methodology where the Development team & Operations team work as a together. After adopting DevOps, it helps to increase the speed of an organization to deliver applications and services. And it can be defined as the alignment of development and IT operations with better communication and collaboration. And those who are devops engineers use many tools for development & operations process so that our life becomes easy. Like these popular DevOps tools are:- Docker, Git, SVN, Maven, Jenkins, Selenium, Kubernetes, Puppet, Chef, SaltStack, Nagios, Splunk, etc.

How DevOps works in the Enterprise?

You can see through the image.

Works flow of DevOps

Below you can see works of DevOps by following each phase of the DevOps life cycle which includes continuous development, continuous integration, continuous testing, and continuous deployment.

• Continuous Development – Plan application objectives and code the requirements

• Continuous Testing – Verify the product for actual usage in a live environment

• Continuous Integration – It Plan tests and build the product

• Continuous Deployment – Ensures product is deployed with maximum accuracy

• Continuous Monitoring – It Monitor the product output and find the problem areas

Here are the some Benefits of DevOps:-

  • DevOps ideology encourages a completely new way of thinking and decision-making.
  • DevOps certified professionals are among the highest-paid in the IT industry.
  • The market demand is increasing rapidly with its increased implementation worldwide.
  • It ideology promotes increased collaboration and communication between the operation and development teams.
  • You learn to work in a team consisting of cross-functional team members—QA, developers, operation engineers, and business analysts.

Here you see Salary of DevOps Engineer:-

According to payscale.com, the demand for DevOps is high but companies require individuals to have the correct skill sets. Additionally, the better the experience, the higher is the salary. The average devops salary in India, according to Payscale, is Rs 674,202 per year, inclusive of bonuses and profit-sharing.

Below you can get complete knowledge of Microsoft Azure and Azure DevOps by source of DevOpsSchool.com.

What is Microsoft Azure?

Now, lets know about Microsoft Azure, It is a cloud computing service created by Microsoft that is one of the leading cloud service providers, and day-by-day many organizations are opting for Azure to get the best technologies for efficient computations. Its use will help you to build, deploy, and manage applications through your globally owned network of data centers.

What is Azure DevOps?

Now, lets know about Azure DevOps, it is a mixture of the simplest of technology and therefore the application of best practices. We can say, It is the Next Big thing in IT Industries. Azure DevOps is a Software as a service (SaaS) platform from Microsoft that provides an end-to-end DevOps toolchain for developing and deploying software. Microsoft recently launched this as a result of they perceive that DevOps has become more and more vital to a team’s success. It’s concerning culture and an amendment within the manner we tend to do things, yet as our mental attitude. Azure DevOps captures over fifteen years of investment and learnings in providing tools to support software packages, development groups. more to the present.

How does Azure DevOps work?

In the easiest terms, Azure DevOps is the evolution of VSTS (Visual Studio Team Services). Azure DevOps works both public and private cloud configurations – the services include:

  • Azure Boards – A work tracking system with Kanban boards, dashboards, and reporting
  • Azure Pipelines – A CI/CD, testing, and deployment system that can connect to any Git repository
  • Azure Repos – A cloud-hosted private Git repository service
  • Azure Test Plans – A solution for tests and capturing data about defects
  • Azure Artifacts – A hosting facility for Maven, npm, and NuGet packages

Azure DevOps use cases include – 1. Planning 2. Developing 3. Delivery 4. Operations

How to become a Azure DevOps Certified Engineer and list of the various certifications:–

If you want to become a Microsoft Azure DevOps Certified Engineer: then, you must earn at least one of the following: Microsoft Certified: Azure Administrator Associate, Microsoft Certified: Azure Developer Associate certification.

These are Best Microsoft Azure Certification:-

  • Microsoft AZ-900 Certification: Azure Fundamentals course
  • AZ-104 Azure Administrator Exam Certification course
  • Microsoft AZ-400 Azure DevOps Certification course
  • AZ-204 Developing Solutions
  • AZ – 303 Microsoft Azure Architect
  • AZ – 304 Microsoft Azure Architect Design
  • Microsoft AZ-500 Certification: Azure Security Technologies course

Below you can path of Azure Certification:-

Pre-Requisites for Microsoft Azure course

  • Basics of Networking
  • Basics of the MS Azure Platform
  • Basic concepts related to operating systems
  • Basic familiarity with infrastructure paradigms such as active directory and PowerShell

What is the Salary of Azure DevOps Engineer?

Here I am going to share with you the average salary of an Azure DevOps Engineer. If you are working at a product-based company, then the salary ranges start from ₹16L to ₹42L per year. And the average salary of an Azure DevOps Engineer working at a service-based company can range start from ₹5.5L to ₹23L per year.

These are some Popular Courses of Azure:-

What are the Difference Between DevOps and Azure DevOps?

DevOps is basically a culture and it is really hot at the moment and is revolutionizing the workplace. It is the bridge closing the gap between Development and Operations team and bringing them together. DevOps is achieved through tools, processes, and automation, but, even more than that, through a change in organizational culture.

Azure DevOps is a Software as a service (SaaS) platform from Microsoft that provides an end-to-end DevOps toolchain for developing and deploying software. It is a mixture of the simplest of technology and therefore the application of best practices. Azure DevOps works both public and private cloud configurations.

If you are planning to become an Master in Azure DevOps Engineer, and searching to the best institute for preparing for Azure certifications, then I would suggest you one of the best Institutes that is DevOpsSchool.com. This institute has 10 to 15+ years of experienced trainers who providing you quality training with industries requirement.

I am going to share with you some videos, then you can get some overview of DevOps and Start to learn Azure DevOps course.

DevOps Fundamental to Advanced Tutorial for Beginners

Microsoft Azure Fundamental Tutorial | AZ-900 Certification

Why Choose DevOpsSchool | Reviews | Testimonials | Learner’s Feedback

I hope this tutorial is very helpful for you!

Keep learning! Best of Luck

Tagged : / / / / / / / / / / / /

List of AWS regions and availability zones

by scmgalaxy KAmazon Web ServicesLeave a Comment on List of AWS regions and availability zones

List of  AWS Regions

This is complete list of  AWS regions available currently.

S.No Code Name
1 us-east-1 US East (N. Virginia)
2 us-west-2 US West (Oregon)
3 us-west-1 US West (N. California)
4 eu-west-1 EU (Ireland)
5 eu-central-1 EU (Frankfurt)
6 ap-southeast-1 Asia Pacific (Singapore)
7 ap-northeast-1 Asia Pacific (Tokyo)
8 ap-southeast-2 Asia Pacific (Sydney)
9 ap-northeast-2 Asia Pacific (Seoul)
10 sa-east-1 South America (São Paulo)
11 cn-north-1 China (Beijing)
12 ap-south-1 India (Mumbai)

AWS upcoming regions

 

S.No Code Name
1 N/A OHIO
2 N/A MONTREAL
3 N/A UK
4 N/A INDIA
5 N/A NINGXIA

List of  AWS regions and their availability zones

S.No AWS region code AWS region name Number Of Availability Zones Availability Zone Names
1 us-east-1 Virginia 4 us-east-1a
us-east-1b
us-east-1c
us-east-1e
2 us-west-2 Oregon 3 us-west-2a
us-west-2b
us-west-2c
3 us-west-1 N. California 3 us-west-1a
us-west-1b
4 eu-west-1 Ireland 3 eu-west-1a
eu-west-1b
eu-west-1c
5 eu-central-1 Frankfurt 2 eu-central-1a
eu-central-1b
6 ap-southeast-1 Singapore 2 ap-southeast-1a
ap-southeast-1b
7 ap-southeast-2 Sydney 3 ap-southeast-2a
ap-southeast-2b
ap-southeast-2c
8 ap-northeast-1 Tokyo 2 ap-northeast-1a
ap-northeast-1c
9 ap-northeast-2 Seoul N/A N/A
10 sa-east-1 Sao Paulo 3 sa-east-1a
sa-east-1b
sa-east-1c
11 cn-north-1 China (Beijing) N/A N/A
12 ap-south-1 India (Mumbai) 2 ap-south-1a
ap-south-1b

If you are familiar with AWS CLI you can always check regions and availability zones using following aws cli commands

Find regions using AWS CLI

Command:  aws ec2 describe-regions

Tagged : / /

Getting Started with Amazon Simple Queue Service (SQS)

by scmgalaxy KAmazon Web ServicesLeave a Comment on Getting Started with Amazon Simple Queue Service (SQS)

amazon-simple-queue-service

We’ve put together a list of resources that we think will be useful to you, as you familiarize yourself with Amazon SQS and get started working with it.

Introductory Topics

What is Amazon SQS?
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/Welcome.html

Getting Started with Amazon SQS:
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-getting-started.html

How Amazon SQS Queues Work:
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-how-it-works.html

Best Practices for Amazon SQS:
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-best-practices.html

Using Amazon SQS Dead Letter Queues:
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html

Using JMS with Amazon SQS:
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-java-message-service-jms-client.html

Limits in Amazon SQS:
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-limits.html

Integration with Other AWS Services

Subscribing an Amazon SQS Queue to an Amazon SNS Topic:
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-subscribe-queue-sns-topic.html

Monitoring Amazon SQS with CloudWatch:
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/MonitorSQSwithCloudWatch.html

Managing Large Amazon SQS Messages (Up to 2 GB) Using Amazon S3:
http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-s3-messages.html

Tagged : / / / / /

AWS Storage FAQ

by scmgalaxy KAmazon Web ServicesLeave a Comment on AWS Storage FAQ

What data is stored in ephemeral storage of an Amazon EC2 instance?

Anything that is not stored on an ebs volume that is mounted to the instance will be lost. For instance, if you mount your ebs volume at /mystuff, then anything not in /mystuff will be lost. If you don’t mount an ebs volume and save stuff on it, then I believe everything will be lost.

You can create an AMI from your current machine state, which will contain everything in your ephemeral storage. Then, when you launch a new instance based on that AMI it will contain everything as it is now.

Meaning of “Warning: Please note that any data on the ephemeral storage of your instance will be lost when it is stopped”

There is a difference between “stop” and “terminate”. If you “stop” an instance that is backed by EBS then the information on the root volume will still be in the same state when you “start” the machine again.

Basically, root volume (your entire virtual system disk) is ephemeral, but only if you choose to create AMI backed by Amazon EC2 instance store.

If you choose to create AMI backed by EBS then your root volume is backed by EBS and everything you have on your root volume will be saved between reboots.

If you are not sure what type of volume you have, look under EC2->Elastic Block Store->Volumes in your AWS console and if your AMI root volume is listed there then you are safe. Also, if you go to EC2->Instances and then look under column “Root Device” of your instance and if it says “ebs”, then you don’t have to worry about data on your root device.

Tagged : / / / /

What is the difference between terminating and stopping an EC2 instance?

by scmgalaxy KAmazon Web ServicesLeave a Comment on What is the difference between terminating and stopping an EC2 instance?

terminating-and-stopping-an-ec2-instance

Answer

Terminate Instance

When you terminate an EC2 instance, the instance will be shutdown and the virtual machine that was provisioned for you will be permanently taken away and you will no longer be charged for instance usage. Any data that was stored locally on the instance will be lost. Any attached EBS volumes will be detached and deleted. However, if you attach an EBS Snapshot to an instance at boot time, the default option in the Dashboard is to delete the attached EBS volume upon termination.

Stop Instance

When you stop an EC2 instance, the instance will be shutdown and the virtual machine that was provisioned for you will be permanently taken away and you will no longer be charged for instance usage. The key difference between stopping and terminating an instance is that the attached bootable EBS volume will not be deleted. The data on your EBS volume will remain after stopping while all information on the local (ephemeral) hard drive will be lost as usual. The volume will continue to persist in its availability zone. Standard charges for EBS volumes will apply. Therefore, you should only stop an instance if you plan to start it again within a reasonable timeframe. Otherwise, you might want to terminate an instance instead of stopping it for cost saving purposes.

The ability to stop an instance is only supported on instances that were launched using an EBS-based AMI where the root device data is stored on an attached EBS volume as an EBS boot partition instead of being stored on the local instance itself. As a result, one of the key advantages of starting a stopped instance is that it should theoretically have a faster boot time. When you start a stopped instance the EBS volume is simply attached to the newly provisioned instance. Although, the AWS-id of the new virtual machine will be the same, it will have new IP Addresses, DNS Names, etc. You shouldn’t think of starting a stopped instance as simply restarting the same virtual machine that you just stopped as it will most likely be a completely different virtual machine that will be provisioned to you.

Tagged : / / / / / / /

What’s the difference between ephemeral and volume boot disks?

by scmgalaxy KAmazon Web ServicesLeave a Comment on What’s the difference between ephemeral and volume boot disks?

Different boot sources

There are several different kinds of sources to boot from in the DreamCompute dashboard, but they all need to create some sort of virtual disk for the virtual machine to boot. The virtual disk can use either ephemeral storage or volume block storage. When launching an instance, you have several Boot Source options:

  • Image: Launches an instance from the image you choose onto either an ephemeral disk or a new volume disk.
  • Instance Snapshot: Launches an instance from the instance snapshot you choose onto either an ephemeral disk or a new volume disk.
  • Volume: Launches an instance from an existing bootable volume.
  • Volume Snapshot: Creates a volume from the volume snapshot you choose and then launches an instance using that new bootable volume.

Ephemeral boot disks

Ephemeral disks are virtual disks that are created for the sole purpose of booting a virtual machine and should be thought of as temporary.

Ephemeral disks are useful if you aren’t worried about needing to duplicate an instance or destroy an instance and save the data. You can still mount a volume on an instance that is booted from an ephemeral disk and put any data that needs to be saved on it, instead of using the volume as the root of your OS.

  • Can be snapshotted: Useful for duplicating instances or having a copy of an instance at a certain point in time. Snapshots of ephemeral boot disks are stored as Images and count against DreamCompute’s Image quota.
  • Do not use up volume quota: If you have more instance quota, you can always boot it from an ephemeral disk even if you don’t have any volume quota left.
  • Are destroyed when the instance is terminated: This means you will loose your data if you want to delete an instance to free up some instance quota.

Volume Boot Disks

Volumes are a more permanent form of storage than ephemeral disks and can be used to boot from as well as a mountable block device.

Volume boot disks are useful if you need an easy way to duplicate instances and back them up with snapshots, or if you need a more reliable storage solution for your instance than an ephemeral disk. If you use them, you should plan ahead so that you have enough quota for all of the instances you want to boot.

  • Can be snapshotted: Useful for duplicating instances or having a copy of an instance at a certain point in time.
  • Does not get destroyed when you delete the instance (Unless you select the “Delete Volume on Instance Delete” option): You can delete the instance and your data will still exist as a volume that you can boot from later.
  • Uses your volume quota: This can be pricey if you have lots of instances, or take lots of snapshots.

Source – https://help.dreamhost.com/hc/en-us/articles/217701757-What-s-the-difference-between-ephemeral-and-volume-boot-disks-

Tagged : / / / /

Difference between AWS EFS vs EBS vs S3

by scmgalaxy KUncategorizedLeave a Comment on Difference between AWS EFS vs EBS vs S3

1 GB to store in US-East-1: (Updated at 2016.dec.20)

  • Glacier: $0.004/Month (Note: Major price cut in 2016)
  • S3: $0.023/Month
  • S3-IA (announced in 2015.09): $0.0125/Month (+$0.01/gig retrieval charge)
  • EBS: $0.045-0.1/Month (depends on speed – SSD or not) + IOPS costs
  • EFS: $0.3/Month

Further storage options, which may be used for temporary storing data while/before processing it:

  • SNS
  • SQS
  • Kinesis stream
  • DynamoDB, SimpleDB

The costs above are just samples. There can be differences by region, and it can change at any point. Also there are extra costs for data transfer (out to the internet). However they show a ratio between the prices of the services.

There are a lot more differences between these services:

EFS is:

  • Generally Available (out of preview), but may not yet be available in your region
  • Network filesystem (that means it may have bigger latency but it can be shared across several instances; even between regions)
  • It is expensive compared to EBS (~10x more) but it gives extra features.
  • It’s a highly available service.
  • It’s a managed service
  • You can attach the EFS storage to an EC2 Instance
  • Can be accessed by multiple EC2 instances simultaneously
  • Since 2016.dec.20 it’s possible to attach your EFS storage directly to on-premise servers via Direct Connect. ()

EBS is:

  • A block storage (so you need to format it). This means you are able to choose which type of file system you want.
  • As it’s a block storage, you can use Raid 1 (or 0 or 10) with multiple block storages
  • It is really fast
  • It is relatively cheap
  • With the new announcements from Amazon, you can store up to 16TB data per storage on SSD-s.
  • You can snapshot an EBS (while it’s still running) for backup reasons
  • But it only exists in a particular region. Although you can migrate it to another region, you cannot just access it across regions (only if you share it via the EC2; but that means you have a file server)
  • You need an EC2 instance to attach it to
  • New feature (2017.Feb.15): You can now increase volume size, adjust performance, or change the volume type while the volume is in use. You can continue to use your application while the change takes effect.

S3 is:

  • An object store (not a file system).
  • You can store files and “folders” but can’t have locks, permissions etc like you would with a traditional file system
  • This means, by default you can’t just mount S3 and use it as your webserver
  • But it’s perfect for storing your images and videos for your website
  • Great for short term archiving (e.g. a few weeks). It’s good for long term archiving too, but Glacier is more cost efficient.
  • Great for storing logs
  • You can access the data from every region (extra costs may apply)
  • Highly Available, Redundant. Basically data loss is not possible (99.999999999% durability, 99.9 uptime SLA)
  • Much cheaper than EBS.
  • You can serve the content directly to the internet, you can even have a full (static) website working direct from S3, without an EC2 instance

Glacier is:

  • Long term archive storage
  • Extremely cheap to store
  • Potentially very expensive to retrieve
  • Takes up to 4 hours to “read back” your data (so only store items you know you won’t need to retrieve for a long time)

There are several interesting aspects in terms of pricing. For example Glacier, S3, EFS allocates the storage for you based on your usage, while at EBS you need to predefine the allocated storage. Which means, you need to over estimate. ( However it’s easy to add more storage to your EBS volumes, it requires some engineering, which means you always “overpay” your EBS storage, which makes it even more expensive.)

Source

https://stackoverflow.com/questions/29575877/aws-efs-vs-ebs-vs-s3-differences-when-to-use

Tagged : / / /

DevOps Engg Full-Time Position In SFO

by scmgalaxy KGeneralLeave a Comment on DevOps Engg Full-Time Position In SFO

DevOps Engineer (California Fulltime)
To support our key business initiatives, we are looking for a DevOps Engineer to build innovative and highly scalable solutions to help build best in class CI/CD pipeline by making use of cutting edge technologies and tools. Also, build a world-class infrastructure that could span across cloud, bare metal and/or a hybrid environment to support our DevOps ambitions. We believe in building incrementally, thoughtfully managing what we have, automating “all the things,” continuously integrating and delivering, prioritizing the many exciting projects on the roadmap, and, above all working together.

Responsibilities

• Support and improve our tools for continuous build, automated testing and release management
• Streamline, standardize and automate build and release processes
• Provide automation and provisioning through use of configuration management tools
• Continuously look to improve the efficiency of our build/release/deploy process (via automation, new tools), driving towards the implementation of Continuous Delivery
• Communicate and collaborate among cross-functional teams in a multinational environment
• Manage our infrastructure on AWS and our own Datacenters
• Ability to work in an agile way with complex systems and regulated environment

Qualifications

• 5+ years’ experience as a build/release engineer or similar role with hands on experience working with enterprise products
• A fast learner, self-starter with DevOps mindset and proponent of software development best practices
• Proficient in various programming and scripting languages, especially Python, Ruby, and shell scripting
• Experience with latest tools in the Continuous Integration Space, e.g. Jenkins, FinalBuilder, MSBuild, ANT, Maven
• Experience with version control tools like SVN, TFS, Git and managing branching strategy
• Knowledge of version control, build, packaging, and release workflows
• Experience of dealing with build failures, debugging and fixing the issues
• Experience with AWS (Amazon Web Services) hosting, VMware virtualization, VMware ESX, Linux, and Windows experience
• Experience in any of the configuration management tools like Chef, Puppet, Salt, Ansible is a big plus
• Experience working in a regulated environment, and familiarity with security analysis tools such as Fortify is a plus

Tagged : / /

How to Setup AWS Credentials using AWS Command Line Interface?

by scmgalaxy KAmazon Web ServicesLeave a Comment on How to Setup AWS Credentials using AWS Command Line Interface?

setup-aws-credentials-using-aws-command

Setup AWS Credentails using AWS Command Line Interface

Install the AWS CLI Using Pip
Please click here complete installation guide.

Test the AWS CLI Installation

 $ aws help

Environment Variables – 

  • AWS_ACCESS_KEY_ID
  • AWS_SECRET_ACCESS_KEY

Step 5: Get a key aws_access_key_id, aws_secret_access_key, region from AWS website, under your 

$ aws configure

Step 6: Setup AWS with key

$  aws configure
AWS Access Key ID [None]: AKIAJB6WCXXXXRKRT5SQ
AWS Secret Access Key [None]: fDBVPhlHzMk70ip5FGHDl/AcmEyMnylwOllc+n4s
Default region name [None]: us-east-1
Default output format [None]:
$  aws s3 list

Step 7: Verify details in ~/.aws/credentials and ~/.aws/config

$ more ~/.aws/credentials
[default]
aws_access_key_id = AKIAJB6WCXXXXRKRT5SQ
aws_secret_access_key = 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

$  more ~/.aws/config
[default]
region = us-east-1

Step 8: Verify AWS CLI setup

$ aws ec2 describe-instances --output table --region us-west-2

The AWS credentials file –

Located at ~/.aws/credentials on Linux, OS X, or Unix, or at C:\Users\USERNAME \.aws\credentials on Windows. This file can contain multiple named profiles in addition to a default profile.

The CLI configuration file –

Typically located at ~/.aws/config on Linux, OS X, or Unix, or at C:\Users\USERNAME \.aws\config on Windows. This file can contain a default profile, named profiles, and CLI specific configuration parameters for each.

Reference
http://docs.aws.amazon.com/cli/latest/userguide/installing.html
http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html
http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html

Tagged : / / / / / / / / / / / / / /