AWS panorama documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in application deployment documentation
Security assessment
Consistency update for service naming. No changes to security permissions or role configuration in the deployment process.
Diff
diff --git a/panorama/latest/dev/gettingstarted-sample.md b/panorama/latest/dev/gettingstarted-sample.md index a792f4c11..c2ae20377 100644 --- a//panorama/latest/dev/gettingstarted-sample.md +++ b//panorama/latest/dev/gettingstarted-sample.md @@ -417 +417 @@ The sample application uses the SDK for Python to upload metrics to Amazon Cloud -It gets permission from a runtime role that you assign during deployment. The role is defined in the `aws-panorama-sample.yml` AWS CloudFormation template. +It gets permission from a runtime role that you assign during deployment. The role is defined in the `aws-panorama-sample.yml` CloudFormation template. @@ -457 +457 @@ The sample application installs the SDK for Python and other dependencies with p -To use the AWS SDK in your application code, first modify the template to add permissions for all API actions that the application uses. Update the AWS CloudFormation stack by running the `1-create-role.sh` each time you make a change. Then, deploy changes to your application code. +To use the AWS SDK in your application code, first modify the template to add permissions for all API actions that the application uses. Update the CloudFormation stack by running the `1-create-role.sh` each time you make a change. Then, deploy changes to your application code.