* fix: Add AWS_REGION fallback for gateway notebooks
Update AWS_DEFAULT_REGION environment variable setting in AgentCore
gateway notebooks to fall back to AWS_REGION when available,
defaulting to us-east-1 if neither is set.
This change ensures compatibility with different AWS environment
configurations and follows SageMaker best practices.
Files modified:
- 01-tutorials/02-AgentCore-gateway/01-transform-lambda-into-mcp-tools/01-gateway-target-lambda.ipynb
- 01-tutorials/02-AgentCore-gateway/02-transform-apis-into-mcp-tools/02-transform-openapi-into-mcp-tools/01-openapis-into-mcp-api-key.ipynb
- 01-tutorials/02-AgentCore-gateway/02-transform-apis-into-mcp-tools/02-transform-openapi-into-mcp-tools/02-openapis-into-mcp-oauth-enterpris-apis.ipynb
- 01-tutorials/02-AgentCore-gateway/02-transform-apis-into-mcp-tools/03-transform-smithyapis-into-mcp-tools/01-s3-smithy-into-mcp-iam.ipynb
Changed: os.environ['AWS_DEFAULT_REGION'] = 'us-east-1'
To: os.environ['AWS_DEFAULT_REGION'] = os.environ.get('AWS_REGION', 'us-east-1')
* adding requirement files for sm run
* adding requirement files for sm run
* renaming gateway folders
* Remove cell execution output
* renaming gateway folders
* changing pip install for gateway search sample
* remove cell outputs
---------
Co-authored-by: Maira Ladeira Tanke <mttanke@amazon.com>
