AWS EC2 Best practices

AWS EC2 Best practices
AWS recommends these best practices to maximize the benefits and satisfaction of EC2
Security & Network
For security group, use the most permissive rules.
Regularly patch, update and secure the operating system, as well as the applications, on the instance
Use identity federation, IAM user and IAM roles to manage access to AWS resources.
Credential management policies and procedures should be established for creating, distributing and rotating AWS access credentials.
If the AWS account has been newly created, VPC will be used by default.
Securely encrypt EBS volumes and snapshots
EC2 supports Instance Store and EBS volumes. It is important to understand the implications for root device type for data persistence and backup.
Separate Amazon EBS volumes should be used for the root device (operating system) and your data.
Ensure that the data volume (with data) persists after an instance termination.
To store only temporary data, you can use the instance store. Keep in mind that data stored in the instance stores is deleted when an instance terminates or is stopped.
Instance Store database storage requires that you have a cluster with a replication factor that guarantees fault tolerance. Resource Management
To track and identify your AWS resources, you can use custom resource tags and instance metadata
Check out your Amazon EC2 limits. You should request any limit increases well in advance of when you will need them.Backup and Recovery
Backup the instance regularly using Amazon EBS snapshots (not automatically) or another backup tool.
Data Lifecycle Manager (DLM), automates the creation, retention and deletion of snapshots taken for back up EBS volumes
To save the configuration as an AMI (Amazon Machine Image) for future instances, create an instance.
Implement High Availability by deploying critical components across multiple Availability Zones and replicating the data accordingly
Respond to and monitor events.
You should design the applications to handle dynamic IP address when the instance is restarted.
Implement failover. As a starting point, you can attach a network interface to a replacement instance.
Refer to references

Posted in Uncategorized | Leave a comment

AWS EC2 Amazon Machine Image- AMI

Amazon Machine Image – AMI
An Amazon Machine Image – AMI is the information needed to launch an instance. This is a virtual server that runs in the cloud.
An AMI is essentially a template that can be used to launch as many instances of the same thing.
Instances can be launched from as many AMIs as you like within a VPC
An AMI includes the following:One or more EBS snapshots, or, for instance-store-backed AMIs, a template for the root volume of the instance for e.g, an operating system, an application server, and applications
Launch permissions are used to control which AWS accounts have access to the AMI to launch instances, e.g. AWS account IDs with which the AMI is shared
Block device mapping that specifies which volumes will be attached to the instance at launch
AMIs can either be provided, managed, or published.
AMIs that are provided by third-party or community providers of public custom
Private AMIs are created by other AWS accounts, and shared with you
YouAMI Types creates private and custom AMIs
Region & Availability ZoneAMIs can be copied to other regions, but they are regional.
Operating systemAMIs can be found in many OS flavors, such as Linux, Windows, ubuntu, etc. Linux, windows, ubuntu, etc
Architecture (32-bit and 64-bit)
Launch PermissionsLaunch Permissions – These permissions determine who has access the AMIPublic – Accessible to all AWS account
Explicit – Shared by specific AWS accounts
Private/Implicit – Only available for AMI creator accounts
Root device storageAMIs may have EBS or Instance storage as their root device storage
EBS backedEBS volumes can be maintained independently of the EC2 lifecycle.
EBS-backed instances can be stopped without affecting volumes
If the Delete On Termination flag has been disabled, EBS instances can be continued without losing volumes upon termination.
EBS-backed instances boot up faster than Instance store-backed instances, as only the parts that are required to boot the instance need to be retrieved form the snapshot before they are made available.
AMI creation is easier when AMIs are backed by EBS. The CreateImage API action registers the EBS-backed AMI.
Instance Store backedInstance Store is ephemeral storage that is dependent on the Instance’s lifecycle
If the instance is stopped or terminated, the instance store is deleted.
The volume of the instance store cannot be stopped
Instance store volumes have an AMI in S3 and take longer to boot than EBS-backed instances. This is because all the parts must be retrieved from S3 before an instance can be made available.
To create Linux AMIs backed up by the instance store, you need to create an AMI from your instance using the Amazon EC2 AMI Tools.
Linux Virtualization Types
Linux Amazon Machine Images can use either paravirtual (PV), or hardware virtual machine(HVM) virtualization.
The main difference between PV AMIs and HVM AMIs lies in the way they boot and whether they can use special hardware extensions (CPUs, networks, and storage) to improve performance.
AWS recommends that you use the most current generation of instance types and HVM AMIs for launching instances to get the best performance.
HVM AMIsHVM aMIsHVM aMIs are presented with a fully-virtualized set of hardware and boot by execution of the master boot record from the root block device.
The HVM virtualization type allows you to run an operating system directly on top a virtual machine, without any modifications, as if it were running on bare-metal hardware.
The EC2 host system emulates a portion or all of the underlying hardware presented to the guest.
HVM guests can, unlike PV guests have fast access to the underlying hardware of the host system.
To take advantage of enhanced networking or GPU processing, HVM AMIs must be used. To pass instructions to specialized network or GPU devi

Posted in Uncategorized | Leave a comment

AWS EBS vs Instance Store

AWS EBS vs Instance Store
Two types of block level storage are supported by EC2 instancesElastic Block Store and EBS.
Instance Store (Ephemeral Store)
EC2 Instances may be launched using either Elastic Block Store or Instance Store volumes as root volumes and additional volumes.
You can launch EC2 instances by choosing between AMIs backed with EC2 instance store or AMIs supported by EBS. AWS recommends that you use EBS-backed AMIs to launch EC2 instances. They launch faster and use persistent storage.
Instance store volumes allow you to access storage from disks that are physically attached.
An Instance stored instance is launched when the image used to boot it is copied to its root volume (typically sda1).
Instance store is temporary block-level storage that can be used to store instances.
Key points for Instance store backed Instance
Boot time is usually shorter than EBS backed volumes, and typically takes less than 5 minutes.
Can be used as a Root Volume and attached to other volumes
Instance store backed instances can have a maximum volume of 10GiB
Instance store volume can only be attached as additional volumes when the instance launches. They cannot be attached after the Instance is running.
Instance store backed Instances can’t be stopped. AWS doesn’t guarantee that the instance will be launched on the same host if it is stopped and restarted. Therefore, data is lost.
Data on Instance store volume is lost in the following scenarios.-Failure to install an underlying drive
Stopping an EBS-backed example where instance stores have been attached as additional volumes
Termination of the Instance
When the instance is restarted, data on the Instance store volume is not lost
AWS recommends that you distribute the data from EC2 instance stores across multiple AZs in order to support instances that are backed by EC2.
Backup critical data from the instance storage volumes to persistent storage on an ongoing basis.
Instance store-backed Instances can’t be upgraded
Elastic Block Store (EBS). An “EBS-backed” instance is one that is backed by an EBS volume. This volume was created from an EBS snapshot.
An EBS volume behaves as a raw, unformatted external block device that can attach to one instance. It is not physically attached (more like network-attached storage).
Volume is independent of the instance’s running life.
Once an EBS volume has been attached to an instance you can use it as any other physical hard disk.
EBS volume can be detached and attached to another instance
EBS volumes can also be encrypted using the EBS encryption featureKey points to EBS backed Instance
Boot time is usually very short, often less than a minute
Can be used as a Root Volume and attached to other volumes
EBS-backed Instances can have a maximum 64TiB volume size, depending on the OS.
EBS volume can also be added to the Instance as an additional volume when it is launched or when it is running.
If the Delete On Termination flag has been enabled, data on the EBS root volume is lost.
Attached EBS volumes if the Delete On Termination flag has been enabled It is disabled by default. Data on EBS volumes is NOT lost in the following scenarios.
Stopping an EBS-backed case
Termination of the Instance regarding additional EBS volumes Additional EBS volumes can be removed with all data intact
EBS-backed instances can be stopped in various volume- and instance-related tasks

Posted in Uncategorized | Leave a comment

AWS EBS Volume Types

AWS EBS Volume Types
AWS offers the following EBS volume types. They differ in price and performance, and can be customized to meet storage and cost needs.
Solid state drives (SSD-backed), volumes optimized for transactional workloads that involve frequent read/write operations with low I/O sizes. The dominant performance attribute of IOPSGeneral Purpose SSD is gp2/gp3.
Provisioned IOPS SSD SSD (io1/io2)
HDD-backed volumes of hard disk drives (HDD) are optimized for large streaming workloads. Throughput (measured as MiB/s is a better performance measurement than IOPSThroughput Optimized HDD [st1]).
Cold HDD (sc1)
Magnetic Volumes (standard) (Previous Generation)EBS Volume Types (New Generation)Solid state drives (SSD-backed) volumesGeneral Purpose SSD Volumes (gp2/gp3)
SSD volumes for general purposes are cost-effective storage that can be used for a wide range of workloads.
General Purpose SSD volumes deliver single-digit millisecond latencies
The general purpose SSD volumes can be as small as 1 GiB up to 16 TiB.
Volumes of General Purpose SSD (gp2) have a maximum throughput rate of 160 MiB/s (at least 214 GiB).
Provides a baseline performance of 3 IOPS/GiB
Provides the ability to burst up to 3,000 IOPS over extended periods of time for volumes less than 1 TiB, and up to a maximum 16,000 IOPS (at 5.334 GiB).
If the volume performance is not as good as the baseline level due to an empty I/O credit, you might consider using a larger General Purpose SSD volume (with higher baseline performance)
For workloads that require IOPS performance greater then 16,000 IOPS, you can switch to a Provisioned SSD volume.
Volumes of General Purpose SSD (gp3) storage are provided with a baseline rate of 3,000 IOPS, 125 MiB/s, and are included in the price of storage.
Additional IOPS (upto 16,000) or throughput (upto 1,000 MiB/s), can be provided at an additional cost.
The maximum ratio of provisioned IOPS and provisioned volume size to provisioned IOPS is 500 IOPS/GiB
Provisioned throughput to provisioned IOPS is at.25 MiB/s. I/O Credits and Burst Performance
I/O credits are the bandwidth that the General Purpose SSD volume has available to burst large amounts I/O when it is required beyond the baseline performance.
Volume size determines the volume performance for general purpose SSD (gp2) volumes. This is the benchmark performance level of the volume, for e.g. 100 GiB volume has 300 IOPS @ 3IOPS/GiB
The general purpose SSD volume size determines how quickly it accumulates I/O credit for e.g. 100 GiB can accumulate 180K IOPS/10 minutes with a performance of $300 IOPS (300 * 60* 10).
Larger volumes have a higher baseline performance and accumulate I/O credit faster for e.g. 1 TiB has a baseline performance level of 3000 IOPS
The volume’s I/O credits are more valuable than its baseline performance level. It can also burst faster when it needs more performance, such as when it is running at 3000 IOPS for 1 minute. 300 GiB volume can burst at 3000 IOPS in 1 minute (180K/3000).
Each volume receives an I/O credit balance equal to 5,400,000 I/O credits. This is sufficient to sustain the maximum burst performance for 30 minutes at 3,000 IOPS.
The initial credit balance is designed for a quick boot cycle for boot volumes, and a great bootstrapping experience with other applications.
Each volume can accumulate I/O credit over a time period that can be used to increase performance up to a maximum of 3,000 IOPS
Unutilized I/O credit cannot exceed 54,00,000.
Volumes up to 1 TiB can explode up to 3000 IOPS above and beyond its baseline performance
Volumes greater than 1 TiB have a baseline performance equal to or higher than the maximum burst performance. Their I/O credit balance is never exhausted.
For General Purpose SSD volumes, the baseline performance cannot exceed 10000 IOPS. This limit is reached @ 3333 GiB
Baseline Performanc

Posted in Uncategorized | Leave a comment

Snapshot AWS EBS

EBS Snapshot
EBS allows you to create snapshots (backups), and then write a copy to S3. The volume’s data is redundantly stored in multiple Availability Zones.
Snapshots can also be used to create new volumes or increase the volume of existing volumes.
Snapshots are incremental backups that store only the data that has changed since the last snapshot was taken.
Snapshots can be smaller than volume because the data is compressed before being saved as S3
Although snapshots are saved incrementally over time, the snapshot deletion process requires that you only retain the most recent snapshot to restore the volume.
Multi-Volume Snapshots
Snapshots can be used for backups of critical workloads such as large databases or file systems that span multiple EBS volumes.
Multi-volume snapshots allow you to take precise point-in-time, crash-consistent snapshots of multiple EBS volumes attached at an EC2 instance.
EBS Snapshot creation
Snapshots can also be created periodically from EBS volumes and are point-in time snapshots.
Snapshots are incremental. They only store the blocks that have changed since the last snapshot was taken.
Snapshots are created asynchronously. The snapshot is created instantly while the modified blocks are uploaded to S3. While the snapshot is being completed, it is not affected by ongoing reads or writes to the volume.
Snapshots can also be taken from volumes that are not in use. Snapshots can only capture data that was written to EBS volumes at the time of the snapshot command is issued. This excludes data that is cached by OS applications.
The best way to create a Snapshot using an EBS volume is to stop all file writes to it
Take a Snapshot -> Unmount the Volume
Stop the instance – Take Snapshot
EBS volume created from a snapshotbegins is an exact replica the original volume that was used for the snapshot.
Data from replicated volume loads can be stored in the background, so it can be used immediately.
If data is not loaded yet, the volume downloads the requested data immediately from S3 and then continues loading all the data in the background. EBS Snapshot Deletion
Only the snapshot data is deleted when a snapshot is deleted.
The ability to restore volumes from earlier snapshots of a volume is not affected by the deletion of previous snapshots.
Active snapshots contain all the information required to restore your data (from when the snapshot was taken) and to create a new EBS volume.
Although snapshots are saved incrementally over time, the snapshot deletion process requires that you only retain the most recent snapshot to restore the volume.
Snapshot of root device of EBS volume used to register AMI cannot be deleted. To delete the snapshot, AMI must be deregistered.
Snapshots are limited to the region where they were created. They can only be used to launch EBS volumes in the same region.
Snapshots can also be copied across regions, making it easier to use multiple regions for geographic expansion, data center migration and disaster recovery.
Snapshots are copied using S3 server-side encryption (256 bit Advanced Encryption standard) to encrypt data. The snapshot copy also receives an ID that is different from the original snapshot’s ID.
User-definable tags are not copied from the source to a new snapshot.
The first Snapshot copy to another area is always a complete copy, while the rest are a summary.

Posted in Uncategorized | Leave a comment

Microsoft Azure vs Amazon AWS

Your organization may be leveraging cloud-based services for cost savings, pay-as you-go, or because of the built-in security or data resilience. Or at least that’s the data suggesting. Today, up to 82% of workloads are hosted in the cloud and 67% of enterprise infrastructure is cloud-based.
As businesses consider moving to the public cloud, one question continues to be asked by cloud enthusiasts, business leaders, and engineers: Which cloud is better, Amazon AWS or Microsoft Azure? There are many factors that will impact your decision on which cloud is best for you.
We’ll be comparing the similarities and differences between Microsoft Azure, Amazon AWS, and hopefully you will leave with a better understanding of which cloud — Microsoft Azure, or Amazon AWS — is best for your business.
An Overview of Amazon AWS and Microsoft Azure
Amazon AWS is the market leader for public cloud services, with 33% of global market share. Microsoft Azure currently holds 13%. Both Amazon AWS and Microsoft Azure offer similar cloud-centric features, including subscription pricing, consumption-based pricing, native security features, autoscaling and identity access management, high availability and inexpensive object-based storage, as well as instant provisioning.
Both Amazon AWS and Microsoft Azure are aligned on the majority of services. For casual cloud practitioners, either Microsoft Azure or Amazon AWS can be a great match. In the following sections we will examine some of the differences between these cloud offerings. Let’s start by looking at some of the similar features and services offered by Amazon AWS and Microsoft Azure.
What are the Computing Differences in AWS & Azure?
Computing capabilities are at the top of every IT department’s priority list. Computing capabilities can make or break a business’s ability to perform highly transactional and computationally-intensive processes.
AWS deployments will rely on virtual machine instances within AWS, also known as elastic cloud computing (EC2 instances) or elastic cloud computing. AWS allows users to create their own virtual machines and have the freedom to select the size, power, and other resources.
To create a virtual machine, users can use Microsoft Azure to create a virtual disk (or (VHD). After creating a virtual machine, users can scale it accordingly. The main take-home is that EC2 users can customize their virtual machines based upon resources, while Microsoft Azure users rely only on a base function VM which integrates with Microsoft Azure services.
AWS and Azure Network and Content Delivery
Cloud-based networking is used to keep cloud environments private and secure, and also allow communication between multiple locations.
Amazon AWS addresses this issue by providing a virtual private network (VPC) that users can use to isolate their AWS environment. APIs can then be used to enable communication between VPCs and between AWS environments and on-premises networks.
Microsoft Azure approaches cloud networking in a slightly different way. Microsoft Azure is not a VPC like AWS. Instead, it offers users a private network in which they can configure the subnet, IPs and DNS just like an on-premises IT environment.
Azure offers vNet instead of a VPC. This virtual network allows users to create isolated networks as well as subnets and private IP ranges. Route tables can also be created.

Posted in Uncategorized | Leave a comment

Microsoft Azure roadshow – Learn and Network with 4 Free

Microsoft Azure roadshow ,Erdal Ozkaya
Erdal Ozkaya, CISO of Microsoft Azure, was announced as one of the key speakers at the Microsoft Azure roadshow in Abu Dhabi and Bahrain. He will also address the Kuwait roadshow on 2nd June 2015.
Azure is the Microsoft cloud platform. It is nothing but a growing collection integrated services–compute storage, data networking, and app–that help businesses move faster and do more. It is the only major cloud platform ranked by Gartner as an industry leader for both infrastructure-as-a-service (IaaS) and platform-as-a-service (PaaS). Enterprises can build, deploy, manage, and maintain applications using this powerful combination of managed services and unmanaged services. It runs on a growing global network with Microsoft-managed datacenters in 19 regions. This gives you a wide range options for running applications and great performance.
Ozkaya gave a presentation during the roadshow and went into detail about Microsoft Azure Security. Ozkaya explained the basics of Azure security, including network security, threat defense, and data protection, as well as the commitments Azure makes in protecting customer data privacy.
Ozkaya expressed his delight at his participation in the roadshow and stated that it was a “confluence of like-minded people who have come together to share their experiences, learn from each other.” Roadshows like these benefit the entire eco-system: customers, developers, partners and developers all have to win.
Ozkaya presented on enterprise mobility, BYOD and Software as a Service (SaaS) as well as discussing cloud security. He also shared best practices for staying safe in a digital world. He ended the presentation with an open discussion for the audience to discuss security issues.
Read more at 2015/05/24/emts-ciso-erdal-addresses-microsoft-azure-roadshow/#oii83lEjSPWb2ReZ.99
emt CISO highlights the fundamentals of Azure security including threat defense, network security and data protection
Erdal Ozkaya, emt Distribution CISO, was one of the key speakers at the Microsoft Azure roadshow in Abu Dhabi and Bahrain. Ozkaya will also address the Microsoft Azure community at the roadshow in Kuwait, 2nd June 2015.
Ozkaya expressed his delight at his participation in the roadshow and stated that it was a “confluence of like-minded people who have come together to share their experiences, learn from each other.” Roadshows like these benefit the entire eco-system: customers, developers, partners and developers all have to win.
Ozkaya presented on enterprise mobility, BYOD and Software as a Service (SaaS) as well as discussing cloud security. He also shared best practices for staying safe in a digital world. He ended the presentation with an open discussion for the audience to discuss security issues.

This news was published in
Erdal in the news:
More Free Events

Posted in Uncategorized | Leave a comment

Microsoft Azure Camp – Join us 4 Free

Microsoft Azure Camp
Table of Contents

This free training event will provide the knowledge and skills necessary to integrate cloud solutions with your existing on-premises datacenters without compromising security, control, reliability, or scalability.
You will be amazed at how Azure infrastructure services allow you to provide reliable data access and maximize productivity across platforms, including Open Source (OSS), Microsoft, and other.
If you are an IT operations/infrastructure professional and have a keen interest in understanding Azure Infrastructure solutions, join this IT Innovation Series event for first hand experiences with real-world scenarios around Microsoft Azure.
Event Code: 1032692567Event Name: Microsoft Azure IT CampStart Date: 11/23/2015Start Time: 9:30 AM (GMT+04:00) Abu Dhabi, Muscat End Date: 11/23/2015 End Time: 6:00 PM (GMT+04:00) Abu Dhabi, Muscat
Location: H HotelSheikh Zayed RoadDubaiUnited Arab Emirates
Register now : click/services/Redirect2.ashx?CR_CC=200702438&CR_EAC=300322479
09:30 – 10:00Introduction10:00 – 10:30Keynote10:30 – 11:30Module 1: Deployment with Azure Resource Manager Templates and GIT11:30 – 11:45Networking11:45 – 12:45Module 2: Designing an Azure Compute and Storage Infrastructure (standard and premium) for Advanced Performance12:45 – 02:00Lunch02:00 – 03:00Module 3: Designing an Azure Networking Infrastructure for Advanced Security03:00 – 04:00Module 4: ASR Recovery for Protection and Migration from on-premises04:00 – 04:15Networking04:15 – 05:15Module 5: Designing Identity Solutions with Azure Active Directory05:15 – 05:30Wrap Up05:30 – 06:00Certificates & Free Exam Vouchers Distribution

What is Azure?
The Azure cloud platform includes more than 200 products and services that can be used to bring new solutions to life. With the tools and frameworks you choose, you can build, run, and manage apps across multiple clouds.
Trust your cloud
Secure your business from the ground up with the support of a team seasoned experts and proactive compliance that is trusted by governments, startups, and enterprises.
Operate hybrid seamlessly
We can meet you at the edge, on-premises, or across multiple clouds. Services designed for hybrid cloud allow you to integrate and manage your environments.
You can build on your terms
Open source is a commitment. We support all languages and frameworks. You can build what you want and deploy it where you want.
Be ready for the future
Microsoft supports you in your development today and your product visions tomorrow with continuous innovation.
Operate hybrid seamlessly
We can meet you at the edge, on-premises, or across multiple clouds. Services designed for hybrid cloud allow you to integrate and manage your environments.
You can build on your terms
Open source is a commitment. We support all languages and frameworks. You can build what you want and deploy it where you want.
Be ready for the future
Microsoft supports you in your development today and your product visions tomorrow with continuous innovation.
Solutions do the hard work
Azure solutions can help you solve your business problems. They bring together all the relevant products, services and third-party apps. You’ll be able to quickly get up and running with a cost-effective, scalable solution that integrates with your existing investments, from DevOps to Business Analytics to the Internet of Things.

Posted in Uncategorized | Leave a comment

Metin Tuncdoruk, Group Sales Manager, CE0 Training

Metin Tuncdoruk’ Feedback
Erdal, CEO IT Training, has been a friend for nearly 2 years. Erdal is a hardworking, focused, and driven individual. He is always enthusiastic, generous with time, and willing to help his students and his peers. He is one of the most entertaining and knowledgeable trainers I have ever had the pleasure to work alongside.
His students love him and he makes my life so much easier by making sure our clients return to Erdal. He is a great team player, a great teacher, and communicator. His personality is wonderful and he is very approachable. Erdal is well-known worldwide. He can speak four languages fluently, and has even been known to use all four together in one sentence. Erdal is highly sought after worldwide and has won numerous awards. Erdal is a great IT Trainer and I would recommend him for any role. Erdal is capable of doing anything he wants.
Metin Tuncdoruk, Group Sales Manager, CEO Training (2011)

Five Reasons Feedback is Important
Karen Neuman
Many of us are approaching the end of the year which means that feedback and year-end conversations will be in the air. Do you remember when the last time someone gave you feedback on something that you did not do in a scheduled feedback session.
If you find yourself thinking for more than 10 seconds, it is most likely too long ago. Although feedback is often frowned upon or even feared by many societies, it can be one of the most valuable gifts you can give or receive from someone. Sometimes, it can be the last push you need in order to get out of your comfort zone and do what you thought impossible.
As demonstrated by many great leaders, leadership is about supporting and encouraging talent. A true leader knows that a company or team can only be as successful and as great as its people. Without feedback, flowers won’t blossom.
Here are 5 reasons feedback is so important in our private and professional lives.
1. It can keep us going. Feedback comes in many forms, both positive and negative. However, it should always be constructive. Although it is subjective, it is often very useful. I am amazed at how many people use absolute terms during feedback sessions, especially as a counselor. When that one time you are not prepared or delivering the best presentation possible, it becomes “you are never prepared!” Or “You are not a good presenter.”
These final and absolute statements can be fatal to self-esteem, motivation and self-development and most importantly, to our happiness. These absolute statements can also set off a chain reaction that can lead to self-fulfilling prophecy, depression, psychosomatic symptoms, and sick-leaves at end.
Before giving feedback to someone, it is important to examine our motives and mood. This includes whether we feel angry, jealous, afraid, stressed, or just plain antipathy towards them. Then, it is up to us to look at the performance and goals of the other person professionally.
Sam Walton said it so beautifully:
“Outstanding leaders go above and beyond to improve the self-esteem of their employees.” It’s amazing what people can achieve if they believe in themselves.
2. It gives us a sense of belonging and purpose.
“The deepest principle in human nature is the desire to be appreciated. “William James
Many schools of psychology recognized the importance of feeling connected and appreciated from an early stage. As human beings, our core values are to feel valued, needed and appreciated.

Posted in Uncategorized | Leave a comment

Mercedes Benz AMG Data Breach 2021

Mercedes Benz AMG Data Breach
Table of Contents

I regret to inform you all that I received an email from Mercedes Benz AMG stating that my data, which they hold, has been hacked. I am also one of the 1000 AMG victims. Here are the details of the Mercedes Benz Data Breach details.
What happened?
The breach was discovered by an external security expert, who reported it to Mercedes. Mercedes then resolved the problem. Mercedes stated that it had notified the appropriate government agencies and that it has begun contacting those affected by the incident.
What is leaked?
Potential buyers’ driver’s license numbers, credit card details, social security numbers, and credit card details could have been exposed during the affected timeframe. The data leak also includes credit ratings and birth dates.
The majority of the personal information exposed includes names, phone numbers, addresses, email addresses, and addresses of customers. Mercedes stated that anyone whose personal data was compromised would receive a credit monitoring subscription for one year.
Mercedes-Benz claimed that in order to access the information, one must be familiar with specific software tools and applications. Furthermore, a search on the internet would not reveal any data contained within such documents.
This is the second German Car manufacturer to be affected by the data leak. Volkswagen revealed that over 3.3 million clients and Audi’s luxury automobile affiliate Audi were affected by a data breach. This leakage lasted more than two years.
A vendor informed Mercedes-Benz on June 11, 2021 that the cloud storage platform had inadvertently made sensitive personal information of less 1,000 Mercedes-Benz customers and potential buyers available. This confirmation was part an ongoing investigation that was conducted in collaboration with the vendor. An external security researcher was able to uncover the issue. We believe that the information was entered by customers or interested buyers on dealer or Mercedes-Benz websites between January 1, 2014. and June 19, 2017. This incident did not compromise any Mercedes-Benz systems. We also have no evidence that any Mercedes-Benz files had been maliciously misused.
MBUSA is concerned about data security. Our vendor confirmed that the issue has been resolved and that it cannot be repeated. We will continue to investigate the situation to ensure that it is appropriately addressed.
According to the vendor, the personal information of these individuals (less then 1,000) consists mainly of self-reported credit scores, as well as very few driver license numbers, social insurance numbers, credit card information, and dates of birth. The information would require special software programs and tools to view it. An Internet search would not return any of the files. (Heimdal Security)

About Mercedes Benz
Mercedes-Benz’s history and origin.
Mercedes-Benz history begins in 1886, when Karl Benz, an engineer, invented the first car. This invention set the standard for innovation and technology that is still evident today.
Gottlieb Daimler und Karl Benz
Gottlieb Daimler, Karl Benz and others invent the high-speed engine and automobile independently in the 1880s. This laid the foundations of motorised private transport. Both engineers were able to do private development work with the support of financial backers and their partners. Benz founded Benz & Co. Rheinische Gasmotoren-Fabrik in Mannheim in October 1883; the Daimler-Motoren-Gesellschaft (DMG) was founded in Cannstatt in November 1890.
Both companies wanted a distinctive trademark to distinguish their products and make them more familiar. They chose their initial names Benz and Daim.

Posted in Uncategorized | Leave a comment