Soal Wawancara AWS

A VPC is the best way of connecting to your cloud resources from your own data center. Once you connect your datacenter to the VPC in which your instances are present, each instance is assigned a private IP address that can be accessed from your data center. That way, you can access your public cloud resources as if they were on your own private network.

Amazon Route 53 is a scalable and highly available Domain Name System (DNS). The name refers to TCP or UDP port 53, where DNS server requests are addressed.

Amazon Web Services (AWS) is a cloud computing platform that offers a vast range of services, including computing power, storage, and databases, to help businesses scale and grow more cost-effectively.

Key Features of AWS

1. Scalability and Elasticity: AWS provides tools that allow for both vertical and horizontal scaling, as well as the ability to auto-scale based on demand.

1. Global Reach: With data centers in multiple geographic regions, AWS enables businesses to operate on a global scale while remaining compliant with local regulations.

1. Pay-As-You-Go Pricing: This flexible pricing model allows users to pay only for the resources they consume, reducing upfront costs.

1. Security and Compliance: AWS offers a variety of security tools and features to help protect data, as well as compliance with numerous industry standards.

1. Hybrid Capabilities: AWS supports hybrid architectures, allowing businesses to integrate their existing on-premises solutions with the cloud.

1. Artificial Intelligence and Machine Learning: With AWS, businesses can harness the power of AI and ML through accessible services for data processing, analysis, and more.

1. Developer Tools: From code repository management to continuous integration and deployment, AWS provides a comprehensive suite of developer-centric services.

1. Internet of Things (IoT): AWS offers capabilities for managing and processing IoT data, connecting devices securely to the cloud.

While you may think that both stopping and terminating are the same, there is a difference. When you stop an EC2 instance, it performs a normal shutdown on the instance and moves to a stopped state. However, when you terminate the instance, it is transferred to a stopped state, and the EBS volumes attached to it are deleted and can never be recovered.

Identity and Access Management (IAM) is a web service for securely controlling access to AWS services. IAM lets you manage users, security credentials such as access keys, and permissions that control which AWS resources users and applications can access.

EC2 is short for Elastic Compute Cloud , and it provides scalable computing capacity. Using Amazon EC2 eliminates the need to invest in hardware, leading to faster development and deployment of applications. You can use Amazon EC2 to launch as many or as few virtual servers as needed, configure security and networking, and manage storage. It can scale up or down to handle changes in requirements, reducing the need to forecast traffic. EC2 provides virtual computing environments called “instances.”

S3 is short for Simple Storage Service, and Amazon S3 is the most supported storage platform available. S3 is object storage that can store and retrieve any amount of data from anywhere. Despite that versatility, it is practically unlimited as well as cost-effective because it is storage available on demand. In addition to these benefits, it offers unprecedented levels of durability and availability. Amazon S3 helps to manage data for cost optimization, access control, and compliance.

The three basic types of cloud services are:

• Computing
• Storage
• Networking

Here are some of the AWS products that are built based on the three cloud service types:

Computing - These include EC2, Elastic Beanstalk, Lambda , Auto-Scaling, and Lightsat.

Storage - These include S3, Glacier, Elastic Block Storage, Elastic File System.

Networking - These include VPC , Amazon CloudFront , Route53

The Key-Pairs are password-protected login credentials for the Virtual Machines that are used to prove our identity while connecting the Amazon EC2 instances. The Key-Pairs are made up of a Private Key and a Public Key which lets us connect to the instances.

EBS is a kind of permanent storage in which the data can be restored at a later point. When you save data in the EBS, it stays even after the lifetime of the EC2 instance. On the other hand, Instance Store is temporary storage that is physically attached to a host machine. With an Instance Store, you cannot detach one instance and attach it to another. Unlike in EBS, data in an Instance Store is lost if any instance is stopped or terminated.

Elastic Computing in AWS refers to the ability to dynamically adjust your computing needs based on real-time demands and pay only for what you use. This is achieved through services like Amazon EC2.

Key Features

• Scalability: EC2 instances can be scaled up or down to accommodate varying workloads.
• Load Balancing: Multiple EC2 instances can distribute incoming traffic for improved performance.
• Auto Scaling Groups: EC2 instances can be automatically scaled in response to changing demand patterns.
• Application Load Balancers: Tailored for handling HTTP and HTTPS traffic.

Benefits

• Cost-Efficiency: Pay-as-you-go model reduces expenses related to underutilized resources.
• Performance: Elasticity ensures that sufficient resources are available to meet performance requirements.
• Fault Tolerance: Using multiple EC2 instances and Auto Scaling enhances system reliability.

Code Example: Auto Scaling Setup

Here is the Python code:

import boto3

client = boto3.client('autoscaling')

response = client.create_auto_scaling_group(
    AutoScalingGroupName='string',
    LaunchConfigurationName='string',
    MinSize=1,
    MaxSize=1,
    DesiredCapacity=1
)

The AWS Management Console serves as a graphical user interface for interacting with AWS services. It offers an intuitive way to access and manage a wide range of AWS resources.

Key Features

• User-Friendly Dashboard: Provides an overview of system health, cost management tools, and recent resource activity.

• Service Navigation: Offers categorized service access, from compute and storage to machine learning and analytics.

• Resource Management: Allows for resource provisioning, configuration, and monitoring through a point-and-click interface.

• Task Automation: Enables set-up of automated tasks such as backup schedules and resource scaling.

• Integrated Tools: Incorporates third-party applications and AWS-specific utilities for enhanced functionality.

• Collaboration and Security: Facilitates user and access management, making it easier to work within teams while adhering to best security practices.

Console vs. SDKs vs. CLIs

Compared to the AWS Command Line Interface (CLI) and Software Development Kits (SDKs) for various programming languages:

Key Distinctions

• Ease of Use: The console's graphical nature makes it more approachable for beginners, whereas CLIs and SDKs cater more to developers and advanced users.

• Functionality: The console covers a broad range of AWS services, but might lag behind in supporting the latest offerings compared to the up-to-date coverage provided by SDKs.

• Workflow Flexibility: CLIs are often preferred for scripting and automation, while the console is tailored for manual, point-and-click operations.

Console Role-Based Access

When the AWS Management Console is used in conjunction with the Identity and Access Management (IAM) service, it allows for granular, role-based controls and shared access across teams.

The Storage Classes that are available in the Amazon S3 are the following:

• Amazon S3 Glacier Instant Retrieval storage class
• Amazon S3 Glacier Flexible Retrieval (Formerly S3 Glacier) storage class
• Amazon S3 Glacier Deep Archive (S3 Glacier Deep Archive)
• S3 Outposts storage class
• Amazon S3 Standard-Infrequent Access (S3 Standard-IA)
• Amazon S3 One Zone-Infrequent Access (S3 One Zone-IA)
• Amazon S3 Standard (S3 Standard)
• Amazon S3 Reduced Redundancy Storage
• Amazon S3 Intelligent-Tiering (S3 Intelligent-Tiering)

AWS CloudFormation templates are YAML or JSON formatted text files that are comprised of five essential elements, they are:

• Template parameters
• Output values
• Data tables
• Resources
• File format version

The AWS Shared Responsibility Model establishes clear responsibilities for security and compliance between AWS and the customer. This model varies for different AWS services, but generally follows two core components: "Security of the Cloud" and "Security in the Cloud".

Security of the Cloud

AWS holds the primary responsibility for protecting the infrastructure and physical facilities on which its services are built. This includes:

• Global Infrastructure: AWS maintains secure data centers, with measures such as biometric access control and continuous surveillance.
• Compliance Certifications: AWS obtains third-party security and compliance certifications to ensure its operations meet industry-standards.
• Hardware and Software: AWS manages the security and maintenance of the hardware and software infrastructure that powers its cloud services.

Security in the Cloud

Customers are responsible for securing their data, applications, and services running on AWS. The extent of this responsibility can vary based on the specific AWS service in use, but generally includes:

• Data Encryption: Customers should encrypt their data to protect its confidentiality and integrity during transit and while at rest in AWS services.
• Access Management: Implementing robust Identity and Access Management (IAM) policies to regulate user access to AWS resources.
• Operating System and Networking: For Infrastructure as a Service (IaaS) offerings, customers are responsible for securing their Operating Systems and network configurations, among other tasks.
• Configuration Management: Customers should manage and monitor the configuration of their AWS resources to ensure they align with best security practices.

Here are the steps involved in a CloudFormation solution:

• Create or use an existing CloudFormation template using JSON or YAML format.
• Save the code in an S3 bucket, which serves as a repository for the code.
• Use AWS CloudFormation to call the bucket and create a stack on your template.
• CloudFormation reads the file and understands the services that are called, their order, the relationship between the services, and provisions the services one after the other.

Amazon S3 can be used for instances with root devices backed by local instance storage. That way, developers have access to the same highly scalable, reliable, fast, inexpensive data storage infrastructure that Amazon uses to run its own global network of websites. To execute systems in the Amazon EC2 environment, developers load Amazon Machine Images (AMIs) into Amazon S3 and then move them between Amazon S3 and Amazon EC2.

Amazon EC2 and Amazon S3 are two of the best-known web services that make up AWS.

You can know that you are paying the correct amount for the resources that you are using by employing the following resources:

• Check the Top Services Table It is a dashboard in the cost management console that shows you the top five most used services. This will let you know how much money you are spending on the resources in question.
• Cost Explorer There are cost explorer services available that will help you to view and analyze your usage costs for the last 13 months. You can also get a cost forecast for the upcoming three months.
• AWS Budgets This allows you to plan a budget for the services. Also, it will enable you to check if the current plan meets your budget and the details of how you use the services.
• Cost Allocation Tags This helps identify the resource that costs more in a particular month. It lets you organize your resources and cost allocation tags to keep track of your AWS costs.

Here are some differences between AWS CloudFormation and AWS Elastic Beanstalk:

• AWS CloudFormation helps you provision and describe all of the infrastructure resources that are present in your cloud environment . On the other hand, AWS Elastic Beanstalk provides an environment that makes it easy to deploy and run applications in the cloud.
• AWS CloudFormation supports the infrastructure needs of various types of applications, like legacy applications and existing enterprise applications. On the other hand, AWS Elastic Beanstalk is combined with the developer tools to help you manage the lifecycle of your applications.

The two key differences between the IAM role and IAM user are:

• An IAM role is an IAM entity that defines a set of permissions for making AWS service requests, while an IAM user has permanent long-term credentials and is used to interact with the AWS services directly.
• In the IAM role, trusted entities, like IAM users, applications, or an AWS service, assume roles whereas the IAM user has full access to all the AWS IAM functionalities.