<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Eliezer Perruci on Medium]]></title>
        <description><![CDATA[Stories by Eliezer Perruci on Medium]]></description>
        <link>https://medium.com/@eliezerperruci?source=rss-0656087ca383------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kNOorgJNVyYX0-2yksNHpw.jpeg</url>
            <title>Stories by Eliezer Perruci on Medium</title>
            <link>https://medium.com/@eliezerperruci?source=rss-0656087ca383------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:04:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eliezerperruci/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Configuring and deploying a SaaS application on AWS EC2 across multiple instances using Ansible and…]]></title>
            <link>https://eliezerperruci.medium.com/configuring-and-deploying-a-saas-application-on-aws-ec2-across-multiple-instances-using-ansible-and-8c84b57fc2f0?source=rss-0656087ca383------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c84b57fc2f0</guid>
            <category><![CDATA[ansible]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[iac]]></category>
            <dc:creator><![CDATA[Eliezer Perruci]]></dc:creator>
            <pubDate>Fri, 26 Sep 2025 01:32:40 GMT</pubDate>
            <atom:updated>2025-09-26T01:32:40.974Z</atom:updated>
            <content:encoded><![CDATA[<h3>Configuring and deploying a SaaS application on AWS EC2 across multiple instances using Ansible and securely storing configuration files on GitHub</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P92V6tmNopQvU4xZDWWvKg.jpeg" /></figure><p>In this project based on a real-world scenario, I used the Ansible configuration management automation to configure and deploy the innovative SaaS application on AWS EC2 instances that will serve multiple locations…</p><p>I organized everything in <strong>GitHub</strong>: a repo with roles/, inventories/, group_vars/, host_vars/, and templates/ (Jinja2). Branch protections, required reviews, secret-scanning, and a CODEOWNERS file kept changes safe. Each EC2 instance carried tags like App=HumanGov, Env=Prod, and Location=FL|CA|…. Ansible’s <strong>AWS dynamic inventory</strong> discovered targets by those tags, so a single playbook could fan out to the right fleet per state without hard-coding IPs. Connectivity used <strong>SSM Session Manager</strong> (no open SSH), with instance profiles granting least-privilege access to <strong>DynamoDB</strong> and <strong>S3</strong>. The playbooks were idempotent and layered: a baseline hardening role (users, packages, firewalls, CloudWatch logs/alarms), a runtime role (Python, systemd service, log rotation), a web role (Nginx reverse proxy, TLS), and an app role that rendered environment-specific config from templates and pulled secrets at runtime from <strong>SSM Parameter Store</strong> (KMS-encrypted).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mVCHR_rLOLrSp0HwVWfHDg.png" /></figure><p>For governance, <strong>GitHub Actions</strong> linted YAML/Ansible and performed a check-mode plan on pull requests. On approved merges, an environment-protected workflow assumed an AWS role via OIDC and triggered the deployment to the selected locations, posting results back to the PR. Rollbacks were simple: revert in GitHub and re-run the workflow — Ansible converged hosts back to the previous known-good state.</p><p><strong>Result:</strong> consistent, secure, repeatable deployments to multiple EC2 groups across states — with zero manual SSH, per-location targeting via tags, centralized secrets, and a GitHub-first workflow that made every release auditable and easy to roll back.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c84b57fc2f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Reusable SaaS Multi-Tenant AWS Infrastructure using Terraform Modules and Securely…]]></title>
            <link>https://eliezerperruci.medium.com/building-a-reusable-saas-multi-tenant-aws-infrastructure-using-terraform-modules-and-securely-bc0f066eabbd?source=rss-0656087ca383------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc0f066eabbd</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[iac]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Eliezer Perruci]]></dc:creator>
            <pubDate>Fri, 12 Sep 2025 19:32:10 GMT</pubDate>
            <atom:updated>2025-09-12T19:32:10.127Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building a Reusable SaaS Multi-Tenant AWS Infrastructure using Terraform Modules and Securely Managing Configurations in GitHub</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z9xnKV5FyT6iIa6HCXbScg.jpeg" /></figure><p>In this project based on a real-world scenario, I designed and deployed a reusable, multi-tenant SaaS infrastructure on AWS using Terraform modules.</p><p>The infrastructure was based on AWS services such as EC2 instances, DynamoDB databases, and S3 buckets. To securely store and collaborate on the Terraform configuration, I used <strong>GitHub</strong> with branch protection rules, required reviews, signed commits, secret scanning, and a CODEOWNERS file to gate changes.</p><p>I structured the code as a “tenant factory.” A root stack orchestrated versioned modules for network (VPC, subnets, security groups, VPC endpoints), compute (EC2 + IAM roles + SSM), and data (one DynamoDB table + one S3 bucket per tenant). Each module accepted a tenant_id, environment, and cost tags so onboarding Florida, California, or any new tenant was just instantiating the same modules with a new ID. Data was siloed: IAM policies enforced per-tenant access using condition keys (e.g., DynamoDB leading keys and S3 path prefixes), and each bucket/table used its own KMS key.</p><p>Terraform state lived in S3 with versioning/SSE-KMS and was lock-protected in DynamoDB. State files were namespaced per tenant to isolate drift and simplify rollbacks. All state traffic stayed private via VPC endpoints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lrD6Gwl3OJj4BMDGLkp_Pg.png" /></figure><p><strong>GitHub Actions</strong> handled governance and automation: on every pull request, workflows ran fmt/validate/plan and posted the plan as an artifact and PR comment; merging to protected branches required green checks and approvals. A separate “apply” workflow was tied to <strong>GitHub Environments</strong> with manual reviewers and environment secrets.</p><p>The result was a repeatable multi-tenant baseline managed in GitHub — new tenants can be provisioned in minutes with isolated data, strong guardrails, and a clean, OIDC-based pipeline to plan and apply changes safely.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc0f066eabbd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementation Of Git Repositories For Application And Infrastructure Code Using AWS Code Commit +…]]></title>
            <link>https://eliezerperruci.medium.com/implementation-of-git-repositories-for-application-and-infrastructure-code-using-aws-code-commit-26a70620799b?source=rss-0656087ca383------2</link>
            <guid isPermaLink="false">https://medium.com/p/26a70620799b</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[iac]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Eliezer Perruci]]></dc:creator>
            <pubDate>Sat, 06 Sep 2025 01:16:07 GMT</pubDate>
            <atom:updated>2025-09-06T01:16:07.535Z</atom:updated>
            <content:encoded><![CDATA[<h3>Implementation Of Git Repositories For Application And Infrastructure Code Using AWS Code Commit + Proof Of Concept (POC) Process Of Commit, Push And Revert Code Changes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4_q0fVHf2x69W2RzJJaF8w.jpeg" /></figure><p>In this project based on a real-world scenario, I implemented Git repositories for application and infrastructure code using AWS CodeCommit, and got hands-on experience with the Proof of Concept (PoC) process of commit, push, and revert code changes.</p><p>My mission was to set up a Git repository using AWS CodeCommit and Git Hub for HumanGov, a hypothetical Software as a Service for government organization.</p><p>I designed a two-repo strategy: <strong>human-gov-application</strong> (Python app plus web assets) and <strong>human-gov-infrastructure</strong> (Terraform, Kubernetes YAML, Ansible, Dockerfiles). I created branch policies (<strong>main</strong>, <strong>develop</strong>, feature/*) and enabled <strong>approval rule templates</strong> requiring peer review before merging to main. Access followed least-privilege with IAM groups for Developers and DevOps, KMS encryption for repos, and optional <strong>VPC endpoints (PrivateLink)</strong> so instances in private subnets could reach CodeCommit without public egress. For the developer workflow, I used the <strong>git-remote-codecommit</strong> helper with AWS CLI SSO credentials, standardized .gitignore, commit message conventions (Conventional Commits), and pre-commit hooks with git-secrets to block accidental key uploads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fUn5OKPNbrLTDBlZ77DHgg.png" /></figure><p>The <strong>application repo</strong> included a minimal Python service, HTML/CSS, unit tests (pytest), a Dockerfile, and Kubernetes manifests for later deployment. The <strong>infrastructure repo</strong> held Terraform modules (networking, EKS/ECR stubs, IAM roles) and Ansible playbooks for day-two configuration. I added CodeCommit <strong>triggers</strong> to <strong>SNS</strong> so pushes/PRs send email notifications, while <strong>CloudTrail</strong> and <strong>CloudWatch</strong> provided an auditable trail of who changed what and when.</p><p>For the PoC, I walked the full cycle:</p><ul><li>git checkout -b feature/banner, commit a UI change, <strong>push</strong> to CodeCommit, open a <strong>Pull Request</strong>, and merge after approval.</li><li>Introduce a safe fault, then <strong>revert</strong> with git revert &lt;sha&gt; on main, demonstrating immediate rollback and automatic notifications.</li><li>Tag a release (v0.1.0) and mirror the repo locally with an additional remote to validate interoperability with GitHub workflows.</li></ul><p>Outcome: clear repo boundaries for app and IaC, secure access and reviews by default, standardized developer ergonomics, and a tested commit→push→review→merge→revert loop — ready to plug into CodeBuild/CodePipeline when the team moves from PoC to CI/CD.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26a70620799b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementation of an E-Commerce System on AWS in an automated way using Terraform and Ansible]]></title>
            <link>https://eliezerperruci.medium.com/implementation-of-an-e-commerce-system-on-aws-in-an-automated-way-using-terraform-and-ansible-23cb5697705a?source=rss-0656087ca383------2</link>
            <guid isPermaLink="false">https://medium.com/p/23cb5697705a</guid>
            <category><![CDATA[ansible]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Eliezer Perruci]]></dc:creator>
            <pubDate>Sat, 30 Aug 2025 02:02:13 GMT</pubDate>
            <atom:updated>2025-08-30T02:02:13.574Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c42Po6Sq_9iP_uAJ_-l6Xw.png" /></figure><p>In another project based in a real-world scenario, I worked as Cloud Engineer using DevOps, where I created and implemented an e-Commerce MVP (Minimum Viable Product) on AWS in less than 2 hours and in an automated way using Terraform and Ansible (Infrastructure as Code — IaC).</p><p>I provisioned the infrastructure in an automated way using Terraform and Ansible to automate the configuration management process, software installation and package management of the EC2 instance. I also used Magento, PHP, MySQL, and Redis to complete this project.</p><p>I started with a tiny, fast-to-spin VPC: one public subnet, an Internet Gateway, and a security group exposing only 80/443 (and 22 locked to my jump host). Terraform created the IAM instance profile (SSM + CloudWatch), an EC2 <strong>t3.medium</strong> with a <strong>gp3</strong> EBS volume, and tagged everything for dynamic Ansible inventory. User data performed a minimal bootstrap, then I ran terraform apply and immediately targeted the new instance with ansible-playbook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*maPof0YhnzOd4K1M8kIS2Q.png" /></figure><p>Ansible handled the full app stack idempotently. Roles installed <strong>Nginx + PHP-FPM 8.x</strong> with all Magento extensions (bcmath, intl, mbstring, opcache, sodium, soap, xsl, zip), tuned PHP/opcache, and configured <strong>MySQL 8</strong> (secure install, magento DB/user, sane InnoDB defaults). A separate role set up <strong>Redis</strong> for session and page cache. The <strong>magento</strong> role installed Composer, fetched Magento Open Source, set correct filesystem ownership/ACLs, and ran bin/magento setup:install with base URL, admin user, Redis endpoints, and production mode. Cron jobs (bin/magento cron:run) and log rotation were added, and Let’s Encrypt issued TLS so the store launched at <a href="https://mvp.tcb.store./">https://mvp.tcb.store.</a></p><p>For operations, I pushed system and Nginx/PHP logs to <strong>CloudWatch</strong>, set CPU/status alarms, and stored secrets in <strong>SSM Parameter Store</strong> (Ansible pulled them at runtime; DB password never lived in plaintext). From zero to checkout page took ~90 minutes including smoke tests and a quick demo catalog.</p><p>Finally, I outlined the scale-up path: place <strong>ALB</strong> in front, split <strong>RDS MySQL</strong> and <strong>ElastiCache Redis</strong>, move media to <strong>S3 + CloudFront</strong>, add <strong>WAF</strong>, and extend Terraform modules to Multi-AZ Auto Scaling. The MVP proved the value fast while leaving a clean runway to production-grade architecture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23cb5697705a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Executive Presentation of Infrastructure costs for an SAP Migration project from On-Premises to AWS]]></title>
            <link>https://eliezerperruci.medium.com/executive-presentation-of-infrastructure-costs-for-an-sap-migration-project-from-on-premises-to-aws-15b887dcf070?source=rss-0656087ca383------2</link>
            <guid isPermaLink="false">https://medium.com/p/15b887dcf070</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Eliezer Perruci]]></dc:creator>
            <pubDate>Sat, 30 Aug 2025 00:09:57 GMT</pubDate>
            <atom:updated>2025-08-30T00:09:57.210Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zMSfjs3oRtaM-isZHBrPzw.png" /></figure><p>In this project based on a real-world scenario, I acted as a Cloud Architect and created an executive presentation of infrastructure costs for a SAP migration project from On-Premises to AWS.</p><p>SAP workloads were running in a corporate DataCenter with the environment divided into Production, Quality Assurance — QA and Development/Test layers.</p><p>My mission was to estimate the costs of migration to AWS, considering that this infrastructure will be running on AWS for at least the next 3 years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YAWiEB6UsU4Npr2a7D_c8w.png" /></figure><p>To calculate costs, I built a bottom-up model using the AWS Pricing Calculator and an Excel workbook that mirrored the three environments. First, I inventoried current usage (vCPU/RAM, disks, IOPS, network egress, SAPS where available) and right-sized to AWS instances rather than lifting raw hardware numbers. I mapped application servers to general-purpose families (m6i/m7i) and database nodes to memory-optimized families (r6i/x2idn as options), modeling two database paths: <strong>RDS for Oracle (License Included)</strong> vs <strong>EC2 BYOL</strong>. For each, I priced Multi-AZ for Production and Single-AZ for QA/Dev, adding 30% headroom on peak CPU/IO to avoid under-provisioning. Storage was split into <strong>EBS gp3</strong> (with explicit IOPS/Throughput settings), <strong>EFS</strong> for shared/NFS needs, and <strong>S3</strong> for backups and logs with lifecycle policies (Standard → Standard-IA → Glacier Instant/Deep Archive). Networking estimates included inter-AZ data, NAT Gateway hourly + data processing, PrivateLink/VPC endpoints to reduce NAT egress, and modest internet egress based on monthly usage patterns. I added observability and security line items — CloudWatch metrics/logs, SSM, KMS, GuardDuty, AWS Backup — and a Business Support plan. Pricing strategy assumed steady state covered by a <strong>3-year Compute Savings Plan (70–80% coverage)</strong> with the remainder On-Demand for flexibility; QA/Dev factored <strong>instance scheduling</strong> (off nights/weekends) to reflect real usage. I produced three scenarios: <strong>Baseline (all On-Demand)</strong>, <strong>Target (Savings Plans + storage tuning + scheduler)</strong>, and <strong>Optimized (higher coverage, heavier S3 lifecycle, more endpoints/less NAT)</strong>, each with monthly run-rate and 3-year TCO, growth at 10%/year, and a 10% contingency. The final executive deck summarized assumptions, cost by service (compute, storage, network, DB, security/ops, support), one-time migration costs (DataSync/Snowball/Direct Connect, cutover testing), and a simple cash-flow and break-even view versus on-prem operations — giving leadership clear options and the levers to pull for savings without risking SAP performance or availability.</p><p>As a result, leadership received a clear, defensible cost model with options, trade-offs, and a recommended target scenario. The analysis balanced performance and availability with predictable spend, outlined the levers for further savings, and quantified 3-year TCO. With this groundwork in place, the next steps are a short pilot to validate SAP performance on the selected instance families, followed by a phased migration plan aligned to change windows and business risk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15b887dcf070" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementation of a set of EC2 instances using Terraform and AWS Systems Manager configuration with…]]></title>
            <link>https://eliezerperruci.medium.com/implementation-of-a-set-of-ec2-instances-using-terraform-and-aws-systems-manager-configuration-with-85e01cd8e936?source=rss-0656087ca383------2</link>
            <guid isPermaLink="false">https://medium.com/p/85e01cd8e936</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Eliezer Perruci]]></dc:creator>
            <pubDate>Fri, 29 Aug 2025 02:25:20 GMT</pubDate>
            <atom:updated>2025-08-29T02:25:20.559Z</atom:updated>
            <content:encoded><![CDATA[<h3>Implementation of a set of EC2 instances using Terraform and AWS Systems Manager configuration with Amazon Simple Notification Service for automated installation of security agent</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vKdof7cu7jfz9EzF6PRNpw.png" /></figure><p>In this project based on a real-world scenario, I acted as DevSecOps Engineer, and I deployed a set of EC2 instances and infrastructure in an automated way using Terraform (infrastructure as code — IaC). Also, it was necessary to install a specific security agent on all these instances in an automated way.</p><p>Once I provisioned the infrastructure, AWS System Manager and its component Command Run were used to install the security agents in an automated way. I used the Amazon Simple Notification Service — SNS to send an email informing the whole process status.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l5nIFDSszczl4WNhBGpnYA.png" /></figure><p>To guarantee secure, repeatable operations, I codified the VPC, subnets, security groups, and instance profiles in Terraform with least-privilege IAM roles and consistent tagging. After the EC2 fleet came online, AWS Systems Manager targeted instances by tag and executed an SSM document that downloaded the agent, validated the service status, and returned logs. For private subnets, I used VPC endpoints for SSM/EC2Messages so no public internet was required. SNS sent success/failure emails with instance details, while CloudWatch retained command output for audit. The result was a push-button, auditable rollout that can be re-run safely across environments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85e01cd8e936" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementation of a Scalable Web Application using the services of AWS Elastic Beanstalk, DynamoDB…]]></title>
            <link>https://eliezerperruci.medium.com/implementation-of-a-scalable-web-application-using-the-services-of-aws-elastic-beanstalk-dynamodb-f583c5878da9?source=rss-0656087ca383------2</link>
            <guid isPermaLink="false">https://medium.com/p/f583c5878da9</guid>
            <category><![CDATA[high-availability]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[load-balancing]]></category>
            <dc:creator><![CDATA[Eliezer Perruci]]></dc:creator>
            <pubDate>Wed, 27 Aug 2025 03:29:14 GMT</pubDate>
            <atom:updated>2025-08-27T03:29:14.834Z</atom:updated>
            <content:encoded><![CDATA[<h3>Implementation of a Scalable Web Application using the services of AWS Elastic Beanstalk, DynamoDB, CloudFront and Edge Location</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vyyUmMJxKPSGow2Ns1FIsw.png" /></figure><p>In this project based on a real-world scenario, I was responsible for implementing an application that needs to support the high demand of a large number of users accessing it simultaneously.</p><p>This application has been used in a large conference that had more than 10,000 people, in-person and online, with participants from all over the world.This event was broadcast online and in person and 10 vouchers were drawn for 3 Cloud certifications. At that moment, more than 10,000 people in the audience registered their e-mails to guarantee their participation in the raffle.</p><p>We used in AWS, Elastic Beanstalk services to deploy the web application, DynamoDB to store emails, CloudFront to cache static and dynamic files in an Edge Location close to the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fh-2rrUNSN2eMAFC2HaBsQ.png" /></figure><p>To guarantee performance and resilience at peak time, I added Amazon Route 53 to route global traffic, used Elastic Beanstalk with an ELB and Auto Scaling across multiple Availability Zones, and configured CloudFront to keep content close to users. Registrations were written to DynamoDB with on-demand capacity to absorb sudden spikes. With Amazon CloudWatch tracking latency, errors, and throughput, we pre-warmed capacity and delivered a smooth, low-latency experience during the live raffle.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f583c5878da9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migration of a Workload running in a Corporate Data Center to AWS using the Amazon EC2 and RDS…]]></title>
            <link>https://eliezerperruci.medium.com/migration-of-a-workload-running-in-a-corporate-data-center-to-aws-using-the-amazon-ec2-and-rds-548a73919b69?source=rss-0656087ca383------2</link>
            <guid isPermaLink="false">https://medium.com/p/548a73919b69</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <dc:creator><![CDATA[Eliezer Perruci]]></dc:creator>
            <pubDate>Mon, 25 Aug 2025 01:04:36 GMT</pubDate>
            <atom:updated>2025-08-25T01:04:36.533Z</atom:updated>
            <content:encoded><![CDATA[<h3>Migration of a Workload running in a Corporate Data Center to AWS using the Amazon EC2 and RDS service</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CA4OHj0z-dmEAN76Hozebg.png" /></figure><p>In this project, I was the Cloud Specialist responsible for moving a business-critical workload from a corporate data center into AWS. The challenge was to rehost both the application and its database without redesigning them, ensuring a smooth transition with minimal downtime.</p><p>I approached the migration in four stages: <strong>planning</strong>, where I sized resources and defined prerequisites; <strong>execution</strong>, where I provisioned AWS services using best practices; <strong>go-live</strong>, which included a dry-run test followed by the final cutover; and <strong>post-migration</strong>, where I validated stability and secured user access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A-boeprCGJdNjE0XeQjXJw.png" /><figcaption>Solution Architecture</figcaption></figure><p>The new architecture placed the application on an <strong>Amazon EC2 instance</strong> in a public subnet, connected through an <strong>Internet Gateway</strong>, while the database moved to a managed <strong>Amazon RDS</strong> instance inside a private subnet. This design ensured the application remained accessible to users while the database stayed protected and isolated from the public internet.</p><p>By the end of the migration, the workload was running reliably in AWS, with improved performance, stronger security, and a foundation ready for future scaling and high availability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=548a73919b69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automated user migration and management of AWS Identity and Access Management (IAM) resources]]></title>
            <link>https://eliezerperruci.medium.com/automated-user-migration-and-management-of-aws-identity-and-access-management-iam-resources-9700b725480f?source=rss-0656087ca383------2</link>
            <guid isPermaLink="false">https://medium.com/p/9700b725480f</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <category><![CDATA[multi-cloud]]></category>
            <category><![CDATA[aws-iam]]></category>
            <dc:creator><![CDATA[Eliezer Perruci]]></dc:creator>
            <pubDate>Wed, 20 Aug 2025 01:18:26 GMT</pubDate>
            <atom:updated>2025-08-20T01:18:26.504Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jdK6qaygPGSPH-ajQu82ow.png" /></figure><p>In this project based on a real-world scenario, I acted as Cloud Specialist with the mission to migrate users in an automated way and manage AWS IAM (Identity and Access Management) resources.</p><p>There were 100 users that needed to be migrated and have MFA (Multi-factor authentication) enabled on their accounts, as this is a security best practice.</p><p>To avoid repetitive and manual tasks in the AWS console, I needed to think about automating the processes.</p><p>Using GitBash with AWS CLI and Shell Script, I developed an automated workflow to:</p><ul><li><strong>Create IAM users</strong> in bulk and assign them to their respective groups.</li><li><strong>Apply a custom IAM policy</strong> that ensured each user had the correct level of access to resources.</li><li><strong>Enable and enforce MFA</strong> across all accounts, improving the security posture.</li><li><strong>Force password reset on first login</strong> to comply with best practices for account initialization.</li><li><strong>Strengthen the AWS account password policy</strong>, including rules for complexity, expiration, and reuse prevention.</li></ul><p>This approach drastically reduced manual intervention, ensured consistency across all user accounts, and minimized the chance of configuration errors. By leveraging automation, I was able to migrate more than 100 users seamlessly, enforce security standards from day one, and leave the environment with a repeatable process that can be applied in future migrations or onboarding activities. See the project’s architecture below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AE_ZAX_PBZlbp9eByk9L8g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9700b725480f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>