Database – Amazon Relational Database Service (RDS), Create an Amazon RDS, DynamoDB, Create an DynamoDB Table and Amazon Redshift

dkj gbndlvbjn bhvbjkd vbnb inbjn kbnijjgfbnn bdjnb jnkjnbn kcbx nbnjib ijbnnkjbnxb c kjnj ckbkn kjkb kj bmb k kjnk nbijnbkj bm ckjbncj kb vruke fki jkb j uh j fjhb dsv kjjnviihb hbgjngkc kjwnui b bkj bfnbm ,m fhvund gmd nvkj vbuidfb jdfbnlzdkfj v b,mxfvjk nvbjdf nbuzdfhvlnvbdfjkv zlfjkvbinuids bvj ilh dfj ndfj ndzfb ar

1. Amazon RDS (Relational Database Service) UNIT IV Database – Amazon Relational Database Service (RDS), Create an Amazon RDS, DynamoDB , Create an DynamoDB Table and Amazon Redshift

2. What is Amazon RDS (Relational Database Service)? Amazon RDS is a managed relational database service that simplifies the setup, operation, and scaling of databases in the cloud. It automates common administrative tasks such as backups, patching, Migration and hardware provisioning. Amazon RDS supports an array of database engines to store and organize data. A  DB instance  is an isolated database environment in the AWS Cloud. The basic building block of Amazon RDS is the DB instance. 

3. Amazon RDS DB instances- Diagram A DB instance is an isolated database environment in the AWS Cloud. The basic building block of Amazon RDS is the DB instance. Your DB instance can contain one or more user-created databases. The following diagram shows a virtual private cloud (VPC) that contains two Availability Zones, with each AZ containing two DB instance You can access your DB instances by using the same tools and applications that you use with a standalone database instance. You can create and modify a DB instance by using the AWS Command Line Interface (AWS CLI), the Amazon RDS API, or the AWS Management Console.

4. Amazon RDS application architecture: example The following image shows a typical use case of a dynamic website that uses Amazon RDS DB instances for database storage:

5. Components of the Amazon RDS application architecture: example 1) Elastic Load Balancing AWS routes user traffic through Elastic Load Balancing. A load balancer distributes workloads across multiple compute resources, such as virtual servers. In this sample use case, the Elastic Load Balancer forwards client requests to application servers. 2) Application servers Application servers interact with RDS DB instances. An application server in AWS is typically hosted on EC2 instances, which provide scalable computing capacity. The application servers reside in public subnets with different Availability Zones (AZs) within the same Virtual Private Cloud (VPC). 3) RDS DB instances The EC2 application servers interact with RDS DB instances. The DB instances reside in private subnets within different Availability Zones (AZs) within the same Virtual Private Cloud (VPC). Because the subnets are private, no requests from the internet are permitted. The primary DB instance replicates to another DB instance, called a read replica. Both DB instances are in private subnets within the VPC, which means that Internet users can't access them directly.

6. Amazon RDS Instance: Supported Database Engines A DB engine is the specific relational database software that runs on your DB instance.. Amazon RDS supports eight engines: Amazon Aurora PostgreSQL-Compatible Edition. Amazon Aurora MySQL-Compatible Edition. RDS for PostgreSQL. RDS for MySQL. RDS for MariaDB . RDS for SQL Server. RDS for Oracle. RDS for Db2. AWS provides other database services, including the following: Amazon DynamoDB key-value and document database for NoSQL databases. 2. Amazon Neptune for graph databases. 3. AWS Database Migration Service to ease database transfers and transformations.

7. Key Feature of RDS

8. Amazon RDS pricing

9. Practical 9: Creation of DB Instance- MYSQL Engine and Connect Practical 9: Creation of DB Instance- MYSQL Engine and Connect Group Activity1 : Dynamo DB + Query Execution Group Activity 2: Redshift+ Query Execution

10. AWS Cloud Development Kit (AWS CDK): It is an open-source software development framework for defining cloud infrastructure in code and provisioning it through AWS CloudFormation . Two Parts in CDK: 1) AWS CDK Construct Library – A collection of pre-written modular and reusable pieces of code, called constructs , that you can use, modify, and integrate to develop your infrastructure quickly. 2) AWS CDK Command Line Interface (AWS CDK CLI) – A command line tool for interacting with CDK apps. Use the CDK CLI to create, manage, and deploy your AWS CDK projects. The CDK CLI is also referred to as the CDK Toolkit . Infrastructure as code ( IaC ) uses DevOps methodology and versioning with a descriptive model to define and deploy infrastructure, such as networks, virtual machines, load balancers, and connection topologies. Popular IAC: Terraform AWS CloudFormation Azure Resource Manager (ARM) Templates Google Cloud Deployment Manager Ansible Puppet Chef Pulumi

11. AWS CDK core Concepts: 1) Infrastructure as Code ( IaC ): AWS CDK allows you to define cloud infrastructure using code. Supports multiple programming languages ( TypeScript , JavaScript, Python, Java, C#/ .Net , and Go). 2) Constructs- Library for Reusable Code : Reusable cloud components defined in code. Three levels of constructs: L1 (Low-level) : Directly represent AWS CloudFormation resources. L2 (High-level) : Provide higher-level abstractions, simplifying resource configuration. L3 (Patterns) : Predefined architectures for common use cases. 3) Stacks- Logical Unit : A stack represents a collection of AWS resources managed as a single unit. Deployment : AWS CDK synthesizes the stack into a CloudFormation template for deployment. Isolation : Stacks isolate different parts of your infrastructure. Reusability : Stacks can be reused and instantiated with different configurations

12. AWS CDK core Concepts: 4) AWS CloudFormation Integration: CDK convert your code into AWS CloudFormation templates( Json,YAML format). Benefits from AWS CloudFormation's robust deployment processes and extensive resource configuration support. 5) App: The root of the CDK application. Contains one or more stacks. 6) Deployment: Use the CDK CLI to deploy your stacks. The CLI handles the synthesis and deployment process.

13. Steps in AWS CDK The AWS CDK supports TypeScript , JavaScript, Python, Java , C#/ .Net , and Go. You can use any of these supported programming languages to define reusable cloud components known as constructs . You compose these together into stacks and apps. Then, you deploy your CDK applications to AWS CloudFormation to provision or update your resources.

14. Steps in AWS CDK Project The AWS CDK can be written in any supported programming language. You start with a CDK project, which contains a structure of folders and files, including assets. Within the project, you create a CDK application. Within the app, you define a stack, which directly represents a CloudFormation stack. Within the stack, you define your AWS resources and properties using constructs.

15. Benefits of the AWS CDK Infrastructure as Code ( IaC ) Develop, deploy, and manage infrastructure programmatically . Use best practices like code reviews, unit tests, and source control . General-Purpose Programming Languages Define infrastructure using TypeScript , JavaScript, Python, Java, C#/ .Net , and Go. Control programming constructs like parameters, loops, and inheritance. Integrated Development Environment (IDE) Benefits Use your preferred IDE for syntax highlighting and intelligent code completion. AWS CloudFormation Integration Deploy infrastructure predictably and repeatedly with rollback on error. No need to learn a new IaC management service. Reusable Constructs Develop faster with reusable components. Use high-level constructs for quick setup with secure defaults. Create and share custom constructs for unique use cases.

16. Example of CDK: Create a scalable, load-balanced ECS Fargate service running in a VPC with the specified resources.

17. Sample Application Creation Sample Java Program: example of using the AWS CDK Constructs Library to create an Amazon Elastic Container Service (Amazon ECS) service with AWS Fargate launch type. Assignment 3: Create an AWS Fargate service using the AWS CDK

18. CI/CD on AWS CI/CD can be pictured as a pipeline, where new code is submitted on one end, tested over a series of stages (source, build, test, staging, and production), and then published as production-ready code. AWS brings in a complete set of CI/CD developer tools to accelerate software development and release cycles. AWS CodePipeline automates the build, test, and deploy phases of the release process every time there is a code change, based on the defined release model. This enables the rapid and reliable delivery of features and updates.

19. AWS CodePipeline –Components AWS can set up CI/CD pipelines using the following AWS Developer Tools: AWS CodeCommit AWS CodeBuild AWS CodePipeline AWS CodeDeploy Amazon Elastic Container Registry AWS CodeStar CI/CD pipeline creation can be automated using AWS CDK and AWS CloudFormation .

20. AWS CodePipeline –Process for Development Step1 : Network Setup: AWS CDK and AWS CloudFormation initiate creation of network prerequisites. Step2: Infrastructure Deployment: AWS CDK and AWS CloudFormation initiate creation of resource stacks. Step 3: Cloud Network Function (CNF) Deployment: CNF deployed onto EKS clusters using Kubectl and Helm charts. Deploys necessary applications/tools (e.g., Prometheus, Fluentd ). Deployment via Lambda functions or AWS CodeBuild . Step 4: Continuous Updates and Deployment: Iterative steps for container/configuration changes and upgrades. Automated using AWS Services (e.g., AWS CodeCommit , Amazon ECR, GitLab Webhooks ).

21. AWS CodePipeline – Usecases AWS CodePipeline can address a variety of development and operation use cases including: Compiling, building, and testing code with AWS CodeBuild Continuous delivery of container-based applications to the cloud Pre-deployment validation of artifacts (such as descriptors and container images) required for network service or specific cloud-native network functions Functional, integration, and performance tests for containerized network function/virtual network function (CNF/VNF), including baseline and regression testing Reliability and disaster recovery (DR) testing