[docs] doc update for sdlf-cicd

Author: cnfait

README.md

@@ -66,19 +66,19 @@ The [SDLF workshop](https://sdlf.workshop.aws/) walks you through the deployment
 
 1. Get the latest stable release of SDLF, unarchive it and cd to the new folder:
 ```
-curl -L -O https://github.com/awslabs/aws-serverless-data-lake-framework/archive/refs/tags/2.8.0.tar.gz
-tar xzf 2.8.0.tar.gz
-cd ./aws-serverless-data-lake-framework-2.8.0/
+curl -L -O https://github.com/awslabs/aws-serverless-data-lake-framework/archive/refs/tags/2.9.0.tar.gz
+tar xzf 2.9.0.tar.gz
+cd ./aws-serverless-data-lake-framework-2.9.0/
 ```
 
 2. Deploy the CodeBuild projects for bootstrapping the rest of the infrastructure:
 ```
 cd sdlf-cicd/
-./deploy-cicd.sh -p aws_profile_name datalake
 ./deploy-role.sh -p aws_profile_name datalake
+./deploy-cicd.sh -p aws_profile_name datalake
 ```
 
-`./deploy-cicd.sh --help` and `./deploy-role.sh --help` give more details about available options.
+`./deploy-role.sh --help` and `./deploy-cicd.sh --help` give more details about available options.
 
 3. Start the `sdlf-cicd-datalake` project and wait for it to complete. It creates an end-to-end data lake infrastructure, including data processing and consumption services.
 

docs/constructs/cicd.md

@@ -3,46 +3,60 @@
 !!! note
     `sdlf-cicd` is defined in the [sdlf-cicd](https://github.com/awslabs/aws-serverless-data-lake-framework/tree/main/sdlf-cicd) folder of the [SDLF repository](https://github.com/awslabs/aws-serverless-data-lake-framework).
 
-## Simplified CICD with SDLF > 2.8.0
+## Simplified CICD with SDLF ≥ 2.10.0
 
-**SDLF > 2.8.0** has a simplified CICD setup that can be used with any [source provider](https://docs.aws.amazon.com/codebuild/latest/userguide/access-tokens.html) supported by AWS CodeBuild. SDLF creates two CodeBuild projects able to deploy SDLF constructs (a third is created during the deployment process, but the user is never expected to interact directly with it), leaving the configuration of the source step to the user:
+!!! note
+    Also check the [SDLF public workshop](https://catalog.us-east-1.prod.workshops.aws/workshops/501cb14c-91b3-455c-a2a9-d0a21ce68114/en-US/10-demo).
+
+**SDLF ≥ 2.10.0** has a simplified CICD setup that can be used with any [source provider](https://docs.aws.amazon.com/codebuild/latest/userguide/access-tokens.html) supported by AWS CodeBuild. SDLF creates two CodeBuild projects able to deploy SDLF constructs, leaving the configuration of the source step to the user:
 
-* `sdlf-cicd-bootstrap`, publishing SDLF constructs in the private CloudFormation registry,
-* `sdlf-cicd-{name provided by the user}`, deploying the actual infrastructure,
-* and the third appearing during deployment, that should not be modified: `codeseeder-sdlf`.
+* `sdlf-cicd-bootstrap`, uploading SDLF constructs on S3 ready to be used by the CloudFormation service
+  * they can also be published as CloudFormation modules on the private CloudFormation registry (`DEPLOYMENT_TYPE` set to `cfn-module`)
+* `sdlf-cicd-{name provided by the user}`, deploying the actual infrastructure.
 
-These CodeBuild projects are required in every account SDLF is used, and can be deployed with the `./deploy-cicd.sh` script in the `sdlf-cicd` module:
+They can be deployed with the `./deploy-cicd.sh` script in the `sdlf-cicd` module:
 
 ```
 ./deploy-cicd.sh --help # provides details on the available options
 
-./deploy-cicd.sh -p aws_profile sdlf-main
+# `main` can be changed to a more sensible name
+./deploy-cicd.sh -p aws_profile main
+```
+
+Replace `aws_profile` with the name of the AWS profile giving access to the account SDLF CICD infrastructure will be deployed in. `main` is a user-provided name - feel free to use a different one, within constraints.
+
+These CodeBuild projects requires an IAM role in the AWS account data infrastructure will be deployed (even if the account is the same the CodeBuild projects are in). This role can be deployed with the `./deploy-role.sh` script in the `sdlf-cicd` module:
+
+```
+./deploy-role.sh --help # provides details on the available options
+
+# the name must match the name used with ./deploy-cicd.sh, in this case `main`
+./deploy-role.sh -p aws_profile main
 ```
 
-Replace `aws_profile` with the name of the AWS profile giving access to the account SDLF will be used in. `sdlf-main` is a user-provided name - feel free to use a different one, within constraints.
+Replace `aws_profile` with the name of the AWS profile giving access to the account SDLF data infrastructure will be deployed in. `main` is a user-provided name - it **must match** the name used with ./deploy-cicd.sh, in this case `main`.
 
 Once the CodeBuild projects are created, the user can edit them manually to configure the source provider. Please refer to the [AWS CodeBuild documentation](https://docs.aws.amazon.com/codebuild/latest/userguide/access-tokens.html) for details on how to do this. `sdlf-cicd-bootstrap` should have a git repository containing a copy of the entire SDLF repository as source. `sdlf-cicd-{name provided by the user}` should use an empty git repository as source - this is the repository end users are going to work in, pushing CloudFormation templates referencing SDLF constructs, as seen in the [public workshop](https://catalog.us-east-1.prod.workshops.aws/workshops/501cb14c-91b3-455c-a2a9-d0a21ce68114/en-US/10-demo/200-foundations).
 
-There is no SDLF-specific DevOps account in this setup.
 
-`./deploy-cicd.sh` can be run multiple times in the same account if required, with different names. This can be useful if teams with different scopes are responsible for the data architectures. For example:
+`./deploy-cicd.sh` can be run multiple times in the same account if required, with different names. This can be useful if teams with different scopes are responsible for the data architecture in an account. For example:
 
 ```
-./deploy-cicd.sh -p aws_profile sdlf-main
-./deploy-cicd.sh -p aws_profile sdlf-engineering
+./deploy-cicd.sh -p aws_profile platform
+./deploy-cicd.sh -p aws_profile engineers
 ```
 
 This would create the following:
 
 * `sdlf-cicd-bootstrap`
   * this is created only once, no matter how many times `./deploy-cicd.sh` is used in a given account.
-* `sdlf-cicd-sdlf-main`
+* `sdlf-cicd-platform`
   * this CodeBuild project could be linked to a git repository owned by a data platform team, creating centralized storage layers with `sdlf-foundations`.
-* `sdlf-cicd-sdlf-engineering`
+* `sdlf-cicd-engineers`
   * this CodeBuild project could be linked to a git repository owned by a data engineers team, creating technical catalogs and data processing pipelines with `sdlf-dataset` and the various `sdlf-stage-*`.
 
 
-## Infrastructure
+## Infrastructure - SDLF ≤ 2.10.0
 
 !!! note
     This section and the rest of the page does not apply to the setup described above.