AWS prescriptive-guidance low security documentation change
Summary
Updated navigation link, fixed Moto documentation URL to HTTPS, removed trailing slash from LocalStack URL, corrected apostrophe usage, and reformatted section reference text.
Security assessment
The change from HTTP to HTTPS for the Moto documentation link addresses a security issue by ensuring encrypted connections to prevent man-in-the-middle attacks during documentation access. Other changes are non-security formatting/navigation updates.
Diff
diff --git a/prescriptive-guidance/latest/hexagonal-architectures/improve-dev-cycle.md b/prescriptive-guidance/latest/hexagonal-architectures/improve-dev-cycle.md index 8fa9cc77b..8f96491c0 100644 --- a//prescriptive-guidance/latest/hexagonal-architectures/improve-dev-cycle.md +++ b//prescriptive-guidance/latest/hexagonal-architectures/improve-dev-cycle.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Building hexagonal architectures on AWS](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Building hexagonal architectures on AWS](introduction.html) @@ -15 +15 @@ Developing software for the cloud introduces new challenges for software enginee -Testing directly in the cloud is the only way to make sure that your architectural components, such as gateways in Amazon API Gateway, AWS Lambda functions, Amazon DynamoDB tables, and AWS Identity and Access Management (IAM) permissions, are configured correctly. It might also be the only reliable way to test component integrations. Although some AWS services (such as [DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.html)) can be deployed locally, most of them cannot be replicated in a local setup. At the same time, third-party tools such as [Moto](http://docs.getmoto.org/en/latest/) and [LocalStack](https://localstack.cloud/) that mock AWS services for testing purposes might not reflect real service API contracts accurately, or the number of features might be limited. +Testing directly in the cloud is the only way to make sure that your architectural components, such as gateways in Amazon API Gateway, AWS Lambda functions, Amazon DynamoDB tables, and AWS Identity and Access Management (IAM) permissions, are configured correctly. It might also be the only reliable way to test component integrations. Although some AWS services (such as [DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.html)) can be deployed locally, most of them cannot be replicated in a local setup. At the same time, third-party tools such as [Moto](https://docs.getmoto.org/en/latest/) and [LocalStack](https://localstack.cloud) that mock AWS services for testing purposes might not reflect real service API contracts accurately, or the number of features might be limited. @@ -21 +21 @@ However, the most complex part of the enterprise software is in the business log -A hexagonal architecture helps developers focus on the domain instead of infrastructure technicalities. This approach uses local tests (the unit testing tools in your chosen development framework) to cover domain logic requirements. You won’t have to spend time solving technical integration problems or deploy your software to the cloud to test the business logic. You can run unit tests locally and reduce the feedback loop from minutes to seconds. If a deployment takes 5 minutes but unit tests complete in 5 seconds, that’s a significant reduction in the time it takes to detect mistakes. The [Testing business logic first](./improve-software-quality.html#logic) section later in this guide covers this approach in more detail. +A hexagonal architecture helps developers focus on the domain instead of infrastructure technicalities. This approach uses local tests (the unit testing tools in your chosen development framework) to cover domain logic requirements. You won't have to spend time solving technical integration problems or deploy your software to the cloud to test the business logic. You can run unit tests locally and reduce the feedback loop from minutes to seconds. If a deployment takes 5 minutes but unit tests complete in 5 seconds, that's a significant reduction in the time it takes to detect mistakes. The [Testing business logic](./improve-software-quality.html#logic) _first_ section later in this guide covers this approach in more detail.