Allows to create a new Service Account into an organization in Confluent Cloud via API.
See the docs for properties
You need
- An account on Confluent Cloud Platform
- Have a Confluent Cloud API Key
- AWS Account, and for the following installation steps, aws cli
# Optionally create an API key via the CLI
confluent api-key create --resource cloud -o json
export API_KEY=<API KEY RETURNED>
export API_SECRET=<API SECRET RETURNED>
aws cloudformation deploy --stack-name confluent-cloud-api-credentials --template confluent-secrets.template \
--parameter-overrides ConfluentApiKey=${API_KEY} ConfluentSecretKey=${API_SECRET}export SECRET_ARN=`aws cloudformation describe-stack-resources --stack-name confluent-cloud-api-credentials --logical-resource-id ConfluentSecret | jq -r .StackResources[0].PhysicalResourceId`Using the activate.template we create IAM roles and enable the resource in the account, all at once.
aws cloudformation deploy --stack cfn-resource--confluentcloud-iam-serviceaccount --template activate.template \
--capabilities CAPABILITY_IAMThis option offers the "extra security" to have a different IAM Execution role for that resource than others.
Most recommended if you consider enabling multiple ConfluentCloud:: resources published
We are going to use cfn-resources-iam-roles.template template to create the Execution and LoggingRole first, then use these in the activate.template as parameters.
aws cloudformation deploy --stack-name iam--cfn--confluentcloud-resources --template cfn-resources-iam-roles.template \
--capabilities CAPABILITY_IAMExport the IAM Roles to env vars
EXEC_ROLE_ARN=`aws cloudformation describe-stacks --stack-name iam--cfn--confluentcloud-resources | jq -r '.Stacks[0].Outputs[] | select(.OutputKey=="ExecutionRoleArn")' | jq -r .OutputValue`
LOGGING_ROLE_ARN=`aws cloudformation describe-stacks --stack-name iam--cfn--confluentcloud-resources | jq -r '.Stacks[0].Outputs[] | select(.OutputKey=="CloudWatchRoleArn")' | jq -r .OutputValue`Now, we activate the resource using these IAM Roles
aws cloudformation deploy --stack cfn-resource--confluentcloud-iam-serviceaccount --template activate.template \
--capabilities CAPABILITY_IAM \
--parameter-overrides ExecutionRoleArn=${EXEC_ROLE_ARN} LoggingRoleArn=${LOGGING_ROLE_ARN}aws cloudformation deploy --stack-name my-first-service-account --template resource-test.template \
--parameter-overrides ConfluentCloudApiSecrets=${SECRET_ARN} ServiceAccountName=cfn-test-service-accountIf you are getting errors with the resource, you can see in the logs what issues occurred that lead to this issue. With the template activate.template, you can see that there is a CloudWatch log group that will be logging the code execution and so you can open an issue on GitHub
If at any point in the logging you'd notice information that is not supposed to be there, please notify it immediately. With that said, as the "vendor" of that resource, we will never have access to these logs or anything in your account.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent