| Table of Contents |
|---|
...
...
Training Resources
Ed Izzo AWS Tips
Great catching up as always, Jim. Maybe we'll finally meet in person post-vaccination this summer!
...
- Choose Between Java Serverless Options
- Sign Up for AWS Account with Billing
- Create AWS Access Keys
- Install and Configure AWS CLI
- Create AWS Role
- Download the Project from GitHub
- Configure Okta JWT Auth
- Create the Lambda
- Create an AWS API Gateway
- Test Your API Gateway URL
- Generate a JWT Token
- Test the Protected Serverless Function
- Learn More about AWS and Java
Apache OpenWhisk
Cloud Serverless Cost Calculator - AWS, Azure, IBM, GCP
...
https://cloudwars.co/amazon/amazon-addresses-critical-blind-spot-mainframe-deal-tcs/
This hybrid cloud phenomenon—the ability for private-cloud and public-cloud environments to work seamlessly with on-premises systems including mainframes—has become the Holy Grail for not only the businesses deploying it but also for cloud vendors looking to win the hearts, minds and wallets of those businesses.
Over the past few years, AWS has made some impressive strides in addressing the hybrid-cloud reality, particularly as it has continued to expand its offerings under its Outposts family of services aimed at tying into on-premises environments.
But, as I’ve noted before, the very fact that AWS chose the term “Outposts” reveals a lot about Amazon’s perspective: that these are marginal and minimal concessions in the form of stuff to be kept out on the fringes and visited or used only when necessary.
That is perhaps an understandable perspective from a cloud-computing zealot, but it is most certainly not the point of view that businesses around the world are taking as they pursue the hybrid blend that’s optimal for their success.
And into that breach comes the enhanced partnership between AWS and TCS.
While TCS has been a close partner of AWS for many years, the new relationship calls for all of the AWS-focused efforts of TCS to be brought together for the first time under a single entity. That is no small achievement in a huge company like TCS (Tata Consultancy Services), which posted revenue of $22 billion for its last full fiscal year and has 469,000 employees in 46 countries.
TCS said its new business unit will be focused on helping businesses migrate mainframe and other legacy environments to AWS, modernize their applications and data estates and pursue industry-specific innovations.
In an email exchange, I received some additional insights into the partnership from Krishna Mohan, VP and global head of the TCS AWS Business Unit.
“Mainframe modernization mainly includes movement of entire mainframe workloads and associated ecosystems into AWS and broadly aligned to cloud-adoption strategy,” Mohan said via email.
“Once modernized or rehosted, the new cloud-native applications will integrate with various SaaS/PaaS solutions available and the on-premises workloads that fit into the hybrid-cloud model.”
In reply to my questions about the possible size of this mainframe-migration opportunity and related issues, Mohan offered the following insights:
1. Mainframes are still used by:
- 71% of the Fortune 500;
- 96 of the world’s largest 100 banks;
- 9 of the world’s 10 largest insurance companies; and
- 23 of the 25 largest retailers in the US.
2. 70% of CXOs say mainframe migration and modernization is a top priority in the next 3 years, according to a survey of more than 200 CXOs conducted by IDG Research on behalf of TCS/AWS.
3. Mainframe applications are still in wide use, according to the IDG survey, including:
- 69% for core business;
- 67% for internal apps;
- 67% for finance apps;
- 61% customer-facing apps; and
- 60% for AI/ML.
Potential Challenges
Candidate Solutions
...
Case ID 7197414421 - can I use AWS services from Lightsail?
Lightsail provides a base set of resources available 24x7 in different configurations for compute, storage, memory, network access. From a Lightsail account, console do I have access to normal AWS services as an option?
Step-by-step guide for Example
...
create an admin user acct
If you don't already have an access key for your AWS account root user, don't create one unless you absolutely need to. Instead, use your account email address and password to sign in to the AWS Management Console and create an IAM user for yourself that has administrative permissions.
rjm0g$psyn#pz9
create 2 admins - jmason, smason
user key files downloaded
swt1-aws-new_user_credentials-v1.csv
Created user jmason
Attached policy AdministratorAccess to user jmason
Attached policy AmazonAPIGatewayAdministrator to user jmason
Created access key for user jmason
Created login profile for user jmason
welcome email to jm9g
You now have access to the AWS Management Console for the account ending in 1661. ------
Sign-in URL: https://594585551661.signin.aws.amazon.com/console
User name: jmason
Your password will be provided separately by your AWS account administrator.
welcome email smason
You now have access to the AWS Management Console for the account ending in 1661. ------
Sign-in URL: https://594585551661.signin.aws.amazon.com/console
User name: smason
Your password will be provided separately by your AWS account administrator.
Created an org - swt1
| Info |
|---|
...