SAP on AWS · Automation & DevOps for SAP on AWS

When configuring EC2 instance metadata access for an SAP host, why should you enforce IMDSv2 and not leave IMDSv1 enabled, and what concretely changes in how a request is made?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Automation & DevOps for SAP on AWS

With CloudFormation managing your SAP infrastructure, why must you change infrastructure by updating and re-deploying the template rather than editing resources directly in the console?

You want ABAP code to call AWS services (S3, Lambda) from inside an SAP application. Which SDK do you use, and where is it configured — not the AWS console?

In a CloudFormation template you want extra resources created only when the environment is production. Which section controls that, and which section is the wrong tool for it?

Your Lambda needs PyRFC/NWRFCSDK to connect to SAP over RFC, which pushes it past the Lambda package size limit. Which packaging method do you choose, and what limit forces it?

For an SAP automation task that runs sporadically (e.g. only when an S3 event fires), why does Lambda's billing model make it cheaper than a standing server, and what does it actually bill for?

In an AWS CI/CD pipeline for SAP automation artifacts, which single service does the orchestration, and what is the trap in assuming it also builds and deploys?

Start learning today

Free to start — download the app or use it in your browser.