AWS Migration Steps

5 Phase Approach

1. Migration Preparation and business planning - Stand alone little planning. In most cases inter-connectivity requires very detail planning and prep for technical and business side of operation

right obj determines and type of benefit you see.

it starts with foundation experience and developing preliminary business case for migration

Write done:

objective to meet

age and architecture of existing applications

Application constraints

output is : Types of benefit you see and begins



2. Portfolio discovery and planning

take deeper look at IT portfolio

find dependencies

what migration works for each application

focus on app discovery

building use case for each application

etc AWS application discover service  can assist.

3/4. Designing, migration and validating your applications

focus is from portfolio level to application level for designing. migrating  and validating

6 R's

you can take help from

partners
AWS server migration service
AWS database migration service
CloudEndure Migration

5. Operate - On going operation of our application in cloud

this the place where we look for how old system migrated to cloud could be turned off.

these systems were migrated to cloud due to their dependencies

ongoing phase

take information and lessons learned form migration and looking for continue improvement





-----------


Well Architect ed Tool by AWS framework

To

learn best practices
measure your architecture against best practices
Improvement - area to improve

5 pillar of well arch framework

operational excellence

Security

reliability

performance efficiency

Cost Optimizations

What is Workload

collection of AWS resources and code that delivers business value

subset of resources in one or more accounts

e.g eCommerce site, mobile app back end , corp HR system




Comments

Post a Comment

Popular posts from this blog

Qlik Sense Important Links

Qlik Sense learning https://learning.qlik.com/ https://www.qlik.com/us/services/training/self-paced-learning Qlik sense pricing   https://www.capterra.com/p/145530/QlikSense/#pricing https://www.qlik.com/us/pricing/qlik-sense-client-managed Qlik Sense Server Installation Document preview of Qlik Sense Server Installation Step By Step Guide.pdf https://community.qlik.com/t5/Documents/Qlik-Sense-Server-Installation-Step-By-Step-Guide/ta-p/1480562 https://community.qlik.com/t5/New-to-Qlik-Sense/how-to-download-Qlik-Sense-server/td-p/869140 Support Portal https://support.qlik.com/QS_Home_Page Qlik FIPS Support FIPS mode is not supported out of the box for Qlik Sense, QlikView, and Qlik NPrinting. Workarounds exist for NPrinting and Sense.  For general information about FIPS and Microsoft's statement around it, see  Microsoft's Security Guidance blog. https://community.qlik.com/t5/Knowledge-Base/Qlik-Software-and-FIPS-mode/ta-p/1717239 https://docs.microsoft.com/en-US/windows/...
Read more

Cloud Architecture Notes

Image
The architectural priorities and needs of every app are different, but the four pillars of architecture are an excellent guidepost you can use to make sure that you have given enough attention to every aspect of your application: Security : Safeguarding access and data integrity and meeting regulatory requirements Performance and scalability : Efficiently meeting demand in every scenario Availability and recoverability : Minimizing downtime and avoiding permanent data loss Efficiency and operations : Maximizing maintainability and ensuring requirements are met with monitoring A layered approach to security Defense in depth is a strategy that employs a series of mechanisms to slow the advance of an attack aimed at acquiring unauthorized access to information The common principles used to define a security posture are confidentiality, integrity, and availability, known collectively as CIA. Confidentiality - Principle of least privilege. Restricts access to informa...
Read more

AWS Rout53 NS records do not match with whois dns records OR Your site NOT working with registered domain name? Check this...

  Log in to your AWS web console Select Route53 service Select Hosted Zones in the left pane Select domain name (but do not click on the domain name, just select the radio button) Notice the 4 name servers in the right pane. Next, go to domain registrar site (in your case stay in Route53), log in and configure name servers for your domain. In Route53: select 'Registered domains' in the left pane, click on your domain name, verify that in the upper right you have name servers from step 5, if they don't exactly match, click 'Add/Edit Name servers' and enter name servers from step 5) After this you will receive email on your registered email id with AWS. Once the sync os done you will get notified. After notification you can try your ULR <some-name>.com or www.<some-name>.com "A" records created during route 53
Read more